Hi Hank,

as Lianja recently released a new version, can you give an oversight of what is ***not*** possible on the web/android/iOS clients but doable in the i86/AMD64 platforms in windows or Linux ?

Back when I was active in their forum, adding a full database engine to Android and iOS mobile clients was on the roadmap, even if main (biz+security) interest was more in centralized data storage. That was dropped when JS "cursor" became central point of interest as datasource, which might allow filtering or pagination to happen client side if wished for via object methods. Coincidence has it that this move mirrored change from native target implementation to Phonegap/Cordova, which already offers Javascript cursors from their idea of accessing data stores. Local munging of some filtered server side data sent into local "JS-Cursor" with pure locally persisted data was not on same level in Android vs. desktop client, SQL not even on the mobile map anymore.

Since then PWA gave more credit to offline functionality, which at least made local persistance standard to claim PWA status, even if done via JSON or key/value stores. Current mobile RAM, CPU and datastorage capabilities are well above Laptops sold a decade ago - which were well above the capabilities of machines we implemented vfp C/S applications for, so the poor, weak overloaded device story today is wrong.

Can you give an update on the current and planned mobile or client side datamunging on Android, iOS and perhaps web (if webassembly comes into play, even more scenarios make sense).

Their roadmap moves around and the milestone docs are overflowing with other infos...

tia
thomas

>Time moves on, how we do things changes, and some ideas last. Lianja has programmable metadata (json) attached to tables, fields, view, database. Some of it integrates (developer option) directly with the UI, giving uniformity with exceptions as wanted, throughout an application. The developer can have other information there, readable at runtime, for doing whatever.
>
>Hank