...
One of the most asked for features now available in Automise 5, stepping into included projects. In Automise 7 and earlier, you could only step over included projects, and wait for them to return. In Automise 5, you can step into the included project, if it is not already opened the IDE will open the project and switch to it automatically. To make this possible, there are now "Step Into" and "Step Over" functions. The Step into/over now also applies to targets Action Lists (see below).
Debugger breakpoints now have conditions :
ActionLists renamed to Targets
ActionLists have been renamed to Targets. Targets can now also define dependencies, so you can for example define Clean, Build, Test, and have Test depend on Build. If you execute the Test target, and Build has not already been executed, it will be executed first before Test. Targets can be specified on the command line.
In Automise 7 and earlier, projects had a Main and an OnFailure (global error handler) actionlist. In Automise 5, projects just have a Default Target. Older projects will be imported such that the Main and OnFailure Targets are called from the Default Target inside a try/catch block.
...
Run Action List Action
You can now return values from Targets Action Lists (ie out parameters) .
Non Visible Changes
...
The stepping engine was rewritten to enable stepping into included projects, and to enable target Action List dependencies. This, work, together with the new variables architecture is where the bulk of effort/time was spent in the Automise 5 development cycle.
...
In addition to the architectural changes, we also spent a lot of time refactoring the code, running static analysis tools over the source, looking for memory leaks, potential bugs etc. One of the results of this is reduced memory usage during a build compared to FB7AT4. The AT5 IDE does use slightly more memory than the FB7 AT4 IDE at startup (mostly due to the heavy use of delphi generics), however the runtime memory usage is much lower.A large part of the refactoring involved unit testing (we created a new unit test framework to suite our needs!) and creating a suite of integration tests.
...
The command line parameters have changed to be more consistent and easier to specify. You can also specify one or more targets Action Lists to execute (when not specified, the default target Action List is executed).
New Project File Formats
...
A new DSL style project file format (.fbp8atp5) is now the default format, it is very easy to diff.
| Code Block | ||
|---|---|---|
| ||
project
begin
projectid = {04710B72-066E-46E7-84C7-C04A0D8BFE18}
target
begin
name = Default
targetid = {E6DE94D6-5484-45E9-965A-DB69885AA5E2}
rootaction
begin
action.group
begin
id = {D860420B-DE46-4806-959F-8A92A0C86429}
end
end
end
end |
A new xml format (.fbx8atx5), much less verbose than the old format.
...
Compressed project files (.fbz8atz5) use the dsl format internally (compressed projects are just a zip file with a project.fbp8 atp5 inside it).
The default project file encoding is now UTF-8, which is more version control friendly (some version control systems treat utf-16 as binaries),