NicerApp WebOS Development Direction
Last modified : 2026-02(February)-17(Tuesday) 11:40:02
The yearly release stage of a new stable version of NicerApp WebOS is always Dec 1st - Dec 24th.
(2026) Compile AI image descriptions into the backgrounds collection.
(2026) Fix final bugs in said.by/me document handling.
(2026) Start on .../logic.databases/uDB-2.0.0, to be based on .../logic.databases/generalizedDatabasesAPI-1.0.0
Add MySQL and PostgreSQL to the list of supported database architectures (via .../NicerAppWebOS/3rd-party/adodb5), currently only couchdb is supported.
Add query routines in uDB to translate couchdb index names to index ids.
Add and test MySQL, PostgreSQL and 'filesystemDB' (fsDB) sub-modules to uDB (also on Window 11), as well as their interactions with the CouchDB part of uDB.
(2027) Start on .../businessLogic/filePhoenix.
(2026) Implement
rendering from HTML to an
image, to facilitate pre-fetches with image preview of specific pages on a NicerApp server by other websites.
(2026) Allow log entries (of console.log in the browser, and all database traffic and error messages on the server) to be logged to a different machine on the LAN than the main server.
(2026) Get na.m.log() to log per datetimeRangeBegin.milliseconds to datetimeRangeEnd.milliseconds into a database on the server, for use in /view/logs as the PHP data belonging to a PHP session_id().
Status : Completed javascript code, now needs revamped generalizedDatabaseAPI written and called, and db businesslogic PHP code.
(2027) Start work on a self-healer component for this WebOS, and a lot more Desktop OS level automated security to be installed via the
main Bash install script.
(2027) Write forum- and hashtag-features.
(2027) Rewrite the help system and comments system.
Write a notification API based on the VAPID browser API for this WebOS.
Write an in-app tutorial API for this WebOS.
Add the next set of animations to .todoList p, span, h1, h2, and h3 HTML elements (config data for which is to be visualized and interacted with in the theme editor by the way).
These will be javascript + PHP generated visualizations for SVG (animated) graphics.
I promise to bring you all some level of CSS animations in the generation config language :)
Maybe even a real translation of CSS animations (they're easy to parse), into SVG color and transparency animations! :D
(2028) Create a quantum + elemental + molecular editor data-structure and component as business logic code and an initially basic 2D (+3D ThreeJS?) user-interface.
Create a donations button (again, in collaboration with paypal.com), with monthly goal indicator, for the news app.
(2030) Create a bitcoin + stocks + bonds + indexes storage & trading app - with free to use accounts as well - in essence i'd need a bank company name. :-D
Add a checkbox in the Theme Editor to select backgrounds and stretch instead of tile them for any DIV.
-
rewrite the backgrounds analysis and automatic resizing routines;
- put all of the backgrounds in a DOMAIN_TLD___backgrounds dataSet with relative filepath (starting at siteMedia/backgrounds) and image size.
- let users search for backgrounds based on filepath, then save those searches in their account settings and make them viewable as photoalbums.
Upgrade the news app and vividDialog : add siteToolbarLeft functionality :
add a 'translate' dropdown box to the app-specific options menu
add French news sources
add/enable/disable/remove any URL to a combination of lists that are each given a name, which get stored in several database-stored dataSubSets (records/documents) inside a dataSet (table/couchdb-database).
the ability to assign specific 'theme' and 'sub-theme' settings to such a URL.
the ability to do keyphrase searches (perhaps later with 'or' and 'and' logic support) on the news content gatered, and paint that content with specific 'theme' and/or 'sub-theme' settings.
(putting all of this in siteToolbarLeft and the rest in the siteThemeEditor, and that those can already be shown at the same time, means you can edit *all* user-interface settings for *any* app or service on any HD screen or pad screen.
let vividDialog have a vividMenu, with vividButton icons that will lead to vividMenus and vividDialogs and vividDialogPopups, at the top-right of it's borders.
the contents of this menu should be defined in a <UL> structure (that can, if needed, get loaded with fresh content via AJAX), much like the vividMenu already is today.
Integration of payment platforms (as plugins) for paypal.com, creditcards, and the Dutch banking system iDeal.