![]() ![]() Script Debugger offers a menu of running and favourite applications for application placeholders, a menu of installed script library names for script placeholders and a menu of commonly used framework names for framework placeholders.ĥ.8 …more coming 6. Script Debugger 6 offers new powers for placeholders referring to applications, script libraries and AppleScript Objective-C framework names when existing clippings, text substitutions and command completions. 5.7 Application, Script Library and Framework Picker If you have Dash installed, you can turn on support so that option-clicking on a word will look it up in Dash. When using interleaved syntax for handlers, parameters will be escaped with pipe characters if they clash with defined terminology. This avoids the new “– Grammar Police” comment being inserted by the compiler in 10.11 (El Capitan). If you type “it’s ” in code, it will be changed to “its “. This avoids a long standing problem where it was impossible to change the case of a variable, property, handler or script object once the script had been compiled. Script Debugger 6 performs each script compilation in a new AppleScript compiler instance. Additional improvements to autocompletion are planned to better support AppleScript Objective-C development. Improved code completion to include all matching user defined identifiers. While not yet fully complete, Script Debugger 6 at long last provides code folding where you can collapse block structures and comments within your code to reduce clutter when editing. When multiple search terms are entered the Open Quickly command looks for each term within the script name, description, finder comment and script source.įor example, if you have a series of scripts containing the same ‘writeToFile’ handler, you can locate these scripts by entering the search terms ‘write’, ‘writeToFile’ or ‘writeFile’. The Open Quickly window highlights the portion of the script’s name, description, Finder comment or script source that matches the search term(s) entered.ĭiscontiguous search matches are reported (when a single search term is entered), similar to the way Xcode’s Open Quickly command behaves when looking up identifiers and source file names. The Open Quickly command has been heavily revised for Script Debugger 6. You can elect to dismiss the progress display by clicking the ‘x’ button. Note also that progress information is shown in the window title bar and the script’s document tab. Script Debugger supports both determinate and indeterminate progress reporting. When a script begins reporting progress information by setting any of AppleScript’s progress reporting properties Script Debugger 6 responds by adding a progress bar display above the script’s source: Progress ReportingĪppleScript’s progress reporting properties (introduced in Mac OS X 10.10 (Yosemite) are fully supported in Script Debugger 6. ![]() This default copyright string may containing clipping directives where are expanded at the time a new script document is created. ![]() You are able to specify a default copyright string which is used when creating new bundled scripts and applications. Script Debugger 6 gives you the option of auto-incrementing build numbers each time a script is saved.Īdditionally, you are able to identify a Scripting Definition (SDEF) file from your script’s bundle and to select a developer ID to enable always-on code signing for your script. You are now able to edit a bundle ID, copyright string, marketing version string and build number. The Script Debugger 6 bundled script resource editor has been expanded. There is no requirement to go through a special Save or Export operation.Ģ. Once you enable code signing for a script by selecting a developer ID, Script Debugger signs your script each time you save it. Script Debugger 6 adopts an always-on approach to code signing. Given that it has been several years since the release of Script Debugger 5, I hope that the appearance of this information will give people confidence that Script Debugger 6’s release is imminent.īeta testing of Script Debugger 6 is on going and I will update this post as changes are made to the application.ĭISCLAIMER: Nothing is final until the software ships and there is always the possibility that a feature may have to be removed or altered in the final product. I’m posting this in-progress document publicly as a bit of an experiment. « Chromecast Followup | Home | Script Debugger 6 Release Notes (6A162) » Script Debugger 6 Release Notes (6A121) ![]()
0 Comments
Leave a Reply. |