NovaOS

 No, we aren't. NovaOS is just moving RoturTW to an external comprehensive application. As so many people like to use NovaOS's RoturTW Services without having to go through a NovaOS installation. OrionClient is essentially running a headless NovaOS session underneath to represent a full RoturTW Client. Though OrionClient is not saving anything permanently or running a filesystem, window manager, or process manager, as NovaOS does. OrionClient uses a basic hosted static application with direct communication (not NTX ), like what old NovaOS apps used to do. OrionClient provides no sandboxing for its applications, which is justified because it does not provide sideloading functionality.

Claw for Nova : Major stability and feature updates. Read-Write System : Handles much larger files with ease. Settings App : Advanced pages and deeper control. nova.css : Adds border-radius , gap spacing, and sizing controls. Improved standard. Media Player : Improved file format support, chunked streaming. Files App : Optimized for mobile. "Open as text" feature. Subfolder UI cleanup. Better folder handling. Huge stability improvements. System-Level : Right-click close window. Improved app launch stability. NTX API lets apps integrate deeply. OLP revamped with new Handlers. Handlers : NTX-based one-liners to trigger system features. App Permissions : Granular app control. Backups : Download full account state with one click. Works across devices. Themes : Stable syncing across all windows. Expanded theme store. Concentric radius UI standardization. Store App : Sections for themes and my apps. Au...

This is a part of the Permissions system. The NTX System "Project Avocado", as we used to call it, is the most interesting and ongoing project in the new NovaOS. The idea is simple, a unified system that gets added into applications while they're running so that they have the ability to talk with the NovaOS system - even when being fully isolated and sandboxed. The permissions system relies on this single system a lot, it is the underlying state of all app-os communications. Everything an app wants to do is available within this one system. Basic structure It's a javascript class , with a ton of functions inside. That's it. But looking again shows that all the functions are grouped with categories. The categories are named "fileGet", "dir", "olp" etc. Adding to your app Using it is as easy as including a nova-include with "ntx" in the content. The class will be added to your application context's myWindow object. Remembe...

Nova Design is a part of the nova ecosystem that studies user interface design and its impact on various hidden aspects such as emotion, addictiveness, experience etc. The Goal of the study is to understand and implement natural, cognitive senses that we all share in regular user interface design. Studying user experience is crucial , every design choice changes how a user uses and comments on a system. Studying complex human emotions are hard , but through cognitive and easily observable patterns in character can be easier. This will allow Nova Design to create data on how much it matters and if it's worth efforts. Even though Nova Design isn't yet perfect , each element of the UI should be refactored and studied through multiple perspectives. Choices and intentions of users could also change how someone looks at UI. Cultural changes change how users feel about UI , this in fact can create varied feelings on different elements and colors. Without hindering the UI for differen...

There are several ways to access NovaOS. Here is a list of ways on how: The public version The public version of NovaOS is a version that is intended for public use . This includes use of the webpage hosted in GitHub Pages. The public version has this link:  https://adthoughtsglobal.github.io/Nova-OS/ There is a redirect  site that links to this public version hosted at  https://novaos.netlify.app/ . But it is being slowly discarded from usage. The development version NovaOS Experiments is a project under adthoughtsglobal  that is dedicated to test and implement new features in NovaOS. See a whole list of Experiments here .  The development version or usually called as the 'dev' version ('ondev version', 'dev ver', 'experiment version' 'nova flags version'), is not intended for public use and may cause issues.  This includes use of the webpage hosted in GitHub Pages. This is due to the direct pushes of updates that are being made and are not p...

steps to use dev version if you have saved data on old version: open dev version if the boot is 'stuck', click on erase everything at the bottom reload steps to use dev version if you have saved data on old version and you have access to the public version: open your normal, public version open settings app click on 'storage' on the sidebar scroll down and click on 'Erase device' steps to remove all data for the domain using the inspect window open your normal, public version execute this script on console: localStorage.removeItem('todo'); localStorage.removeItem('magicString'); localStorage.removeItem('updver'); localStorage.removeItem('qsets'); let indexedDB = window.indexedDB || window.mozIndexedDB || window.webkitIndexedDB || window.msIndexedDB || window.shimIndexedDB; let dbName = 'trojencat'; try { let deleteRequest = indexedDB.deleteDatabase(dbName)...

As we all know, novaos is a really complex webapp. Its insides are multiple layers of documents and scripts that work together to create an ecosystem for you to strive. Starting with the most basic aspect of Nova, the kernel. The NovaOS kernel Unlike an ordinary kernel, NovaOS has a 'kernel' that deals with how you manage windows and open apps. But for the time being, what you have to understand are 3 basic things Windows in novaos are separate document fragments or child documents. The code ran in the child document is injected by NovaOS on initializing the new child document. The windows, after the initialization, does not have anything to do with the original file unless it's compelled by a script to do so. The kernel is really cool, the kernel comes with a lot of stuff, like openers, opener protocols, file opening systems, window management systems and a whole lot, which we will discuss later! But now, to actually run an app, we need to store the app somewhere, so we go...