Skip to main content

Posts

Showing posts from September, 2024

Preparing for switching NovaOS versions

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)...

Inside NovaOS: how does it actually work?

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...