moware 11 2024.23 (turku100)

various turku bugs fixed

All known bugs regarding turku running on the first 100 clients were fixed with this release. 👉 hopefully no new issues introduced .. 💥 💀 🔥

SDI turku support and moware url command extensions

developer preview of SDI web applications with correct url handling

moware 11 2024.22A (optim++)

bugfix release for h2forms

moware 11 2024.22 (optim)

2024.22 is an optimized moware

Turkuforms

Ask to terminate other app instance in case single instance mode is activated

Using Material Icon Font Outlined 24

H2forms

Using Material Icon Font Outlined 24

Keyboard Optimization

Former versions of h2forms have immediately shown the custom keyboard on zebra devices when some enabled, numeric delegate was present in a form. As a consequence, the keyboard took up half the screen space in almost all form scenarios.

This behaviour is optimized in this version of h2forms. The custom keyboard is not shown, in case the focus is on a scanable delegate, expecting the user to use the scan hardware trigger button. In order to show the custom keyboard in these cases if need be, the user can simply touch the delegate.

Those user touch events on delegate forms are now reported on port J in the reqLog field and the searchable text 'keyboardtouchrequest'. However, all touch events on delegates are reported not just those intended to show the keyboard.

You have to use OptimKeyboard = "true" in the AppFactory to enabled this feature.

All platforms

New window title handling

‼️ ‼️ Apply the refactoring script for moware 11 2024.22

The command window title comes with three options now.

• add on: add some information to the cmd name or the action label name
• overwrite: overwrite title with some information
• overwrite_predecessor: overwrite title with some information, even if command is executed as successor of another cmd.

Bring parent tab in focus, when command running as GO / GO_MODAL or SEARCH is terminated.

moware 11 2024.21 (bugfix)

Bugfix release

Turku fixes

Empty scopes are allowed on all platforms

moware 11 2024.20 (alert)

Support for single line statements on switch

The new status switch will automatically use a more compact editor when the case consists of only a single statement. If an empty statement is added, the switch will count that as two statements, thus switching to the multiline editor. Additionally, an Autocompleter adding all remaining stati to the next case was impelemented.

Fallback close message in case browser window is closed

In case the user closes the browser (e.g. via window tab or by X in the browser tab), turku will force a confirmation window when graph owners with sessions to commit are still open.

This is indeed a fallback mechanism supported by browsers. A styling in not possible.

💫 additionally: bugfixes and navigation preserves username param over lifecycle 👯

moware 11 2024.19 (switch)

FOCUS FORWARD 2

Use the "FOCUS FORWARD 2" option in grid layouts to transfer the focus to an element in the grid. In a backward compatible manner, the focus is requested on the first element in a grid. The new option allows you to request the focus on another element.

new STATUS SWITCH

The new status switch supports advanced checks, folding and better readability. It is fully backward compatible. When a 'default' branch is given, the switch statement behaves analogous to the former implementation.

However, when the default is not present, the status switch will check that a case branch is present for all possible stati. Additionally, a case branch can handle more than one status. Each status should be mentioned only once.

The new status switch will not contain a default uppon instantiation. If a default is needed, an intention is available. As can be seen, an autocomplete is also available.

There is a migration script available to adjust existing status switch statements. The migration script is MANDATORY. Additionally, there is a script showing all status swtich statements in the project. One might adjust/delete the default branch manually.

TURKU FIXES

• accept username as param
  adding ?username=XXX to the /login will use the given username instead of the client ip
  

• various known bugs

moware 11 2024.18A (erdtorpedo ++)

Bugfix release for the 2024.18

reversed manmap nullkey checks on loading

fixed ReferenceDelegate Issues - scope check still in place

moware 11 2024.18 (erdtorpedo)

The post croatian holiday plugin

NOT FOR PRODUCTIVE USE

(1) improved processing speed of job producer

implementation details in producer were changed to decrease the producer runtime. The first spikes stem from the previous implementation, the later ones from the new one.

‼️ as always, be susceptible for a problem of this new implementation in case issues with a job are observed ...

(2) empty scopes on ref. delegates

Empty scopes are handled analogous on all platforms. FX8, H2Forms and TurkuForms won't crash but throw an Exception (which will get reported on portJ) in case the scope ist not set. However, if the ref delegate is in a read only state, a scope is not necessary. A scope is only needed, in case the user can edit the reference.

(3) manmap checks for entities with 'null' key when loading with where

Former releases simply ignored rows with 'null' as key (null, int 0 or string '' in key column) when loading entities with a where {}. From this release on, manmap will report this suspicious rows with 'null' as key with an exception. Manmap always needs unique keys (whereby null, 0 or '' is not allowed).

(4) revised URL handling in turkuforms

Quite complicated url handling to get rid of the <>/home postfix for the application instance. Now, to open the app directly, use <>/login. That will log in the user and redirect to <>/

(5) various bugs and minor improvements ...

(6) handling of selction(s)/push(es) in FINAL_OK and FINAL_CANCEL of commands

When applying the successor pattern only selection(s)/push(es) of the predecessor were taken into account for the parent comand. This changes with this plugin. In case selection(s)/push(es) were given by the predecessor command, the predecessor selections are relevant and forwarded to the parent. In case NO SELECTIONS ARE SPECIFIED in the predecessor, the successor selections are forwarded to the parent (if some present).

‼️ These change in behaviour might not be 100% backward compatible. It might result in unwanted selections in rare cases, when existing code specifies selections in the successor, but not in the predecessor. Additionally, the parent has to be sensitive objectwise for those pushes.....

moware 11 2024.17 (np)

support for dynamic named parameters in custom sql

As can be seen in the screenshot above, one can simply pass an array of NPs to the MapUPDATE / MapSELECT to declare a set of named parameters in the query.

enhanced support for the 'CheckAlsoPredecessorDuplication'

Dataux will check for a command already running when executing a successor action resulting in the same GO. Right now, this is 'under test' in the eFWWS.

moware 11 2024.16 (tb)

Some turku bugs

• Auto Select Item in Reference Delegate, in case only one option prevails
• Some column lines for tables
• Multiple cmd's in one layout in compact mode
• connection info + error reporting
• Copy CSV within table additionally on crtl-c

Color within turku tables

Detect running Predecessor Command with same parameters

The 'CheckAlsoPredecessorDuplication' will let moware check for prdecessor commands with same parameters already running. In case one is found, the tab running the command will get the focus, instead of starting a new command instance.