Turbo Form Page Differences
Before Turbo Forms both global scripts and your custom web resources would have been loaded into a content IFRAME within the main window each time you navigate between records.
SparkleXRM solutions already have a load order mechanism that ensure that your custom scripts are loaded in order that they are needed.
Impact on unsupported code
The ribbon workbench 'how-to' article that shows starting a dialog from a ribbon button does infact use openStdWin to ensure consistency with the out of the box dialog experience. I have updated the code to use the parent window when required.
There are a couple of other notable aspects of Turbo Forms that I thought I'd point out:
IFRAMES that are collapsed by default are not sized correctly.
If you have an IFRAME or HTML Webresource inside a Tab that is collaposed by default you will find that they are not sized correctly when the tab is expanded. This will be fixed in an upcoming update but until then you will need to show the tab by default and collapse when the form is loaded.
entityType vs typename
Turbo Forms have dropped the typename attribute of Lookup values.
In the past, the following code would return the same:
With Turbo Forms only the documented entityType is available. The typename attribute was left over from the CRM4 days and just had not been removed until now!