-
Notifications
You must be signed in to change notification settings - Fork 209
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
Custom UI for modules #87
Comments
Hi, Chinmay - i guess that we should try to prototype this. What if we build one around the |
But also -- if you can list out some of your questions to narrow this down, that's also a good next step. Thanks!!! |
This was implemented in #92 Do you think this is complete or can be improved upon? If it looks complete, I shall close the issue |
This looks super. Close!
…On Aug 20, 2017 8:56 AM, "Chinmay Pandhare" ***@***.***> wrote:
This was implemented in #92
<#92>
Now modules have an info.json which spcifies what inputs they take, their
defaults, their min/max values, etc. Documentations also added. This can be
used to create UIs!
Do you think this is complete or can be improved upon? If it looks
complete, I shall close the issue
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#87 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ_3OO3I-m1UQikmJ2OJBGGaaEcNBks5saCz5gaJpZM4OutqO>
.
|
We discussed on #62 that modules should provide their own basic UI. This can be done by creating a wrapper UI module which requires in the actual module and also contains the UI elements.
What do we mean by a basic UI? A basic UI could just mean
<input type="text" />
elements for all input fields or a slider as in FIsheyeGl. It's not very clear as to what should be done - or what the purpose is.What are our expectations from the module in terms of UI? What UI Elements should it return? Ideally, Image Sequencer is supposed to have multiple steps, and not one entire page for just one step (Which has been the case for the demos I have recently made).
This is why I thought that the module can return the elements that it wants, but again the positioning and styling will highly depend on the implementation (one-step, multi-step, multi-image, et cetra.) , so it is really hard to expect the module to return a fit-all UI which can simply be injected into the front end code.
I think still a little clarity is needed on this front.
The text was updated successfully, but these errors were encountered: