-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would like a KRL editor for apps #4
Comments
The child pico could be just a repository of KRL code keyed by the RID of each ruleset held. Editing could be done in the participant pico. The child pico would just receive changed code for a RID and provide the code given the RID. |
Decided to refactor the |
The So after introspection knows it has been installed, it needs to request the installation of the ruleset ruleset. |
Conversely, when the And will it be soon enough? There is a race condition. It depends which of the manage_apps and ruleset rulesets gets scheduled first. Hm. |
With this commit and installing introspection through the Manage Apps app and installing the ruleset app directly in the developer UI, it all works as it did before all the refactoring. |
With this commit, the pattern is complete. To have a byname app use an auxiliary ruleset that uses the main app ruleset as a module, the main app on installation installs the aux ruleset. The aux ruleset eavesdrops on the manage_apps event informing it that the main app is no longer wanted and uninstalls itself immediately. |
The last few commits, ending in this one, have prepared a form with the code of an app (base64 encoded) so that we can send an event to our pico. That event could open up an editor, primed with the current code of an app. In order to install edited code into our pico though, we'll have to spawn a child pico to contain and share the edited code. Then, we can install from a query to that pico.
We would do most communication with the child pico using family channels, but it would need a channel giving access to the query for external use.
The text was updated successfully, but these errors were encountered: