Web UI about jacquard HOT 5 OPEN

cc @danpalmer

from jacquard.

Can we get a quick list of features that we would want in a web interface (roughly sorted in priority, or grouped by possible releases), and check what we already have capabilities for in the API and what would need to be added.

On a more practical note, should the UI be

• in this repo?
• powered by the API, or server-side rendered?
• provided by a plugin?

My feeling is: almost entirely through the API (single page app style) and delivered through a plugin. This could however complicate the repo as the front-end would need all the associated stuff that goes along with JS development, so maybe a separate front-end focused repo would be appropriate?

Thoughts?

from jacquard.

One other question: what language/framework?

I feel like JS+React is pretty uncontroversial, but it might be nice to do it in Elm. Distribution compatibility will be less of a concern than with Python as we'd probably have to compile the front-end in some form anyway.

from jacquard.

Putting the web UI in a separate repo and using the plugin mechanism sounds like an excellent idea, because:

• Logical separation is good (it restricts us from calling into it from the main repo too),
• It keeps the jacquard install small on machines that don't need the web UI,
• It forces us to keep the plugin mechanism good.

Going to discuss this is more detail (plus choice of FE framework) with @danpalmer IRL.

from jacquard.

@danpalmer and I had a brief discussion about this IRL, and concluded that we probably want to build this as a client-side web app rather than classic server-side rendering with forms.

The latter approach would be simpler but the former approach means that we commit to making sure that the web API is high-quality, and gives us more flexibility on what we want to do with the UI.

from jacquard.