neo
neo copied to clipboard
neomjs
The application worker driven frontend framework
Right now, the windows builds are running fine inside the framework scope, but they fail silently when running inside a neo workspace (`npx neo-app`). The problem seems to be the...
**Describe the bug** See screenshot **Expected behavior** The config should be created in the correct place (sorted alphabetically inside the `getConfig(..)` (like on MacOS) instead of **at the very top...
a new build program to automatically generate configs would be sweet. after picking a config name, the program should ask (multi-select) to generate the 1. beforeGetConfig() 2. beforeSetConfig() 3. afterSetConfig()...
in case a user generates any class extending `component.Base`, we can ask to create a related `controller.Component` and `model.Component` as well, which get hooked into the just generated view file.
In case a user wants to generate a `data.Model`, we can then ask a question to automatically generate a `data.Store`, using the just generated model.
Inside the main thread, we get `Neo.workerId = 'main'` and this feels odd, since a main thread is not a worker. threadId feels more clear.
Demo Apps (e.g. Helix) should not be part of the ´API´ documentation, but be added to ´Examples´. The user Apps should be inside a tab ´Apps´. Currently all Apps are...
**Is your feature request related to a problem? Please describe.** I would prefer to have the information sorted in a different way.  https://www.imgbly.com/ib/9IfnbtTdet **Describe the solution you'd like**...