Difference: Appx550FeaturesAppDesign (9 vs. 10)

Revision 102020-04-02 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="Main.Appx550Features"

APPX 5.5.0 Features - Application Design

This page describes the new features in Application Design in Release 5.5.0. Note that the features that include larger screens require a row/col setting of 35 x 144. If you are running at a lower screen size you will get the old versions of the screens. NOTE: The .ENV GET SCREEN SIZE API was returning a row count three rows higher than the actual row setting. This bug has been fixed, so if you were manually compensating for this by subtracting 3 from the returned value, you no longer need to do this.

Changed:
<
<
>
>
 

Data API

The Data API provides a set of tools you can use to have your APPX applications respond to web based queries. See this page for installation and configuration.

Line: 74 to 74
 The contents will vary based on the type of process and type of frame or image. Changing any value from the default will turn on the 'AA' indicator at the Frame or Image level.

Documentation in HTML format

Changed:
<
<		Documentation can now be entered and displayed in HTML format. When you click the 'Documentation' button you will see a display similar to the following:
>
>		Documentation can now be entered and displayed in HTML format.
 
Changed:
<
<		documentation.png
>
>		To convert your existing Documentation to HTML run the 0AD job CONVERT DOCUMENT TO HTML:
 
Changed:
<
<		The 'Text Entry' button replaces the toolbar with a simplified toolbar that only supports plain text. If you need to maintain compatibility with plain text you can use this button to prevent HTML from being entered.
>
>		convert_html.png
 
Changed:
<
<		The HTML editor requires you to use the mouse to advance, and some designers find that annoying, so the automatic presentation of the Documentation screen when adding new objects has been turned off. If you want to enter Documentation while adding, you can use the Alt+D shortcut to call up the Documentation screen. If you want to restore the previous behaviour, set APPX_DOC_ON_ADD to any non blank value.
>
>		This can be invoked from within Application Design in any Application. An explanatory screen will be presented and you can choose to continue or cancel. If you continue all documentation in all applications will be converted to HTML. Since HTML can be longer than APPX plain text some documentation might be truncated. A report will be produced identifying these. This step might take some time to complete depending on the amount of documentation in your applications.
 
Changed:
<
<		To convert your existing Documentation to HTML run the 0AD job CONVERT DOCUMENT TO HTML:
>
>		If you have some Applications that you do not want to convert, then you can either:
  • Temporarily delete them from the Applications file. This will not delete the Application itself and you can add the record back after conversion
  • After the conversion restore the DOCUMENT.* files from backup for those applications
 
Changed:
<
<		convert_html.png
>
>		When you click the 'Documentation' button you will see a display similar to the following:
 
Changed:
<
<		An explanatory screen will be presented and you can choose to continue or cancel. If you continue all documentation in all applications will be converted to HTML. Since HTML can be longer than APPX plain text some documentation might be truncated. A report will be produced identifying these.
>
>		documentation.png
 
Changed:
<
<		Column headings & more in table widgets
>
>		This input will default to either the HTML Editor or the plain text editor. It does this by looking at the existing text to determine if it is HTML or not. If you have run the conversion step above, it will default to HTML. If you have not run the conversion, it will default to the plain text editor. If you are adding new documentation, it will check existing documentation to determine if you are using HTML or not, and default accordingly. If this is a brand new application with no existing documentation, it will default to HTML. This approach allows you mix and match documentation format for situations where you have a mix of character and GUI applications.

The 'Text Entry' button switches to the normal, plain text Documentation entry screen. This will strip all the HTML from your text. It only preserves the line breaks and non-breaking spaces. Entities will be converted, if possible. On the plain text screen the button will show 'HTML Entry'. This will convert the plain text to HTML and display the HTML editor. APPX hard spaces (the underscore character) will be converted to , line breaks converted to <br /> and a pair of line breaks converted to <p>.

The HTML editor requires you to use the mouse to advance, and some designers find that annoying, so the automatic presentation of the Documentation screen when adding new objects has been turned off. If you want to enter Documentation while adding, you can use the Alt+D shortcut to call up the Documentation screen. If you want to restore the previous behaviour, set APPX_DOC_ON_ADD to any non blank value.

Column headings & more in table widgets

  Column headings and cell properties can now be specified in the Table Source. There are 2 new buttons: Column Headings and Cell Properties. Column headings allows you to explicitly set the heading you want on a column as well as some formatting information. Cell properties allows you to set the properties of the cell. Both of these can be manipulated at runtime by updating the Widget file.
Line: 208 to 218
 

New API’s

A number of new APIs have been added:

Changed:
<
<
>
>
  • Set file specifications - https://wiki.appx.com/wiki/bin/view/Main/0LASubrFileSetSpecs
  • Archive security codes - https://wiki.appx.com/wiki/bin/view/Main/0LASubrUtilSecrSave
  • Restore security codes - https://wiki.appx.com/wiki/bin/view/Main/0LASubrUtilSecrRest
  • Convert HTML to text - https://wiki.appx.com/wiki/bin/view/Main/0LASubrConvertHTMLtoText
  • Send an Email - https://wiki.appx.com/wiki/bin/view/Main/0LASubrUtilEmail
 Sending an email relies on the public domain mail client 'mutt'. If you do not already use a command line emailer you will have to install 'mutt' on your server. If you have your own command line email program you can hook the APPX routine and use your own. Instructions for this are on the wiki.

Change Password Process for APPX Authentication

Line: 253 to 263
  We welcome any suggestions on improving this interface.
Changed:
<
<		-- Jean Neron - 2020-02-12
>
>		-- Jean Neron - 2020-02-12
 

Comments

Changed:
<
<
<--/commentPlugin-->
>
>
<--/commentPlugin-->
 
META FILEATTACHMENT attachment="MWE_Toolbar.png" attr="h" comment="" date="1581522444" name="MWE_Toolbar.png" path="MWE Toolbar.png" size="15735" user="JeanNeron" version="1"
META FILEATTACHMENT attachment="MWE_Right_click.png" attr="h" comment="" date="1581522577" name="MWE_Right_click.png" path="MWE Right click.png" size="42768" user="JeanNeron" version="1"
View topic | History: r20 < r19 < r18 < r17 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback