Presently we have two demo pages in the repo to demonstrate setting up a LocusZoom plugin with only a slight variation in the layout. Moving forward we're going to be supporting an increasing amount of flexibility in the layout with only one configuration baked into LocusZoom.DefaultLayout, relegating all that flexibility to only the API Reference.
By building a dynamic demo page that has form elements to tweak the layout (which evolves with the library) we'll not only have a tool to demonstrate the level of variation LocusZoom affords developers but also have something we can stand up on locuszoom.sph.umich.edu to highlight current LocusZoom library development.
A minimum viable product might include:
A couple of big text areas showing the current layout and state objects
Form controls to submit any changes to the layout/state and apply them to the plot
A link to the API reference
It may be wise to avoid creating a big dynamic HTML form without first figuring out a way to model all layout possibilities in some sort of portable data structure which the library can also use for layout verification. Otherwise all new layout rules will need to be implemented twice and there will be a high risk of divergence between the library and the layout builder demo.
Presently we have two demo pages in the repo to demonstrate setting up a LocusZoom plugin with only a slight variation in the layout. Moving forward we're going to be supporting an increasing amount of flexibility in the layout with only one configuration baked into
LocusZoom.DefaultLayout, relegating all that flexibility to only the API Reference.By building a dynamic demo page that has form elements to tweak the layout (which evolves with the library) we'll not only have a tool to demonstrate the level of variation LocusZoom affords developers but also have something we can stand up on locuszoom.sph.umich.edu to highlight current LocusZoom library development.
A minimum viable product might include:
It may be wise to avoid creating a big dynamic HTML form without first figuring out a way to model all layout possibilities in some sort of portable data structure which the library can also use for layout verification. Otherwise all new layout rules will need to be implemented twice and there will be a high risk of divergence between the library and the layout builder demo.