Draft UI concept for PoC (visual editing of HOT templates)
To get familiar with HOT templates editing you can read either the guide or more comprehensive specification. I've tried to address the most basic cases for now, leaving behind:
- parameters constraints editing (frankly speaking, I don't yet imagine how it should be done);
- editing the type of link between properties and parameters, outputs and attributes;
- joining the parameters into parameter groups (simple enough);
- supporting intrinsic functions like str_replace or replace_facade (should be visually edited at all?).
- comment lblanchard 18:40, 22 August 2014 (UTC) I’m missing where these widgets fit into the overall Horizon application. Will this integrate with the Stacks section where the Heat UI work has been done?
Adding a Resource entity
- test-comment smelikyan (talk) 14:22, 22 August 2014 (UTC)
- another test-comment Timur Sufiev (talk) 14:23, 22 August 2014 (UTC)
- comment lblanchard 18:40, 22 August 2014 (UTC) A few things...1) It’s not a very common practice to use right-click in a web UI and I think we should have these actions available always at the top of the canvas rather than buried in a right-click menu. 2) Should instance type be a drop down?
Adding Parameter entity
- comment lblanchard 18:40, 22 August 2014 (UTC) What are the interactions the user needs to take to create a connection on the screen? Do they have to select the resource in some way and choose an action? Do they drag and drop?
Enhancing Resource entity to display both Properties and Attributes
- comment lblanchard 18:40, 22 August 2014 (UTC) I like the idea of using an accordion for this design. Would this be sticky and remember the users preference if they refresh the page?
Adding Output entity
- comment lblanchard 18:40, 22 August 2014 (UTC) Again, how does the user create these connections?