• Inhalt wirkt sehr gequetscht: Padding der Tabellenzellen erhöhen
• Border-Radius von 5px auf die oberen beiden Ecken der Tabelle setzen
• Sliderelemente der Tabellenspalten dünner einstellen (1px?)

1. Actually take list of property keys from class instead of instance.
2. Display correct origin in 3rd column.
3. Make numbers editable.
4. Better representation of sets/maps.
5. Highlight stuff in matching colors.

IS

Tables are implemented to a minimum, using primitive html table elements without any styling at all.

SHOULD

• Tables should look like licked
• Columns should be resizable
• Clickable items should be indicated so
• Per column, besides the existing text renderer function, a renderer component can be specified
• Maybe remove the margin around the tables

Note

Do not use css grid layout so it can still run on toasters!

Nachdem ein "ServiceWorker" registriert ist und der PWA-Support somit vollständig ist, sollten Assets im Sinne von Icons für die installierte App vorhanden sein.

IS

Each entity is a JavaScript object with property IDs as its keys.
Static and user entities are identified by a dedicated boolean property on each entity.
Properties/fields are defined by instances of the property class.
Property values can be either native, reference or getter.

SHOULD

Entities are arrays of numbers.
The meaning of each item is defined by the fields list defined for its class.
Non-numerical values are stored in separate arrays per type with a pointer in their place in the entity.
When saving/exporting user entities, only non-static values are exported, after deduplication.
Static entities will be determined by their IDs, where user entities begin at 1024.
Properties are simple classes extending their type class.
All (non-static) objects have reference counters. When it reaches 0 and the object has no label, the object is deleted.
Property values are always just simple numbers internally, they are native/reference depending on their class. Classes can have methods, including getters/setters.

REASON

Arrays of numbers take much less space in JSON and are stored more efficiently in memory. There is no hashmap lookup happening anymore but only finding the field index for dynamically accessed properties. Static classes' properties can be accessed by constant indexes known at compilation time as before.

Es wäre für einen Nutzer angenehm, wenn die App sich mit einigen Tasten steuern ließe.
Beispiele hierfür sind ein ESC-Tastendruck, um Menüs und Popups zu schließen oder Pfeiltasten, um zwischen Untermenüs zu navigieren (Liste hier ist ja beliebig erweiterbar :)).

IS

The entities are stored in a global, plain map.
When editing entities, the view is not updated automatically.

SHOULD

There should be a way to easily show and update entities, updating the view automatically on modifications.

Momentan können Spalten nur per Maus/Touchpad in ihrer Breite angepasst werden.

Mit dem Berührungsbildschirm soll das auch gehen.

IS

When opening an object view, the object and its properties are shown as a tree.
Only directly assigned properties are shown.
The object menu is accessible via the tree's root element.

SHOULD

Objects should be displayed as a table of properties with these columns:

1. Property label
2. Property value
3. Property origin

All available properties should be shown.

When a property is set directly on the shown object, the origin column should be empty. Otherwise, the object from which the value is inherited should be referenced.

There should still be a (smart) way to access the object menu.