floralsoda / portos Goto Github PK

Could have some kind of caching, but need to evaluate if this conflicts with default values and statics

PortOS should provide a module that simplifies and provides more powerful capabilities involving peripherals, called the Devices module. It should be able to handle defaults, automated syncing, networking, routing, forwarding, turtle peripheral juggling, validation and other such components.

PortOS is big and clunky to carry around, and sometimes you want to write an app that's unrelated to PortOS but contains certain bits and pieces of it.

Convert complex, generalised systems to more specialised frames for small applications
An interface that allows users to manually define the stand-alone, shrunk version
Should detect required modules and include those, too
"don't optimise" attribute that prevents the tool from optimising and simplifying that code
Optimiser that discards unused properties and utilises common patterns to create more specialised code

A serialiser that can handle loops and recursion, as well as options and different formats. Version Agnostic

The turtle component for PortOS should only be downloaded and activated if it is loaded on a turtle, or if the user specifically requests the turtle component.

It should handle task tracking, GPS, inventory management and extension, peripheral juggling, fuel management, path finding and other important turtle functions.

Rendering on CC is quite limiting, as you only have 16 colours to work with and have to carefully manage your colours if you're to change them.

The color palette API should implement RGB color, screen color tracking and automatic palette replacement and switching, making way for new colours when old colours aren't being used. Return error if more than 16 colours are attempted at one time.