Release History Build 36 Build 34 Build 33 Build 32 Build 24 Build 23 Build 22 Build 21 Build 20 Build 19 and older builds Known Issues Release History Build 36 New Features: Layout Editor: New "Sort" checkbox to display available function names sorted by function name (case-sensitive). Uncheck to display in the order that the functions occur in the script. New textfield and buttons to find first/next function name that begins with or contains a specified string (not case-sensitive). Also a new button to position to the last function in the list and select it. Boolean component attributes are now rendered as checkboxes in the attributes table (instead of as comboboxes with true/false choices) Script Editor: Pressing Enter in the "Search for" field now does "Find Next" action. New combobox with function names to quickly jump to selected function. When returning to script editor, now displays the last line you were on. Bug Fixes: Clicking into the "Search for" textfield now resets any selected text in the script editor, and the search is done on the "Search for" value. The "Save As" routine now edits that the app name is not a reserved object name ("button", "jsifile", etc.), which can cause problems. Build 34 New Features: New menubar choice "Run Plugin Application..." to run configured plug-in apps Source code generator for Progress 4GL now creates folders as needed for generated 4GL files Updated documentation files. Updated xml/examples/StdFns.xml file. Bug Fixes: Source code generator for Progress 4GL now creates generated 4GL files in PC format instead of unix format (uses CR/LF newlines instead of just LF) Build 33 New Features: Updated documentation files. Updated system/jsiconfig.xml file. Updated xml/examples/StdFns.xml file. Bug Fixes: Attempting to close the source code generator window by clicking the "X" button in the upper right-hand corner of the frame now warns the user to do this only from the main window (so any changes are saved correctly) and does not close the generator window. When a component attribute is assigned a value equal to the default value for that component (as defined in the system/jsiconfig.xml file), that attribute will be removed from the component definition in the xml file. This also applies to values that are empty strings when no default is defined (i.e. where the default is also an empty string). Likewise, removing the filename of a button image attribute will delete this attribute from the XML file when it is saved. This prevents any problems caused by an empty image filename string when running the application. The vertical scrollbar options for textarea and textpane components are now limited to "Always" and "Never" (the default). The former "As Needed" option was never implemented and has been removed. All Jargon Reader engines treat the presence of a "verticalScrollBarPolicy" attribute in the xml document as meaning "Always" (regardless of the value assigned to the attribute). This has caused some confusion in the past. Text components in existing apps with a value of "As Needed" will continue to behave as "Always" unless changed. When edited in Jargon Writer, they will now show a value of "20", which was the numeric value used for the "As Needed" option. Selecting "Never" as the value removes the attribute from the xml file, and causes the textarea or textpane to be rendered without a vertical scrollbar and limits input in a textarea to its visible rows. Build 32 New Features: Updated documentation files. New ReaderPDA and ReaderWIN executables. Updated system/jsiconfig.xml and xml/examples/StdFns.xml files. New Microsoft Installer ("msi") program to install Jargon Writer. Support for host environments that use PHP scripting. (3.3.32.01) Bug Fixes: Viewing and saving a preferences file (writer.ini, etc) no longer loses that part of a preference value to the right of an equals sign ("=") in the value. When updating an attribute value, ending with the TAB key or clicking the mouse elsewhere in the attribute table now saves the value. However, clicking elsewhere in the layout window (such as in the design tree or layout grid) currently does NOT save the value. (3.3.32.02) Assigning a new or changed function to a component event was not flagging the current app as having been changed, thus allowing the changes to be lost on close. (3.3.32.02) When a component event with an assigned function is displayed, the function is now highlighted in the Available Functions table and the table is scrolled if necessary to display that function name. Also when returning from the Script Editor window, these display values are now retained. (3.3.32.02) Setting the label attribute of a button to an empty string will now delete this label attribute from the XML file when it is saved. Then, when the application is run, any images used with the button will be rendered correctly with no extra space at the top or bottom. (3.3.32.03) Build 24 New Features: Includes V3.3.16 ReaderPDA.exe and ReaderWIN.exe executables Updated documentation files Updated host procedures for ASP, Java, Oracle and Progress Updated system/jsiconfig.xml and xml/examples/StdFns.xml files. Bug Fixes: none Build 23 New Features: The startup screen now allows selection of a preferences file other than the default "xml/writer/writer.ini" file. Choices are stored in a text file "writer.cfg" in the JargonWriter33 root directory. Choices may be simple filenames (which are assumed to be in the "xml/writer" folder) or full pathnames, or relative pathnames. See writer.cfg for examples. Bug Fixes: Opening a new app while editing a script now saves the script changes to the currently open app before opening the new app and displaying its script in the script editor window. Build 22 New Features: Updated system/jsiconfig.xml with various recently added global methods, which are used in the script editor for reference and insertion in scripts. Added xml/examples/StdFns.xml app with many examples of common script functions. Allows two or more physically different xml apps with the same appname to be open at the same time, e.g. dir1/app1.xml and dir2/app1.xml. The second and later apps will have a parenthesized number temporarily suffixed to the appname, e.g. myapp(2). The suffix will be removed when the app is run or saved. Bug Fixes: Prevents the same physical xml app from being opened twice. Corrects problem with viewing script editor when no app is open. Corrects problem with closing apps from the script editor. Build 21 New Features: Build 21 is a complete production release of Version 3.3 Jargon Writer. It includes the 3.3.01 versions of ReaderPDA.exe, ReaderWIN.exe and writer.exe, plus updated documentation reflecting the new features and defect corrections included in the 3.3.01 Jargon Reader releases. There are no changes to the Jargon Writer functionality itself, it is the same as in Build 20. Build 20 New Features: Build 20 is the first production release of Version 3.3 Jargon Writer. All new features are described in the online help documents. Builds 19 and older builds These builds were beta releases. Known Issues D31.17 (L) splitting a component xml element onto two lines causes a parsing error e.g. this won't parse, but it is legal XML syntax: <tree name="tree1" text="Applications" initialWidth="230" initialHeight="350" imageList="writer/default.gif,writer/node1.gif,writer/node2.gif"> D32.13 (L) If you click on a button and the linked function disables that button, focus remains on it and you can press the space bar and fire the event again. This should not happen. If a button is disabled, the space bar or Enter key should not fire it. D32.29 (L) When adding a panel below another panel (in ForDocs.xml), it has the correct placement in the grid (gridY="1") but is placed above the other panel in the component tree. Maybe it is because this app already has a menubar and a panel in the frame (?) See: ForDocs.xml D32.36 (L) Dev tree does not maintain state when frame is hidden and then set visible again. Tree completely compresses when frame is made visible. (There is currently a workaround in the script that expands the selected node and its parents, which provides much of the desired behavior). D32.38 (L) When defining an "Exit" menuitem under File menu, the existing hardcoded "Exit" menu item is given the function to run. However the Exit stays as the top choice and ideally should be in the position defined in the xml menuitems. D32.41 (M) Designpanel VSB does not scroll correctly. It scrolls ESE instead of south when scrolling down. Also picks up bottom of JW frame itself. The HSB seems to be ok. Also one time it lost both scrollbars but cannot reproduce the behavior. Example: try scrolling frame0 in Docs2.xml. D32.55 (H) If a cardpanel has only one card, deleting the card causes Writer to blow up with a system error message. The workaround is to delete the cardpanel itself, which also deletes the card that it contains. Copyright © 1999-2008 Jargon Software, Inc. All rights reserved.