wizard is a rendering framework for serving %make wizards to the user.
This code still needs some production work to be fully functional, but the idea is:
While browsing any path (for instance, /~met/home/tasks), the user chooses wizard from Sky's renderer/overlay dropdown. An HTTP request is sent to /wizard/~/~met/home/tasks.
%wizard, which is bound to the /wizard Eyre endpoint, receives this request. %wizard responds to the HTTP request with a simple page containing a dropdown box of options.
The user chooses an option, for instance, %task-wizard. An HTTP request is sent to /wizard/task-wizard/~met/home/tasks.
%wizard receives this request, sees that the second iota specifies a wizard, and grabs that manx from the (map stud manx) it has in its state. It responds to the HTTP request with this manx.
This manx contains a UI that helps the user create a child. This gets wrapped up into a made and sent to /wizard/task-wizard/~met/home/tasks.
%wizard receives this post request, makes the shrub, and redirects the user to /tree/~met/home/tasks/child.
This (map stud manx) will need to get populated somehow, of course. Pokes could work, and seeing how software distribution works could be illuminating for the specifics here.
Additionally, similar to tree, this would be even better if we could auto-filter down to only types of kids that are allowed to be created under a given shrub using a %z root dependency.
wizard
is a rendering framework for serving%make
wizards to the user.This code still needs some production work to be fully functional, but the idea is:
/~met/home/tasks
), the user chooseswizard
from Sky's renderer/overlay dropdown. An HTTP request is sent to/wizard/~/~met/home/tasks
.%wizard
, which is bound to the/wizard
Eyre endpoint, receives this request.%wizard
responds to the HTTP request with a simple page containing a dropdown box of options.%task-wizard
. An HTTP request is sent to/wizard/task-wizard/~met/home/tasks
.%wizard
receives this request, sees that the second iota specifies a wizard, and grabs thatmanx
from the(map stud manx)
it has in its state. It responds to the HTTP request with thismanx
.manx
contains a UI that helps the user create a child. This gets wrapped up into amade
and sent to/wizard/task-wizard/~met/home/tasks
.%wizard
receives this post request, makes the shrub, and redirects the user to/tree/~met/home/tasks/child
.This
(map stud manx)
will need to get populated somehow, of course. Pokes could work, and seeing how software distribution works could be illuminating for the specifics here.Additionally, similar to tree, this would be even better if we could auto-filter down to only types of kids that are allowed to be created under a given shrub using a
%z
root dependency.