Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features | ||||||||
Changed: | ||||||||
< < | _This page provides an overview of the new features in APPX 6.1.x | |||||||
> > | This page provides an overview of the new features in APPX 6.1.x | |||||||
Overview |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 451 to 452 | ||||||||
| ||||||||
Changed: | ||||||||
< < | For an up to date list of known issues, use Bugtracker & search for bugs in Release 6.1.1. These are the known bugs that we expect to fix in the patch release. | |||||||
> > | For an up to date list of known issues, use Bugtracker & search for bugs in Release 6.1.0. These are the known bugs that we expect to fix in the patch release. | |||||||
Comments: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 414 to 413 | ||||||||
Added: | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 412 to 412 | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: | ||||||||
Line: 437 to 438 | ||||||||
Added: | ||||||||
> > |
| |||||||
Known Issues
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 205 to 204 | ||||||||
.UTIL COMPUTE HASH - accepts an extra flag to compute the hash on the Unicode string
API Help | ||||||||
Changed: | ||||||||
< < | In the ILF editor when you press help, you will see a brief explanation of the API displayed along with some example code that can be cut & paste into your own code. You can also view the wiki page for that function for more detailed explanation. | |||||||
> > | In the ILF editor, when your cursor is on a line with an API statement, if you press help (F1), you will see a brief explanation of that API statement displayed along with some example code that can be cut & paste into your own code. You can also view the wiki page for that function for more detailed explanation by pressing the "View Web Page" button. | |||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 65 to 66 | ||||||||
APPX_PDF_FONT_PATH=<location of font files, default $APPXPATH/fonts/>
APPX_PDF_FONT_MONO=DejaVuSansMono APPX_PDF_FONT_MONO_BOLD=DejaVuSansMono-Bold APPX_PDF_FONT_MONO_ITALIC=DejaVuSansMono-Oblique APPX_PDF_FONT_MONO_BOLD_ITALIC=DejaVuSansMono-BoldOblique APPX_PDF_FONT_SANS=DejaVuSans APPX_PDF_FONT_SANS_BOLD=DejaVuSans-Bold APPX_PDF_FONT_SANS_ITALIC=DejaVuSans-Oblique APPX_PDF_FONT_SANS_BOLD_ITALIC=DejaVuSans-BoldOblique APPX_PDF_FONT_SERIF=DejaVuSerif APPX_PDF_FONT_SERIF_BOLD=DejaVuSerif-Bold APPX_PDF_FONT_SERIF_ITALIC=DejaVuSerif-Italic APPX_PDF_FONT_SERIF_BOLD_ITALIC=DejaVuSerif-BoldItalic | ||||||||
Added: | ||||||||
> > | Unicode Fields and CollationUnicode fields are using collation for sorting and comparison instead of ASCII character codes. This causes some behavioral differences between raw fields and Unicode fields in APPX that you should be aware of. Sorting a Unicode field can have a different result from sorting a Raw field. Since APPX uses collation for sorting Unicode fields, depending on the collation used, you may see different sorting results. Here is an example that shows the differences in result of sorting a Unicode field and a raw field with similar values: RAW -------- Unicode In this case APPX uses the default system collation on a Windows 10 machine which is "en_US". Queries also use collation to sort Unicode fields. So, sorting a Unicode field and a raw field with similar data may result in different sort order. You can use "APPX_QSORT_COL_NAME" and "APPX_QSORT_COL_STRENGTH" environment variables to change the collation used in query processes to sort Unicode fields. If these environment variables are not specified APPX uses the system's collation which also can be overridden (see below). Comparing Unicode Alpha fields may surprise you. If you are using Raw alpha field and run a statement like:The result will be TRUE since ASCII code for character 'a' is larger than 'A'. However, if you run the same statement on Unicode fields (based on the collation used) the result may be FALSE. In case of "en_US" collation, the result will be FALSE but if you use "en_US_POSIX" collation, the result will be TRUE. You can override the collation APPX uses by setting “APPX_UCODE_COL_NAME” and “APPX_UCODE_COL_STRENGTH” environment variables. However, there are some things you need to consider before doing that:
| |||||||
64-bit APPXAPPX 6.1 has been updated to run as a 64-bit application on some platforms. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
OverviewThe most significant change in this is release is support for a Unicode data type. From Wikipedia: "Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The latest version contains a repertoire of 136,755 characters covering 139 modern and historic scripts, as well as multiple symbol sets. The Unicode Standard is maintained in conjunction with ISO/IEC 10646, and both are code-for-code identical." The addition of Unicode will allow you to develop APPX applications to run in any language. | ||||||||
Line: 106 to 106 | ||||||||
Language Translation uses the new .UTIL COMPUTE HASH to compute hash values in the Dictionaries. Your Dictionaries are automatically converted during the migration.
New Predefined Fields | ||||||||
Changed: | ||||||||
< < | A number of new fileds have been defined for 6.1.0 and they are as follows: Work Fields: 'TEMP 4K', 'TEMP 4KC', 'TEMP 4KL', 'TEMP 4KL0', 'TEMP 4KR', 'TEMP 4KR0' | |||||||
> > | As a convenience, number of new fields have been defined for 6.1.0 as shown below. | |||||||
Added: | ||||||||
> > | Work Fields:
| |||||||
New & Revised APIsAll the .TEXT APIs have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware that this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 107 to 106 | ||||||||
Language Translation uses the new .UTIL COMPUTE HASH to compute hash values in the Dictionaries. Your Dictionaries are automatically converted during the migration.
New Predefined Fields | ||||||||
Changed: | ||||||||
< < | Place holder... | |||||||
> > | A number of new fileds have been defined for 6.1.0 and they are as follows: Work Fields: 'TEMP 4K', 'TEMP 4KC', 'TEMP 4KL', 'TEMP 4KL0', 'TEMP 4KR', 'TEMP 4KR0' | |||||||
New & Revised APIsAll the .TEXT APIs have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware that this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 339 to 340 | ||||||||
Added: | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 92 to 91 | ||||||||
You cannot do multiple actions that generates multiple SQL Queries. For example, you CAN add multiple fields to the end of the record, but you CANNOT add a field and delete a field at the same time. The reason for this limitation is that oracle does not support rollback on DML transactions. You still can take advantage of Quick restructure by doing it in multiple steps (Add all your fields, restructure, then delete the fields need to be removed, restructure again). | ||||||||
Changed: | ||||||||
< < | Appx officially supports Oracle SQL, PostgreSQL and MSSQL. Though MySQL is not officially supported, it will likely work and Appx recommends using 8.0.13 or newer to take advantage of Appx quick restructuring. | |||||||
> > | Appx officially supports Oracle and MS. SQL Server. Though MySQL is not officially supported, it will likely work and Appx recommends using 8.0.13 or newer to take advantage of Appx quick restructuring. | |||||||
Desktop Client Uses external Text ViewerThe Desktop Client now uses an external program for viewing text report. Previously these would be displayed in the client itself. The text viewer to use is specified in the client settings: | ||||||||
Line: 107 to 106 | ||||||||
Language Translation uses the new .UTIL COMPUTE HASH to compute hash values in the Dictionaries. Your Dictionaries are automatically converted during the migration.
New Predefined Fields | ||||||||
Changed: | ||||||||
< < | Place holder... | |||||||
> > | Place holder... | |||||||
New & Revised APIsAll the .TEXT APIs have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware that this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). | ||||||||
Line: 367 to 366 | ||||||||
Known Issues
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
We expect to deal with these issues in the next patch release. For an up to date list of known issues, use Bugtracker & search for bugs in Release 6.1.1. These are the known bugs that we expect to fix in the patch release. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 77 to 77 | ||||||||
Regardless of whether you install APPX as 32-bits, 64 bits or both, the applications you develop or upgrade from, will run on either 32 bit or 64-bit 6.1 APPX without further consideration as to bitness.
External Databases Quick Restructure | ||||||||
Changed: | ||||||||
< < | Place holder... | |||||||
> > | Prior to now, when restructured an external database, Appx would build a new table then transfer the data from the old table to the new table, delete the old table then rename the new table to the original table name. This method is inefficient particularly when the table had many records in it.
Now, Appx will analyze the changes that are being made and if they met certain criteria (listed below) then Appx will use SQL commands to restructured the external database. Otherwise, if the new restructuring criteria is not met, Appx will behave as it has in the past.
New restructuring criteria that will cause Appx to use SQL commands:
| |||||||
Desktop Client Uses external Text ViewerThe Desktop Client now uses an external program for viewing text report. Previously these would be displayed in the client itself. The text viewer to use is specified in the client settings: | ||||||||
Line: 325 to 340 | ||||||||
Deleted: | ||||||||
< < | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 325 to 325 | ||||||||
Added: | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 323 to 323 | ||||||||
Added: | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 321 to 321 | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 320 to 321 | ||||||||
Added: | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 319 to 318 | ||||||||
Added: | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 25 to 25 | ||||||||
The new API's have been enhanced to work with Unicode fields, but the older ones have not. You may need to update your applications to use the newer APIs. | ||||||||
Deleted: | ||||||||
< < | Since Unicode fields require 4 bytes per character, the maximum size of an Alpha/Text field is now 1M (1,048,576 characters). The maximum record length for an APPX/IO Type 9 (Large File) increased to 4,194,560 bytes but APPX/IO Type 1 file remains at 32K. Oracle or MS SQL Server don't have record length limit. | |||||||
Unicode is not accepted in ILF statements or Enduser/Designer Selections in a Query. Unicode is accepted in a Query at runtime. If you must refer to a Unicode character in ILF, you can use the \uxxxx syntax. For example, to use the ❤ symbol you could use:
SET --- TEMP 1 = \u2764 | ||||||||
Line: 44 to 42 | ||||||||
Changes in Release 6.1.0Here is a list of the changes in Release 6.1.0: | ||||||||
Added: | ||||||||
> > | Record Length and Field Length Limits IncreasedThe maximum size of an Alpha/Text field is now 1M (1,048,576) characters. The maximum record length for an APPX/IO Type 9 (Large File) increased to 4,194,560 bytes. This is enough to store a maximum field size (1M Unicode characters) + maximum key size (255 bytes) + 1 alignment byte. APPX/IO Type 1 file record length limit remains at 32K. Oracle or MS SQL Server don't have record length limit. | |||||||
UnicodeYou can now specify a 'Unicode' encoding type for Alpha and Text fields. This is entered in the Additional Attributes dialog box: | ||||||||
Line: 74 to 75 | ||||||||
Both versions can be installed and operate on the same server at the same time if they are installed in to separate directories. Regardless of whether you install APPX as 32-bits, 64 bits or both, the applications you develop or upgrade from, will run on either 32 bit or 64-bit 6.1 APPX without further consideration as to bitness. | ||||||||
Added: | ||||||||
> > | External Databases Quick RestructurePlace holder... | |||||||
Desktop Client Uses external Text ViewerThe Desktop Client now uses an external program for viewing text report. Previously these would be displayed in the client itself. The text viewer to use is specified in the client settings: | ||||||||
Line: 86 to 90 | ||||||||
Language TranslationLanguage Translation uses the new .UTIL COMPUTE HASH to compute hash values in the Dictionaries. Your Dictionaries are automatically converted during the migration. | ||||||||
Added: | ||||||||
> > | New Predefined FieldsPlace holder... | |||||||
New & Revised APIsAll the .TEXT APIs have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware that this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 289 to 290 | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 224 to 224 | ||||||||
The following bugs were addressed in this Release: | ||||||||
Added: | ||||||||
> > | ||||||||
| ||||||||
Line: 252 to 253 | ||||||||
Added: | ||||||||
> > | ||||||||
Line: 261 to 263 | ||||||||
Added: | ||||||||
> > |
| |||||||
Line: 278 to 281 | ||||||||
Added: | ||||||||
> > | ||||||||
Line: 287 to 291 | ||||||||
Added: | ||||||||
> > | ||||||||
Added: | ||||||||
> > | ||||||||
Added: | ||||||||
> > | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Added: | ||||||||
> > | ||||||||
New Features/Enhancements6.1.0: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 6 to 6 | ||||||||
Overview | ||||||||
Changed: | ||||||||
< < | The most significant change in this is release is support for a Unicode data type. From Wikipedia: "Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The latest version contains a repertoire of 136,755 characters covering 139 modern and historic scripts, as well as multiple symbol sets. The Unicode Standard is maintained in conjunction with ISO/IEC 10646, and both are code-for-code identical." The addition of Unicode will allow you to develop APPX applications to run in any language. | |||||||
> > | The most significant change in this is release is support for a Unicode data type. From Wikipedia: "Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The latest version contains a repertoire of 136,755 characters covering 139 modern and historic scripts, as well as multiple symbol sets. The Unicode Standard is maintained in conjunction with ISO/IEC 10646, and both are code-for-code identical." The addition of Unicode will allow you to develop APPX applications to run in any language. | |||||||
'UNICODE' is a new storage attribute for Alpha and Text fields. You can change this attribute, restructure the file, and APPX will accept Unicode data in that field. Although you may see some references to a NATIONAL encoding type, it is not implemented in this release. When storing the data in APPX/IO, APPX uses the UTF-32 format, which requires 4 bytes for each character. When printing Unicode data in a non PDF report or reading/writing a stream file, APPX uses UTF-8. The UTF-8 standard uses 1 to 4 bytes per character. It was designed for backward compatibility with ASCII. The first 128 characters of Unicode, which correspond one-to-one with ASCII, are encoded using a single octet with the same binary value as ASCII, so that valid ASCII text is valid UTF-8-encoded Unicode as well. | ||||||||
Line: 14 to 14 | ||||||||
Transcoding is the act of converting to or from Unicode. APPX handles this for you automatically. However, if you move a field containing Unicode data to a non Unicode field and the Unicode data cannot be transcoded to the target encoding a runtime error will occur. This is similar to an overflow condition with a numeric field. We do not want to simply continue, as you have lost data in this case. There are also APIs for transcoding that give you more control. | ||||||||
Changed: | ||||||||
< < | Various fields in APPX System Administration and Application Design have been converted to Unicode. As a result of this, System Administration, Application Design and all Structure files are incompatible between Release 6 and any earlier release. A migration tool is provided to move the System Administration and Application Design files to Release 6.0. See Upgrading an Existing installation for the details. | |||||||
> > | Various fields in APPX System Administration and Application Design have been converted to Unicode. As a result of this, System Administration, Application Design and all Structure files are incompatible between Release 6 and any earlier release. A migration tool is provided to move the System Administration and Application Design files to Release 6.x. See Upgrading an Existing installation for the details. | |||||||
Unicode is not accepted everywhere in the System Administration or Application Design files. Only those fields that are 'user-facing' have been changed. For example, Printer Descriptions, Form Descriptions, Field Descriptions, Field Column Headings are all Unicode. Fields the end user does not see, such as Process Names, File names, etc., are not Unicode. To check if a field accepts Unicode or not, just press Help (F1). The help text will tell you if it is a Unicode field. | ||||||||
Line: 25 to 25 | ||||||||
The new API's have been enhanced to work with Unicode fields, but the older ones have not. You may need to update your applications to use the newer APIs. | ||||||||
Changed: | ||||||||
< < | Since Unicode fields require 4 bytes per character, the maximum size of an Alpha/Text field is now 1M (1,048,576 characters). The maximum record length for an APPX/IO file remains at 32K, but is not limited when using Oracle or MS SQL Server. | |||||||
> > | Since Unicode fields require 4 bytes per character, the maximum size of an Alpha/Text field is now 1M (1,048,576 characters). The maximum record length for an APPX/IO Type 9 (Large File) increased to 4,194,560 bytes but APPX/IO Type 1 file remains at 32K. Oracle or MS SQL Server don't have record length limit. | |||||||
Unicode is not accepted in ILF statements or Enduser/Designer Selections in a Query. Unicode is accepted in a Query at runtime. If you must refer to a Unicode character in ILF, you can use the \uxxxx syntax. For example, to use the ❤ symbol you could use:
SET --- TEMP 1 = \u2764 | ||||||||
Line: 53 to 53 | ||||||||
Unicode fields must be aligned on a 4 byte boundary. When the file is processed, APPX will check this and warn you if you need to add alignment bytes. Simply add an alpha field of the designated length in front of your Unicode field. If you have more than one Unicode field in your file, you may have to add multiple alignment bytes. | ||||||||
Changed: | ||||||||
< < | If the new record length is > 32K, you will get a warning from the Data Dictionary compiler. If you are going to store this file in Oracle or SQL Server, you can ignore this. However, the 32k limit still applies to APPX/IO files. | |||||||
> > | If the new record length is > 32K, you will get a warning from the Data Dictionary compiler. If you are going to store this file in Oracle or SQL Server, you can ignore this. If you are using APPX/IO Type 9 file, the new record length limit is 4,194,560. However, the 32k limit still applies to APPX/IO Type 1 files. | |||||||
In order to display or print Unicode data, the field must have a GUI Attribute of either a LABEL (non modifiable field on an Input or normal field on an Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields on the image are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. | ||||||||
Line: 91 to 91 | ||||||||
The .STREAM functions have been reworked to read or write data in UTF-8 format. | ||||||||
Added: | ||||||||
> > | The regular expression library has changed to support unicode characters. It also supports more complex patterns. | |||||||
The following APIs were added: .TEXT FROM UNICODE - transcodes a Unicode field to a Raw field, with control over characters that can't be transcoded. | ||||||||
Line: 129 to 131 | ||||||||
The following fields have been added to --- WIDGET and can be manipulated via ILF: | ||||||||
Changed: | ||||||||
< < | Drop Shadows | |||||||
> > | Drop Shadows | |||||||
WIDGET DS VISIBLE WIDGET DS DISTANCE WIDGET DS ANGLE WIDGET DS OPACITY WIDGET DS SIZE WIDGET COLOR DS (Group Header) WIDGET COLOR DS R WIDGET COLOR DS G WIDGET COLOR DS B WIDGET COLOR DS NL | ||||||||
Line: 324 to 326 | ||||||||
Added: | ||||||||
> > | ||||||||
Known Issues
| ||||||||
Added: | ||||||||
> > |
| |||||||
We expect to deal with these issues in the next patch release. For an up to date list of known issues, use Bugtracker & search for bugs in Release 6.1.1. These are the known bugs that we expect to fix in the patch release. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 78 to 77 | ||||||||
The Desktop Client now uses an external program for viewing text report. Previously these would be displayed in the client itself. The text viewer to use is specified in the client settings: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | If no viewer is specified, it will be opened using the desktop default for .txt files. | |||||||
Changed: | ||||||||
< < | If no viewer is specified, it will be opened using the desktop default for .doc files. | |||||||
> > | If you wish to use Appx Report Viewer, you can set "useAppxTxtReportViewer" to true in your client's setting. | |||||||
Language TranslationLanguage Translation uses the new .UTIL COMPUTE HASH to compute hash values in the Dictionaries. Your Dictionaries are automatically converted during the migration. | ||||||||
Line: 107 to 108 | ||||||||
.UTIL COMPUTE HASH - accepts an extra flag to compute the hash on the Unicode string
API Help | ||||||||
Changed: | ||||||||
< < | In the ILF editor when you press help, you will see a brief explanation of the API displayed along with some example code that can be cut & paste into your own code. | |||||||
> > | In the ILF editor when you press help, you will see a brief explanation of the API displayed along with some example code that can be cut & paste into your own code. You can also view the wiki page for that function for more detailed explanation. | |||||||
New Widget fieldsThere were a number of GUI capabilities that were previously only accessible via macros (@xxx=yy). The following macros have been converted to formal WIDGET specifications: | ||||||||
Line: 170 to 175 | ||||||||
This option is also available in the Toolbar and Toolbox pulldown menu while at the Process level: | ||||||||
Changed: | ||||||||
< < | New flag to suppress PDF Dialog box | |||||||
> > | New flag to suppress Report Dialog box | |||||||
A new flag has been added to the System Parameters to allow you to suppress the PDF Confirmation Dialog box: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Changed: | ||||||||
< < | Normally when a PDF document is produced and the 'Print on Screen' flag is checked the document will be uploaded to the user's desktop. At that point, a PDF Confirmation Dialog box will appear and the user can continue to the next job step or choose to cancel the job. | |||||||
> > | Normally when a report document is produced and the 'Print on Screen' flag is checked the document will be uploaded to the user's desktop. At that point, a Report Confirmation Dialog box will appear and the user can continue to the next job step or choose to cancel the job. | |||||||
In many cases, this is unnecessary. You can check this box to globally skip this dialog box.
Jump to process from audit history | ||||||||
Line: 319 to 324 | ||||||||
Deleted: | ||||||||
< < | ||||||||
Known Issues
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 321 to 322 | ||||||||
Known Issues | ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
We expect to deal with these issues in the next patch release. For an up to date list of known issues, use Bugtracker & search for bugs in Release 6.1.1. These are the known bugs that we expect to fix in the patch release. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.1.0 Features_This page provides an overview of the new features in APPX 6.1.x | ||||||||
Line: 41 to 40 | ||||||||
There are additional considerations discussed in more detail at the end of the Upgrade instructions. | ||||||||
Changed: | ||||||||
< < | Changes in Release 6.0 | |||||||
> > | Changes in Release 6.1.0 | |||||||
Changed: | ||||||||
< < | Here is a list of the changes in Release 6.0: | |||||||
> > | Here is a list of the changes in Release 6.1.0: | |||||||
UnicodeYou can now specify a 'Unicode' encoding type for Alpha and Text fields. This is entered in the Additional Attributes dialog box: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Changed: | ||||||||
< < | APPX 6.0.0 Features | |||||||
> > | APPX 6.1.0 Features | |||||||
Changed: | ||||||||
< < | This page provides an overview of the new features in APPX 6.0. | |||||||
> > | _This page provides an overview of the new features in APPX 6.1.x | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
OverviewThe most significant change in this is release is support for a Unicode data type. From Wikipedia: "Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The latest version contains a repertoire of 136,755 characters covering 139 modern and historic scripts, as well as multiple symbol sets. The Unicode Standard is maintained in conjunction with ISO/IEC 10646, and both are code-for-code identical." The addition of Unicode will allow you to develop APPX applications to run in any language. | ||||||||
Line: 96 to 96 | ||||||||
.ENV GET ENCODINGS - populates --- ENCODING with all the valid text encodings .UTIL COMPUTE HASH - accepts an extra flag to compute the hash on the Unicode string | ||||||||
Added: | ||||||||
> > | API HelpIn the ILF editor when you press help, you will see a brief explanation of the API displayed along with some example code that can be cut & paste into your own code. | |||||||
New Widget fieldsThere were a number of GUI capabilities that were previously only accessible via macros (@xxx=yy). The following macros have been converted to formal WIDGET specifications: | ||||||||
Line: 201 to 204 | ||||||||
The Output STANDARD ACTION LOG and the Input CONFIRMATION (END) have been added to application 0LC and can now be hooked.
Bugs Fixed | ||||||||
Added: | ||||||||
> > | 6.0.0: | |||||||
The following bugs were addressed in this Release: | ||||||||
Changed: | ||||||||
< < | Unsigned Binary does not convert properly (#2270) Image Editor Item Display locks session (#2571) 'No Record Currently Held' error (#2574) Field and Domain with same name share token values (#2947) RBS - Copying at the Workgroup level doesn't work (#4102) RBS - Multiple Roles with same name & same user (#4103) Duplicate 'T' shortcuts in 'Enter / Edit Translations' (#4108) | |||||||
> > | Unsigned Binary does not convert properly (#2270) Image Editor Item Display locks session (#2571) 'No Record Currently Held' error (#2574) Field and Domain with same name share token values (#2947) RBS - Copying at the Workgroup level doesn't work (#4102) RBS - Multiple Roles with same name & same user (#4103) Duplicate 'T' shortcuts in 'Enter / Edit Translations' (#4108) | |||||||
Known Issues
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 205 to 206 | ||||||||
Unsigned Binary does not convert properly (#2270) Image Editor Item Display locks session (#2571) 'No Record Currently Held' error (#2574) Field and Domain with same name share token values (#2947) RBS - Copying at the Workgroup level doesn't work (#4102) RBS - Multiple Roles with same name & same user (#4103) Duplicate 'T' shortcuts in 'Enter / Edit Translations' (#4108) | ||||||||
Deleted: | ||||||||
< < | HTML Client
Scrolling screens missing column separators (#3187) Find Records for date fields in Tables does not work (#3920) File upload freezes if file name contains spaces (#3943) Using -mapOptionKey does not work (#3953) Text boxes can be resized, but fields below bleed through (#4001) Table headings don't resize for larger font (#4012) .CLIENT UPLOAD FILE hangs 2nd time (#4018) Scan screen rendered incorrectly (#4014) Unable to Upload Large Files (#4026) Tltle Bar Background Color is Used on Entire Window (#4033) Secure icon forces date/time display mostly off screen (#4037) Sometimes page load gets stuck on Loading... (#4090) HTML Client 2017121101 incompatible with NPM Module mongodb 3.0rc0 (#4094) | |||||||
Known Issues
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 17 to 17 | ||||||||
Various fields in APPX System Administration and Application Design have been converted to Unicode. As a result of this, System Administration, Application Design and all Structure files are incompatible between Release 6 and any earlier release. A migration tool is provided to move the System Administration and Application Design files to Release 6.0. See Upgrading an Existing installation for the details. Unicode is not accepted everywhere in the System Administration or Application Design files. Only those fields that are 'user-facing' have been changed. For example, Printer Descriptions, Form Descriptions, Field Descriptions, Field Column Headings are all Unicode. Fields the end user does not see, such as Process Names, File names, etc., are not Unicode. To check if a field accepts Unicode or not, just press Help (F1). The help text will tell you if it is a Unicode field. | ||||||||
Added: | ||||||||
> > | This release has increased memory requirements, and performance in some areas is slow. We are aware of these issues, and they will be addressed in the next patch release. | |||||||
Application Design ConsiderationsAll --- TEMP fields are now Unicode. This may have an impact if you are PASSing a TEMP field to an internal or external routine or program. If it isn't expecting Unicode, that may be a problem. A number of --- WORK RAW xx fields have been added - you can use these in place of --- TEMP fields if you need a non Unicode field. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 127 to 128 | ||||||||
Line Settings | ||||||||
Changed: | ||||||||
< < | WIDGET LINE BASE NUM WIDGET LINE STROKE OFF | |||||||
> > | WIDGET LINE BASE WIDGET LINE BASE NUM WIDGET LINE STROKE OFF | |||||||
HTML Client Table Settings |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 201 to 201 | ||||||||
The following bugs were addressed in this Release: | ||||||||
Changed: | ||||||||
< < | Field and Domain with same name share token values (#2947) RBS - Copying at the Workgroup level doesn't work (#4102) RBS - Multiple Roles with same name & same user (#4103) Duplicate 'T' shortcuts in 'Enter / Edit Translations' (#4108) | |||||||
> > | Unsigned Binary does not convert properly (#2270) Image Editor Item Display locks session (#2571) 'No Record Currently Held' error (#2574) Field and Domain with same name share token values (#2947) RBS - Copying at the Workgroup level doesn't work (#4102) RBS - Multiple Roles with same name & same user (#4103) Duplicate 'T' shortcuts in 'Enter / Edit Translations' (#4108) | |||||||
HTML Client
Scrolling screens missing column separators (#3187) Find Records for date fields in Tables does not work (#3920) File upload freezes if file name contains spaces (#3943) Using -mapOptionKey does not work (#3953) Text boxes can be resized, but fields below bleed through (#4001) Table headings don't resize for larger font (#4012) .CLIENT UPLOAD FILE hangs 2nd time (#4018) Scan screen rendered incorrectly (#4014) Unable to Upload Large Files (#4026) Tltle Bar Background Color is Used on Entire Window (#4033) Secure icon forces date/time display mostly off screen (#4037) Sometimes page load gets stuck on Loading... (#4090) HTML Client 2017121101 incompatible with NPM Module mongodb 3.0rc0 (#4094) Known Issues | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
We expect to deal with these issues in the next patch release. For an up to date list of known issues, use Bugtracker & search for bugs in Release 6.0.1. These are the known bugs that we expect to fix in the patch release. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 214 to 213 | ||||||||
| ||||||||
Changed: | ||||||||
< < | For an update to date list of known issues, use Bugtracker & search for bugs in Release 6.0.1. These are the known bugs that we expect to fix in the patch release. | |||||||
> > | For an up to date list of known issues, use Bugtracker & search for bugs in Release 6.0.1. These are the known bugs that we expect to fix in the patch release. | |||||||
Comments: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 69 to 70 | ||||||||
If no viewer is specified, it will be opened using the desktop default for .doc files. | ||||||||
Added: | ||||||||
> > | Language TranslationLanguage Translation uses the new .UTIL COMPUTE HASH to compute hash values in the Dictionaries. Your Dictionaries are automatically converted during the migration. | |||||||
New & Revised APIsAll the .TEXT APIs have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware that this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 56 to 56 | ||||||||
In order to display or print Unicode data, the field must have a GUI Attribute of either a LABEL (non modifiable field on an Input or normal field on an Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields on the image are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. You also need to consider how this field is used. If it is moved to a non Unicode field (via SET or RECEIVE) that will cause a runtime error to occur if the source field contains Unicode characters that cannot be transcoded. To prevent this, all target fields must also be Unicode and any fields they are moved to, and so on. | ||||||||
Added: | ||||||||
> > |
APPX ships with the DejaVu fonts for PDF printing. You can install a different set of fonts if required, and then use the following environment variable to override the defaults:
APPX_PDF_FONT_PATH=<location of font files, default $APPXPATH/fonts/>
APPX_PDF_FONT_MONO=DejaVuSansMono APPX_PDF_FONT_MONO_BOLD=DejaVuSansMono-Bold APPX_PDF_FONT_MONO_ITALIC=DejaVuSansMono-Oblique APPX_PDF_FONT_MONO_BOLD_ITALIC=DejaVuSansMono-BoldOblique APPX_PDF_FONT_SANS=DejaVuSans APPX_PDF_FONT_SANS_BOLD=DejaVuSans-Bold APPX_PDF_FONT_SANS_ITALIC=DejaVuSans-Oblique APPX_PDF_FONT_SANS_BOLD_ITALIC=DejaVuSans-BoldOblique APPX_PDF_FONT_SERIF=DejaVuSerif APPX_PDF_FONT_SERIF_BOLD=DejaVuSerif-Bold APPX_PDF_FONT_SERIF_ITALIC=DejaVuSerif-Italic APPX_PDF_FONT_SERIF_BOLD_ITALIC=DejaVuSerif-BoldItalic | |||||||
Desktop Client Uses external Text ViewerThe Desktop Client now uses an external program for viewing text report. Previously these would be displayed in the client itself. The text viewer to use is specified in the client settings: | ||||||||
Added: | ||||||||
> > | If no viewer is specified, it will be opened using the desktop default for .doc files. | |||||||
New & Revised APIsAll the .TEXT APIs have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware that this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). | ||||||||
Line: 202 to 210 | ||||||||
| ||||||||
Added: | ||||||||
> > | For an update to date list of known issues, use Bugtracker & search for bugs in Release 6.0.1. These are the known bugs that we expect to fix in the patch release. | |||||||
Comments:Read what other users have said about this page or add your own comments. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 195 to 194 | ||||||||
HTML Client | ||||||||
Changed: | ||||||||
< < | Scrolling screens missing column separators (#3187) Find Records for date fields in Tables does not work (#3920) Using -mapOptionKey does not work (#3953) Text boxes can be resized, but fields below bleed through (#4001) Table headings don't resize for larger font (#4012) .CLIENT UPLOAD FILE hangs 2nd time (#4018) Scan screen rendered incorrectly (#4014) Unable to Upload Large Files (#4026) Tltle Bar Background Color is Used on Entire Window (#4033) Secure icon forces date/time display mostly off screen (#4037) Sometimes page load gets stuck on Loading... (#4090) HTML Client 2017121101 incompatible with NPM Module mongodb 3.0rc0 (#4094) | |||||||
> > | Scrolling screens missing column separators (#3187) Find Records for date fields in Tables does not work (#3920) File upload freezes if file name contains spaces (#3943) Using -mapOptionKey does not work (#3953) Text boxes can be resized, but fields below bleed through (#4001) Table headings don't resize for larger font (#4012) .CLIENT UPLOAD FILE hangs 2nd time (#4018) Scan screen rendered incorrectly (#4014) Unable to Upload Large Files (#4026) Tltle Bar Background Color is Used on Entire Window (#4033) Secure icon forces date/time display mostly off screen (#4037) Sometimes page load gets stuck on Loading... (#4090) HTML Client 2017121101 incompatible with NPM Module mongodb 3.0rc0 (#4094) | |||||||
Known Issues
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 21 to 21 | ||||||||
All --- TEMP fields are now Unicode. This may have an impact if you are PASSing a TEMP field to an internal or external routine or program. If it isn't expecting Unicode, that may be a problem. A number of --- WORK RAW xx fields have been added - you can use these in place of --- TEMP fields if you need a non Unicode field. | ||||||||
Changed: | ||||||||
< < | The new API's have been enhanced to work with Unicode fields, but the older ones have not. You may need to update your applications to use the newer API's, i.e., use --- .STREAM OPEN/READ/WRITE instead of --- STREAM OPEN/READ/WRITE. | |||||||
> > | The new API's have been enhanced to work with Unicode fields, but the older ones have not. You may need to update your applications to use the newer APIs. | |||||||
Since Unicode fields require 4 bytes per character, the maximum size of an Alpha/Text field is now 1M (1,048,576 characters). The maximum record length for an APPX/IO file remains at 32K, but is not limited when using Oracle or MS SQL Server. | ||||||||
Line: 195 to 195 | ||||||||
HTML Client | ||||||||
Changed: | ||||||||
< < | Scrolling screens missing column separators (#3187) Find Records for date fields in Tables does not work (#3920) Using -mapOptionKey does not work (#3953) Text boxes can be resized, but fields below bleed through (#4001) Table headings don't resize for larger font (#4012) .CLIENT UPLOAD FILE hangs 2nd time (#4018) Scan screen rendered incorrectly (#4014) Tltle Bar Background Color is Used on Entire Window (#4033) Sometimes page load gets stuck on Loading... (#4090) | |||||||
> > | Scrolling screens missing column separators (#3187) Find Records for date fields in Tables does not work (#3920) Using -mapOptionKey does not work (#3953) Text boxes can be resized, but fields below bleed through (#4001) Table headings don't resize for larger font (#4012) .CLIENT UPLOAD FILE hangs 2nd time (#4018) Scan screen rendered incorrectly (#4014) Unable to Upload Large Files (#4026) Tltle Bar Background Color is Used on Entire Window (#4033) Secure icon forces date/time display mostly off screen (#4037) Sometimes page load gets stuck on Loading... (#4090) HTML Client 2017121101 incompatible with NPM Module mongodb 3.0rc0 (#4094) | |||||||
Known Issues | ||||||||
Changed: | ||||||||
< < | APPX/ODBC is not available yet Performance Language Translation does not work | |||||||
> > |
| |||||||
Comments: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 192 to 192 | ||||||||
The following bugs were addressed in this Release:
Field and Domain with same name share token values (#2947) RBS - Copying at the Workgroup level doesn't work (#4102) RBS - Multiple Roles with same name & same user (#4103) Duplicate 'T' shortcuts in 'Enter / Edit Translations' (#4108) | ||||||||
Added: | ||||||||
> > |
HTML Client
Scrolling screens missing column separators (#3187) Find Records for date fields in Tables does not work (#3920) Using -mapOptionKey does not work (#3953) Text boxes can be resized, but fields below bleed through (#4001) Table headings don't resize for larger font (#4012) .CLIENT UPLOAD FILE hangs 2nd time (#4018) Scan screen rendered incorrectly (#4014) Tltle Bar Background Color is Used on Entire Window (#4033) Sometimes page load gets stuck on Loading... (#4090) | |||||||
Known IssuesAPPX/ODBC is not available yet |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 69 to 70 | ||||||||
The following APIs were added: | ||||||||
Changed: | ||||||||
< < | .TEXT FROM UNICODE - transcodes a Unicode field to a Raw field, with control over characters that can't be transcoded. | |||||||
> > | .TEXT FROM UNICODE - transcodes a Unicode field to a Raw field, with control over characters that can't be transcoded. | |||||||
Changed: | ||||||||
< < | .TEXT GET UNINAME - returns the name of the Unicode character. | |||||||
> > | .TEXT GET UNINAME - returns the name of the Unicode character. | |||||||
Changed: | ||||||||
< < | .TEXT SET UNINAME - sets a Unicode character by name. | |||||||
> > | .TEXT SET UNINAME - sets a Unicode character by name. | |||||||
Changed: | ||||||||
< < | .TEXT TO UNICODE - transcodes a Raw field to a Unicode field. | |||||||
> > | .TEXT TO UNICODE - transcodes a Raw field to a Unicode field. | |||||||
Changed: | ||||||||
< < | .TEXT UNICODE COMP - compares 2 Unicode fields. | |||||||
> > | .TEXT UNICODE COMP - compares 2 Unicode fields. | |||||||
.ENV GET ENCODINGS - populates --- ENCODING with all the valid text encodings | ||||||||
Line: 126 to 127 | ||||||||
WIDGET SUPPRESS LC | ||||||||
Changed: | ||||||||
< < | Consult the online manual at APPX Multi-Release Application Design Manual for details on the Widget specifications, or use the Help key while in Application Design. | |||||||
> > | Consult the online manual at APPX Multi-Release Application Design Manual for details on the Widget specifications, or use the Help key while in Application Design. | |||||||
New TRAP controlYou can now turn TRAPs on or off in an individual process. When you invoke a process, there is a new TRAP Control button: | ||||||||
Line: 197 to 198 | ||||||||
Performance | ||||||||
Added: | ||||||||
> > | Language Translation does not work | |||||||
Comments:Read what other users have said about this page or add your own comments. | ||||||||
Line: 218 to 221 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 FeaturesThis page provides an overview of the new features in APPX 6.0. | ||||||||
Line: 37 to 36 | ||||||||
There are many new fields on the GUI Attributes screens for Items on an Image. Because of this, we recommend using at least 27 rows in your Desktop Client settings. | ||||||||
Changed: | ||||||||
< < | There are additional considerations discussed in more detail at the end of the Upgrade instructions. | |||||||
> > | There are additional considerations discussed in more detail at the end of the Upgrade instructions. | |||||||
Changes in Release 6.0 | ||||||||
Line: 79 to 78 | ||||||||
.TEXT TO UNICODE - transcodes a Raw field to a Unicode field. .TEXT UNICODE COMP - compares 2 Unicode fields. | ||||||||
Added: | ||||||||
> > | .ENV GET ENCODINGS - populates --- ENCODING with all the valid text encodings .UTIL COMPUTE HASH - accepts an extra flag to compute the hash on the Unicode string | |||||||
New Widget fieldsThere were a number of GUI capabilities that were previously only accessible via macros (@xxx=yy). The following macros have been converted to formal WIDGET specifications: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 Features | ||||||||
Added: | ||||||||
> > | This page provides an overview of the new features in APPX 6.0. | |||||||
Overview |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 Features
Overview | ||||||||
Changed: | ||||||||
< < | The most significant change in this is release is support for a Unicode data type. From Wikipedia: Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The latest version contains a repertoire of 136,755 characters covering 139 modern and historic scripts, as well as multiple symbol sets. The Unicode Standard is maintained in conjunction with ISO/IEC 10646, and both are code-for-code identical. The addition of Unicode will you to develop APPX applications to run in any language. | |||||||
> > | The most significant change in this is release is support for a Unicode data type. From Wikipedia: "Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The latest version contains a repertoire of 136,755 characters covering 139 modern and historic scripts, as well as multiple symbol sets. The Unicode Standard is maintained in conjunction with ISO/IEC 10646, and both are code-for-code identical." The addition of Unicode will allow you to develop APPX applications to run in any language. | |||||||
'UNICODE' is a new storage attribute for Alpha and Text fields. You can change this attribute, restructure the file, and APPX will accept Unicode data in that field. Although you may see some references to a NATIONAL encoding type, it is not implemented in this release. When storing the data in APPX/IO, APPX uses the UTF-32 format, which requires 4 bytes for each character. When printing Unicode data in a non PDF report or reading/writing a stream file, APPX uses UTF-8. The UTF-8 standard uses 1 to 4 bytes per character. It was designed for backward compatibility with ASCII. The first 128 characters of Unicode, which correspond one-to-one with ASCII, are encoded using a single octet with the same binary value as ASCII, so that valid ASCII text is valid UTF-8-encoded Unicode as well. | ||||||||
Changed: | ||||||||
< < | Printing Unicode characters in a PDF document is handled by the inclusion of the DejaVu Font library. This is an open source font collection designed for greater coverage of Unicode, as well as providing more styles. Since there are over 1 million possible Unicode characters, not every font family can print all the characters. You may need to source a different font library if your target language is not fully supported in DejaVu. APPX provides a way for you to override the default fonts. The fonts will be embedded in the PDF document and will display regardless of what fonts the user has on their desktop. | |||||||
> > | Printing Unicode characters in a PDF document is handled by the inclusion of the DejaVu Font library. This is an open source font collection designed for greater coverage of Unicode, as well as providing more styles. Since there are over 1 million possible Unicode characters, not every font family can print all the characters. You may need to source a different font library if your target language is not fully supported in DejaVu. APPX provides a way for you to override the default fonts. The fonts will be embedded in the PDF document and will display regardless of which fonts are installed on the user's desktop. | |||||||
Changed: | ||||||||
< < | Transcoding is the act of converting to or from Unicode. APPX handles this for you automatically, however, if you move a field containing Unicode data to a non Unicode field and the Unicode data cannot be transcoded to the target encoding, a runtime error will occur. This is similar to an overflow condition with a numeric field. We do not want to simply continue, as you have lost data in this case. There are also APIs for transcoding that give you more control. | |||||||
> > | Transcoding is the act of converting to or from Unicode. APPX handles this for you automatically. However, if you move a field containing Unicode data to a non Unicode field and the Unicode data cannot be transcoded to the target encoding a runtime error will occur. This is similar to an overflow condition with a numeric field. We do not want to simply continue, as you have lost data in this case. There are also APIs for transcoding that give you more control. | |||||||
Changed: | ||||||||
< < | Various fields in APPX System Administration and Application Design have been converted to Unicode. Because of this, System Administration, Application Design and all data files are incompatible between Release 6 and any earlier release. A migration tool is provided to move the System Administration and Application Design files to Release 6.0. All key files must be rebuilt as well. See Upgrading an Existing installation for the details. | |||||||
> > | Various fields in APPX System Administration and Application Design have been converted to Unicode. As a result of this, System Administration, Application Design and all Structure files are incompatible between Release 6 and any earlier release. A migration tool is provided to move the System Administration and Application Design files to Release 6.0. See Upgrading an Existing installation for the details. | |||||||
Changed: | ||||||||
< < | Unicode is not accepted everywhere in the System Administration or Application Design files. Only those fields that are 'user-facing' have been changed. For example, Printer Descriptions, Form Descriptions, Field Descriptions, Field Column Headings, are all Unicode. Fields the end user does not see, such as Process Names, File names, etc, are not Unicode. To check if a field accepts Unicode or not, just press Help (F1). The help text will tell you if it is a Unicode field. | |||||||
> > | Unicode is not accepted everywhere in the System Administration or Application Design files. Only those fields that are 'user-facing' have been changed. For example, Printer Descriptions, Form Descriptions, Field Descriptions, Field Column Headings are all Unicode. Fields the end user does not see, such as Process Names, File names, etc., are not Unicode. To check if a field accepts Unicode or not, just press Help (F1). The help text will tell you if it is a Unicode field. | |||||||
Application Design Considerations | ||||||||
Changed: | ||||||||
< < | All --- TEMP fields are now Unicode. This may have an impact if you are PASSing a TEMP field to an internal or external routine or program. If it isn't expecting Unicode, that may be a problem. A number of --- WORK RAW xx fields have been added, you can use these in place of --- TEMP if you need a non Unicode field. | |||||||
> > | All --- TEMP fields are now Unicode. This may have an impact if you are PASSing a TEMP field to an internal or external routine or program. If it isn't expecting Unicode, that may be a problem. A number of --- WORK RAW xx fields have been added - you can use these in place of --- TEMP fields if you need a non Unicode field. | |||||||
Changed: | ||||||||
< < | The new API's have been enhanced to work with Unicode fields, but the older ones have not. You may need to update your applications to use the newer API's, ie, use --- .STREAM OPEN/READ/WRITE instead of --- STREAM OPEN/READ/WRITE. | |||||||
> > | The new API's have been enhanced to work with Unicode fields, but the older ones have not. You may need to update your applications to use the newer API's, i.e., use --- .STREAM OPEN/READ/WRITE instead of --- STREAM OPEN/READ/WRITE. | |||||||
Changed: | ||||||||
< < | Since Unicode fields require 4 bytes per character, the maximum size of an Alpha/Text field is now 1M (1,048,576) characters. The maximum record length for an APPX/IO file remains at 32K, but is not limited when using Oracle or MS SQL Server. | |||||||
> > | Since Unicode fields require 4 bytes per character, the maximum size of an Alpha/Text field is now 1M (1,048,576 characters). The maximum record length for an APPX/IO file remains at 32K, but is not limited when using Oracle or MS SQL Server. | |||||||
Changed: | ||||||||
< < | Unicode is not accepted in ILF statements. If you must refer to a Unicode character in ILF, you can use the \uxxxx syntax. For example, to use the ❤ symbol you could use: | |||||||
> > | Unicode is not accepted in ILF statements or Enduser/Designer Selections in a Query. Unicode is accepted in a Query at runtime. If you must refer to a Unicode character in ILF, you can use the \uxxxx syntax. For example, to use the ❤ symbol you could use: | |||||||
SET --- TEMP 1 = \u2764where 2764 is the code point for the ❤ symbol. | ||||||||
Added: | ||||||||
> > | Since Unicode is not allowed in ILF, the 'Delimited Exporter' in the Data Dictionary toolbox will substitute a ? for Unicode characters if generating a row of field names. | |||||||
If a Group field contains a Unicode field, you cannot SET that group to or from an Alpha field. The process will give an 'Invalid Storage Type' compile error. Similarly, Unicode fields cannot be set into a Group field. This may have an impact on your applications if you are using --- TEMP fields to move data to/from a group, since all --- TEMP fields are Unicode. You can use one of the new WORK RAW fields instead. If a group field contains a Unicode field, it can only be moved to/from another group field. | ||||||||
Changed: | ||||||||
< < | There are many new fields on the GUI Attributes screens for Items on an Image. Because of this, we recommend using at least 27 rows in your Desktop Client setting. | |||||||
> > | There are many new fields on the GUI Attributes screens for Items on an Image. Because of this, we recommend using at least 27 rows in your Desktop Client settings. | |||||||
There are additional considerations discussed in more detail at the end of the Upgrade instructions. | ||||||||
Line: 40 to 42 | ||||||||
Here is a list of the changes in Release 6.0:
Unicode | ||||||||
Changed: | ||||||||
< < | You can now specify a 'Unicode' encoding type for Alpha and Text fields. This is specifed in the Additional Attributes dialog box: | |||||||
> > | You can now specify a 'Unicode' encoding type for Alpha and Text fields. This is entered in the Additional Attributes dialog box: | |||||||
The default encoding type is RAW, which corresponds to US ASCII (ISO-8859-15). If you are not using ISO-8859-15 as your default encoding, then set the APPX_RAW_ENCODING environment variable to tell APPX which encoding you are using. | ||||||||
Changed: | ||||||||
< < | Unicode fields must be aligned on a 4 byte boundary. When the file is processed, APPX will check this and warn you if you need to add alignment bytes. Simply add a simple alpha field of the designated length in front of your Unicode field. If you have more than one Unicode field in your file, you may have to add multiple alignment bytes. | |||||||
> > | Unicode fields must be aligned on a 4 byte boundary. When the file is processed, APPX will check this and warn you if you need to add alignment bytes. Simply add an alpha field of the designated length in front of your Unicode field. If you have more than one Unicode field in your file, you may have to add multiple alignment bytes. If the new record length is > 32K, you will get a warning from the Data Dictionary compiler. If you are going to store this file in Oracle or SQL Server, you can ignore this. However, the 32k limit still applies to APPX/IO files. In order to display or print Unicode data, the field must have a GUI Attribute of either a LABEL (non modifiable field on an Input or normal field on an Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields on the image are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. | |||||||
Changed: | ||||||||
< < | If the new record length is > 32K, you will get a warning from the Data Dictionary compiler. If you are going to store this file in Oracle or SQL Server, you can ignore this, however, the 32k limit still applies to APPX/IO files. | |||||||
> > | You also need to consider how this field is used. If it is moved to a non Unicode field (via SET or RECEIVE) that will cause a runtime error to occur if the source field contains Unicode characters that cannot be transcoded. To prevent this, all target fields must also be Unicode and any fields they are moved to, and so on.
Desktop Client Uses external Text Viewer | |||||||
Changed: | ||||||||
< < | In order to display or print Unicode data, the field must have GUI Attribute of either a LABEL (non modifiable field on an Input or normal field on an Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields on the image are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. | |||||||
> > | The Desktop Client now uses an external program for viewing text report. Previously these would be displayed in the client itself. The text viewer to use is specified in the client settings: | |||||||
Changed: | ||||||||
< < | You also need to consider how this field is used. If it is moved to a non Unicode field (via SET, RECEIVE, etc) that will cause a runtime error to occur if the source field contains Unicode characters that cannot be transcoded. To prevent this, all target fields must also be Unicode and any fields they are moved to, and so on.
New & Revised API's | |||||||
> > |
New & Revised APIs | |||||||
Changed: | ||||||||
< < | All the .TEXT API's have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). | |||||||
> > | All the .TEXT APIs have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware that this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). | |||||||
The .STREAM functions have been reworked to read or write data in UTF-8 format. | ||||||||
Changed: | ||||||||
< < | The following API's were added: | |||||||
> > | The following APIs were added: | |||||||
.TEXT FROM UNICODE - transcodes a Unicode field to a Raw field, with control over characters that can't be transcoded. | ||||||||
Line: 72 to 79 | ||||||||
.TEXT UNICODE COMP - compares 2 Unicode fields.
New Widget fields | ||||||||
Changed: | ||||||||
< < | There were a number of GUI capabilities that were only accessible via macros (@xxx=yy). The following macros have been converted to formal WIDGET specifications: | |||||||
> > | There were a number of GUI capabilities that were previously only accessible via macros (@xxx=yy). The following macros have been converted to formal WIDGET specifications: | |||||||
@SDS - Drop Shadows @SLN - Layering @SFP - Focus Painting @SMV - Movable @SLUB, @SSPO - Line settings @TSRN - Show Row Numbers on Tables (HTML client only) @TSFB - Show footer bar on Tables (HTML client only) @TCSS - Case Sensitive Sorting on Tables (HTML client only) @FULC - Suppress use of Local Connector (HTML client only) | ||||||||
Line: 125 to 132 | ||||||||
Changed: | ||||||||
< < | The options are self explanatory. The system identifies 'your' TRAPs by checking the user id of the user that added the TRAP and the date. Anything you added today will be considered 'your' TRAPs. TRAPs you added in the past, or TRAPs added by other designers are not considered 'your' TRAPs. | |||||||
> > | The options are self-explanatory. The system identifies 'your' TRAPs by checking the user id of the user that added the TRAP and the date. Anything you added today will be considered 'your' TRAPs. TRAPs you added in the past, or TRAPs added by other designers are not considered 'your' TRAPs. | |||||||
Changed: | ||||||||
< < | The method of turning off TRAPs has been changed as well. Previously, APPX would convert the TRAP to a comment statement, making it awkward to activate the TRAP later. Now it will check the TF flags, and as long as there is one available flag, it will simply comment the TRAP, making it easier for you to uncomment it later. | |||||||
> > | The method of turning off TRAPs has been changed as well. Previously, APPX would convert the TRAP to a comment statement, making it awkward to reactivate the TRAP later. Now it will check the TF flags and as long as there is one available flag, it will simply comment the TRAP, making it easier for you to uncomment it later. | |||||||
This option is also available in the Toolbar and Toolbox pulldown menu while at the Process level: | ||||||||
Line: 164 to 171 | ||||||||
Choosing this font type will cause APPX to use the font specified by the Named Resource. If you choose this font type, you must also enter a Named Resource. This replaces the technique described where you have to read the WIDGET record and indirectly set WIDGET FONT to 10 via ILF. Now you can simply choose the font RESOURCE. | ||||||||
Changed: | ||||||||
< < | New utility to check for dup shortcuts | |||||||
> > | New utility to check for duplicate shortcuts | |||||||
A new utility has been added to the 'Tools' tab in Application Design - 'Check for Dup Shortcuts'. It will list all the shortcuts used in the application and flag the ones it thinks might be duplicates: In this example, the letter S is used for both the 'Save' button and the 'Sales Opport.' button and W is used for both 'Weather' and the WWW button. | ||||||||
Changed: | ||||||||
< < | 0LA Output STANDARD MOD LOG and 0LA Input CONFIRMATION (END) in 0LC and can be hooked | |||||||
> > | 0LA Output STANDARD ACTION LOG and 0LA Input CONFIRMATION (END) included in 0LC and can be hooked | |||||||
Changed: | ||||||||
< < | The Output STANDARD MOD LOG and the Input CONFIRMATION (END) have been added to application 0LC and can now be hooked. | |||||||
> > | The Output STANDARD ACTION LOG and the Input CONFIRMATION (END) have been added to application 0LC and can now be hooked. | |||||||
Bugs FixedThe following bugs were addressed in this Release: | ||||||||
Line: 205 to 212 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 Features
| ||||||||
Line: 40 to 40 | ||||||||
Here is a list of the changes in Release 6.0:
Unicode | ||||||||
Changed: | ||||||||
< < | You can now specify a 'Unicode' encoding type for Alpha and Text fields. This is speicifed in the Additional Attributes dialog box: | |||||||
> > | You can now specify a 'Unicode' encoding type for Alpha and Text fields. This is specifed in the Additional Attributes dialog box: | |||||||
Line: 131 to 131 | ||||||||
This option is also available in the Toolbar and Toolbox pulldown menu while at the Process level: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
New flag to suppress PDF Dialog boxA new flag has been added to the System Parameters to allow you to suppress the PDF Confirmation Dialog box: | ||||||||
Line: 204 to 204 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
APPX 6.0.0 Features
| |||||||||||||||||||
Line: 30 to 31 | |||||||||||||||||||
If a Group field contains a Unicode field, you cannot SET that group to or from an Alpha field. The process will give an 'Invalid Storage Type' compile error. Similarly, Unicode fields cannot be set into a Group field. This may have an impact on your applications if you are using --- TEMP fields to move data to/from a group, since all --- TEMP fields are Unicode. You can use one of the new WORK RAW fields instead. If a group field contains a Unicode field, it can only be moved to/from another group field. | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | There are many new fields on the GUI Attributes screens for Items on an Image. Because of this, we recommend using at least 27 rows in your Desktop Client setting. | ||||||||||||||||||
There are additional considerations discussed in more detail at the end of the Upgrade instructions.
Changes in Release 6.0 | |||||||||||||||||||
Line: 37 to 40 | |||||||||||||||||||
Here is a list of the changes in Release 6.0:
Unicode | |||||||||||||||||||
Changed: | |||||||||||||||||||
< < | You can now specify a 'Unicode' encoding type for Alpha and Text fields. This is in the Additional Attributes dialog box: | ||||||||||||||||||
> > | You can now specify a 'Unicode' encoding type for Alpha and Text fields. This is speicifed in the Additional Attributes dialog box: | ||||||||||||||||||
Line: 47 to 50 | |||||||||||||||||||
If the new record length is > 32K, you will get a warning from the Data Dictionary compiler. If you are going to store this file in Oracle or SQL Server, you can ignore this, however, the 32k limit still applies to APPX/IO files. | |||||||||||||||||||
Changed: | |||||||||||||||||||
< < | In order to display or print Unicode data, the field must have GUI Attribute of either a LABEL (non modifiable field or Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. | ||||||||||||||||||
> > | In order to display or print Unicode data, the field must have GUI Attribute of either a LABEL (non modifiable field on an Input or normal field on an Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields on the image are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. | ||||||||||||||||||
You also need to consider how this field is used. If it is moved to a non Unicode field (via SET, RECEIVE, etc) that will cause a runtime error to occur if the source field contains Unicode characters that cannot be transcoded. To prevent this, all target fields must also be Unicode and any fields they are moved to, and so on.
New & Revised API's | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | All the .TEXT API's have been reworked to accept Unicode strings up to 1M in length. The .TEXT LOWER TO UPPER and .TEXT UPPER TO LOWER use the Unicode library to convert text. If you have applications that add or subtract 32 from the ASCII value to convert case, be aware this technique will not work with Unicode data (unless the Unicode field only contains US ASCII characters). The .STREAM functions have been reworked to read or write data in UTF-8 format. The following API's were added: .TEXT FROM UNICODE - transcodes a Unicode field to a Raw field, with control over characters that can't be transcoded. .TEXT GET UNINAME - returns the name of the Unicode character. .TEXT SET UNINAME - sets a Unicode character by name. .TEXT TO UNICODE - transcodes a Raw field to a Unicode field. .TEXT UNICODE COMP - compares 2 Unicode fields. | ||||||||||||||||||
New Widget fields | |||||||||||||||||||
Added: | |||||||||||||||||||
> > |
There were a number of GUI capabilities that were only accessible via macros (@xxx=yy). The following macros have been converted to formal WIDGET specifications:
@SDS - Drop Shadows @SLN - Layering @SFP - Focus Painting @SMV - Movable @SLUB, @SSPO - Line settings @TSRN - Show Row Numbers on Tables (HTML client only) @TSFB - Show footer bar on Tables (HTML client only) @TCSS - Case Sensitive Sorting on Tables (HTML client only) @FULC - Suppress use of Local Connector (HTML client only) The migration utility will convert the macro to the formal specification when it can and the macros still work if you prefer those. Here is a sample GUI Attributes screen showing some of the new fields: We recommend running with at least 27 rows to accommodate the larger Property screens. The following fields have been added to --- WIDGET and can be manipulated via ILF: Drop Shadows WIDGET DS VISIBLE WIDGET DS DISTANCE WIDGET DS ANGLE WIDGET DS OPACITY WIDGET DS SIZE WIDGET COLOR DS (Group Header) WIDGET COLOR DS R WIDGET COLOR DS G WIDGET COLOR DS B WIDGET COLOR DS NL Layering WIDGET LAYER NO Focus Painting WIDGET FOCUS PAINTED Moveable WIDGET MOVE OPTION NO Line Settings WIDGET LINE BASE NUM WIDGET LINE STROKE OFF HTML Client Table Settings WIDGET TAB SHOW ROW NO WIDGET TAB SHOW FOOTER WIDGET CASE SENSITIVE HTML Client Local Connector Control WIDGET SUPPRESS LC Consult the online manual at APPX Multi-Release Application Design Manual for details on the Widget specifications, or use the Help key while in Application Design. | ||||||||||||||||||
New TRAP control | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | You can now turn TRAPs on or off in an individual process. When you invoke a process, there is a new TRAP Control button: If you click the TRAP Control button, you will get some choices: The options are self explanatory. The system identifies 'your' TRAPs by checking the user id of the user that added the TRAP and the date. Anything you added today will be considered 'your' TRAPs. TRAPs you added in the past, or TRAPs added by other designers are not considered 'your' TRAPs. The method of turning off TRAPs has been changed as well. Previously, APPX would convert the TRAP to a comment statement, making it awkward to activate the TRAP later. Now it will check the TF flags, and as long as there is one available flag, it will simply comment the TRAP, making it easier for you to uncomment it later. This option is also available in the Toolbar and Toolbox pulldown menu while at the Process level: | ||||||||||||||||||
New flag to suppress PDF Dialog box | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | A new flag has been added to the System Parameters to allow you to suppress the PDF Confirmation Dialog box: Normally when a PDF document is produced and the 'Print on Screen' flag is checked the document will be uploaded to the user's desktop. At that point, a PDF Confirmation Dialog box will appear and the user can continue to the next job step or choose to cancel the job. In many cases, this is unnecessary. You can check this box to globally skip this dialog box. | ||||||||||||||||||
Jump to process from audit history | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | While viewing Audit History in Application Design, you can jump to that process/file/field: The Audit Browser only shows the process information, but if the change was actually made at the Image level, the Jump button will take you to that Image. | ||||||||||||||||||
Jump to O/C from Button GA | |||||||||||||||||||
Changed: | |||||||||||||||||||
< < | New Font type Resource | ||||||||||||||||||
> > |
While viewing the GUI Attributes of a Button, you can Jump to the Optional Child specified by the button:
In this example, clicking the 'Children' button in the Toolbar will take you to Optional Child 1, since the button fires USER 1.
New Font - ResourceA new Font Type of 'RESOURCE' is available.: Choosing this font type will cause APPX to use the font specified by the Named Resource. If you choose this font type, you must also enter a Named Resource. This replaces the technique described where you have to read the WIDGET record and indirectly set WIDGET FONT to 10 via ILF. Now you can simply choose the font RESOURCE. | ||||||||||||||||||
New utility to check for dup shortcuts | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | A new utility has been added to the 'Tools' tab in Application Design - 'Check for Dup Shortcuts'. It will list all the shortcuts used in the application and flag the ones it thinks might be duplicates: In this example, the letter S is used for both the 'Save' button and the 'Sales Opport.' button and W is used for both 'Weather' and the WWW button. | ||||||||||||||||||
0LA Output STANDARD MOD LOG and 0LA Input CONFIRMATION (END) in 0LC and can be hooked | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | The Output STANDARD MOD LOG and the Input CONFIRMATION (END) have been added to application 0LC and can now be hooked. | ||||||||||||||||||
Bugs Fixed | |||||||||||||||||||
Added: | |||||||||||||||||||
> > | The following bugs were addressed in this Release:
Field and Domain with same name share token values (#2947) RBS - Copying at the Workgroup level doesn't work (#4102) RBS - Multiple Roles with same name & same user (#4103) Duplicate 'T' shortcuts in 'Enter / Edit Translations' (#4108) | ||||||||||||||||||
Known IssuesAPPX/ODBC is not available yet | |||||||||||||||||||
Line: 77 to 195 | |||||||||||||||||||
-- JeanNeron - 2018-02-20
| |||||||||||||||||||
Added: | |||||||||||||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX 6.0.0 Features
| ||||||||
Line: 47 to 46 | ||||||||
Unicode fields must be aligned on a 4 byte boundary. When the file is processed, APPX will check this and warn you if you need to add alignment bytes. Simply add a simple alpha field of the designated length in front of your Unicode field. If you have more than one Unicode field in your file, you may have to add multiple alignment bytes. If the new record length is > 32K, you will get a warning from the Data Dictionary compiler. If you are going to store this file in Oracle or SQL Server, you can ignore this, however, the 32k limit still applies to APPX/IO files. | ||||||||
Added: | ||||||||
> > | In order to display or print Unicode data, the field must have GUI Attribute of either a LABEL (non modifiable field or Output) or RAW TEXT. The default font for a LABEL is Arial, which may be noticeable if the other fields are not. You can override the default font to COURIER to use the same font as fields without a GUI attribute. You also need to consider how this field is used. If it is moved to a non Unicode field (via SET, RECEIVE, etc) that will cause a runtime error to occur if the source field contains Unicode characters that cannot be transcoded. To prevent this, all target fields must also be Unicode and any fields they are moved to, and so on. | |||||||
New & Revised API'sNew Widget fieldsNew TRAP control |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > | APPX 6.0.0 Features
OverviewThe most significant change in this is release is support for a Unicode data type. From Wikipedia: Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The latest version contains a repertoire of 136,755 characters covering 139 modern and historic scripts, as well as multiple symbol sets. The Unicode Standard is maintained in conjunction with ISO/IEC 10646, and both are code-for-code identical. The addition of Unicode will you to develop APPX applications to run in any language. 'UNICODE' is a new storage attribute for Alpha and Text fields. You can change this attribute, restructure the file, and APPX will accept Unicode data in that field. Although you may see some references to a NATIONAL encoding type, it is not implemented in this release. When storing the data in APPX/IO, APPX uses the UTF-32 format, which requires 4 bytes for each character. When printing Unicode data in a non PDF report or reading/writing a stream file, APPX uses UTF-8. The UTF-8 standard uses 1 to 4 bytes per character. It was designed for backward compatibility with ASCII. The first 128 characters of Unicode, which correspond one-to-one with ASCII, are encoded using a single octet with the same binary value as ASCII, so that valid ASCII text is valid UTF-8-encoded Unicode as well. Printing Unicode characters in a PDF document is handled by the inclusion of the DejaVu Font library. This is an open source font collection designed for greater coverage of Unicode, as well as providing more styles. Since there are over 1 million possible Unicode characters, not every font family can print all the characters. You may need to source a different font library if your target language is not fully supported in DejaVu. APPX provides a way for you to override the default fonts. The fonts will be embedded in the PDF document and will display regardless of what fonts the user has on their desktop. Transcoding is the act of converting to or from Unicode. APPX handles this for you automatically, however, if you move a field containing Unicode data to a non Unicode field and the Unicode data cannot be transcoded to the target encoding, a runtime error will occur. This is similar to an overflow condition with a numeric field. We do not want to simply continue, as you have lost data in this case. There are also APIs for transcoding that give you more control. Various fields in APPX System Administration and Application Design have been converted to Unicode. Because of this, System Administration, Application Design and all data files are incompatible between Release 6 and any earlier release. A migration tool is provided to move the System Administration and Application Design files to Release 6.0. All key files must be rebuilt as well. See Upgrading an Existing installation for the details. Unicode is not accepted everywhere in the System Administration or Application Design files. Only those fields that are 'user-facing' have been changed. For example, Printer Descriptions, Form Descriptions, Field Descriptions, Field Column Headings, are all Unicode. Fields the end user does not see, such as Process Names, File names, etc, are not Unicode. To check if a field accepts Unicode or not, just press Help (F1). The help text will tell you if it is a Unicode field.Application Design ConsiderationsAll --- TEMP fields are now Unicode. This may have an impact if you are PASSing a TEMP field to an internal or external routine or program. If it isn't expecting Unicode, that may be a problem. A number of --- WORK RAW xx fields have been added, you can use these in place of --- TEMP if you need a non Unicode field. The new API's have been enhanced to work with Unicode fields, but the older ones have not. You may need to update your applications to use the newer API's, ie, use --- .STREAM OPEN/READ/WRITE instead of --- STREAM OPEN/READ/WRITE. Since Unicode fields require 4 bytes per character, the maximum size of an Alpha/Text field is now 1M (1,048,576) characters. The maximum record length for an APPX/IO file remains at 32K, but is not limited when using Oracle or MS SQL Server. Unicode is not accepted in ILF statements. If you must refer to a Unicode character in ILF, you can use the \uxxxx syntax. For example, to use the ❤ symbol you could use:SET --- TEMP 1 = \u2764where 2764 is the code point for the ❤ symbol. If a Group field contains a Unicode field, you cannot SET that group to or from an Alpha field. The process will give an 'Invalid Storage Type' compile error. Similarly, Unicode fields cannot be set into a Group field. This may have an impact on your applications if you are using --- TEMP fields to move data to/from a group, since all --- TEMP fields are Unicode. You can use one of the new WORK RAW fields instead. If a group field contains a Unicode field, it can only be moved to/from another group field. There are additional considerations discussed in more detail at the end of the Upgrade instructions. Changes in Release 6.0Here is a list of the changes in Release 6.0:UnicodeYou can now specify a 'Unicode' encoding type for Alpha and Text fields. This is in the Additional Attributes dialog box: The default encoding type is RAW, which corresponds to US ASCII (ISO-8859-15). If you are not using ISO-8859-15 as your default encoding, then set the APPX_RAW_ENCODING environment variable to tell APPX which encoding you are using. Unicode fields must be aligned on a 4 byte boundary. When the file is processed, APPX will check this and warn you if you need to add alignment bytes. Simply add a simple alpha field of the designated length in front of your Unicode field. If you have more than one Unicode field in your file, you may have to add multiple alignment bytes. If the new record length is > 32K, you will get a warning from the Data Dictionary compiler. If you are going to store this file in Oracle or SQL Server, you can ignore this, however, the 32k limit still applies to APPX/IO files.New & Revised API'sNew Widget fieldsNew TRAP controlNew flag to suppress PDF Dialog boxJump to process from audit historyJump to O/C from Button GANew Font type ResourceNew utility to check for dup shortcuts0LA Output STANDARD MOD LOG and 0LA Input CONFIRMATION (END) in 0LC and can be hookedBugs FixedKnown IssuesAPPX/ODBC is not available yet PerformanceComments:Read what other users have said about this page or add your own comments.-- JeanNeron - 2018-02-20
|