| Contents |
|---|
This release is a minor point upgrade that primarily addresses bugs found in the previous version as well as the following:
While most of the dialogs displayed during installation should be fairly self-explanatory, detailed instructions can be found in the Installation Guide.
You can download installable executables of AppComposer from our website: support.digislice.com.
Simply fill out the registration form, supplying a valid email address, and two things will be sent to you: a link to the current installable executables, and a license key (generated based on your name and email address). We also request that you fill out the rest of the survey, to help us build better software for you.
Note: AppComposer comes in two flavors: with and without an included Java SDK. If you don't mind a larger download, we encourage you to use the one with the included Java SDK, which will ensure that you have the right version of the SDK. If you know you already have a recent SDK (SDK, not just the JRE, version 1.3 or better) installed on your system, then you can save some time and space by downloading AppComposer without Java. If you are not sure, download the one with Java. If you install the one without Java and have problems running AppComposer, try downloading and installing the one with the Java SDK.
High-end workstations with at least 512MB of physical memory. The official platforms currently supported:
Note: You must have installed a Java Software Development Kit (SDK or JDK) before AppComposer can be installed, unless you download a version of AppComposer that has a JVM embedded into it. You can download a version of J2SE SDK from Sun Microsystems from their website (make sure you download and installed the SDK as the JRE is not sufficient).
Simply execute the program,
AppComposerInstallWindows.exe and following the
instructions displayed in the InstallAnywhere dialog process as
explained in the Getting
Started Guide.
Simply execute the shell script,
AppComposerInstallLinux.bin from the command line,
as in:
$ sh ./AppComposerInstallLinux.bin Preparing to install... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer...
Continue following the instructions displayed in the InstallAnywhere dialog process as explained in the Installation Guide.
Simply execute the shell script,
AppComposerInstallSolaris.bin from the command line,
as in:
$ sh ./AppComposerInstallSolaris.bin Preparing to install... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer...
Continue following the instructions displayed in the InstallAnywhere dialog process as explained in the Installation Guide.
Use StuffIt to
uncompress the SIT
file that you download by double-clicking on it. You will be left with an
installable executable that can be double-clicked to
execute to actually install the product.
Continue following the instructions displayed in the InstallAnywhere dialog process as explained in the Installation Guide.
Note: If you are upgrading from a previous version of AppComposer, you must either install the new version of AppComposer into the same directory, or move the original AppComposer to the Trash, and then empty the trash can before installing the new version of AppComposer.
Support for this product can be obtained in any of the following methods:
The following describe in more detail some of the major changes and features added to the product for this release.
We added a new template component similar to the JSPTemplate
bean that allows web pages to be written using the open source
FreeMarker Template Engine.
Packaging the FreeMarker technology as a JavaBean allows AppComposer users to easily
build FreeMarker data models and process them against FreeMarker templates to
create dynamic output. For more information, see the FreeMarkerBean
documentation or open the example projects in the examples/FreeMarkerExamples
directory.
The following is a brief listing of some of the bugs from the previous (3.0.1) version that have been closed in this (3.0.2) version:
| ID | Summary Description |
|---|---|
| 123 | Eval popup fails to draw sometimes on Windows JDK 1.3.1 |
| 178 | Can't set parameters to SQLRawStatement |
| 175 | Trying to open Alarm.zac fails and appears to lock up product |
| 73 | Saving capsules should automatically add .zac extension |
| 74 | When saving a capsule, the default name should be different |
| 128 | When saving a capsule as a jar, it should default to a name |
The following is a listing of known bugs and issues associated with this version of AppComposer. Details concerning these bugs can be found by logging into our Bugzilla bug tracking system at bugs.digislice.com.
| ID | Summary Description | Priority |
|---|---|---|
| 131 | Selecting "wedge popup items" do not stick to the properties panel [Mac OS X only] | P3 |
| Workaround: This is a strange de-focus issue where the contents don't get saved unless you loose focus from widget just the "right way". One workaround is to click in the field and hit the tab or return key. | ||
| 177 | Cannot open capsules that use missing beans. | |
| Workaround: See the bug details. | ||
| 130 | Cosmetic issues of the menus make it difficult to use. | |
| Workaround: Minor cosmetic issues that will be addressed in a future release. The product is still workable. | ||
| 22 | Console window has no vertical scrollbar toggle. | |
| Workaround If you resize the window, it is usually redisplayed. You can also select all of the text, and copy/paste it to another program for easier viewing. | ||
| 60 | 'Editor not Available' message for constant value of type 'Object' is misleading. | |
| Comments: The message displayed is a warning message. See details in order to understand what the error message should actually say. | ||
| 62 | Focus problem in console window after dialog dismissed | |
| Workaround: See the bug details. | ||
| 47 | Spurious error about "Port 80 in use" when port is not set to 80. | |
| Comments: The error message that is displayed shouldn't be displayed. It works correctly. Most people, however, will not run into it. |