+1 Whilst I can't see this being used by someone who's experienced with creating YAML blueprints, I think it would add a great 'wow factor' to product demos. It'd also be a great way for someone new to Brooklyn to learn how to compose YAML blueprints by building something using an intuitive drag-and-drop interface, and watching how the corresponding YAML is built up. Folks will probably eventually switch to just writing YAML directly, but this would be a key tool in that crucial initial phase where someone is just getting to know about the various Brooklyn concepts
Cheers M On 25 June 2015 at 17:37, Thomas Bouron <[email protected]> wrote: > Hi devs. > > I'm sure it happens to you all the time to jump here ( > https://brooklyn.incubator.apache.org/learnmore/catalog/index.html) to > check which entities are available along with theirs config keys, sensors, > etc. Would it be great to have some sort of nice GUI editor to compose > blueprints on the fly, directly from Brooklyn which would include entities > shipped with Brooklyn + your own Brooklyn catalog? > > Following this idea, I took the liberty to put a quick wireframe / workflow > of how I see this editor working. It's available here: > > https://www.fluidui.com/editor/live/preview/p_VTRECWVgxa6xOSKclTsTSI0BU5kNzz98.1435239663172 > > To explain a bit more in details, the preview is interactive. You can click > on the icon on the top right to display the clickable elements and notes. > Basically, we start with a "Same server Entity", then a "Vanilla Software > Process", then you can go down to the configuration. You can also switch > between the WYSIWYG and YAML views. I think we should probably start with a > one way synchronisation (meaning editor -> YAML) because a two way seems > really complicated. One other alternative would be to have a split screen > between editor and generated YAML but that raise the question of how to > present this editor? Doing a split screen won't fit within a modal. > Finally, the green and red colours are just a visual way to inform the user > that this particular entity is properly configured / valid or not. > > This is just an example, I cannot do the entire thing with my free FluidUI > account (allowed to do only 10 screens) but hopefully, it should give you a > good overview. > > Questions / suggestions / comments are more than welcome! > > Best. > -- > Thomas > > -- > Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. > Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP > > This e-mail message is confidential and for use by the addressee only. If > the message is received by anyone other than the addressee, please return > the message to the sender by replying to it and then delete the message > from your computer. Internet e-mails are not necessarily secure. Cloudsoft > Corporation Limited does not accept responsibility for changes made to this > message after it was sent. > > Whilst all reasonable care has been taken to avoid the transmission of > viruses, it is the responsibility of the recipient to ensure that the > onward transmission, opening or use of this message and any attachments > will not adversely affect its systems or data. No responsibility is > accepted by Cloudsoft Corporation Limited in this regard and the recipient > should carry out such virus and other checks as it considers appropriate. > -- Martin Harris Lead Software Engineer Cloudsoft Corporation Ltd www.cloudsoftcorp.com Mobile: +44 (0)7989 047-855 -- Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. Cloudsoft Corporation Limited does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by Cloudsoft Corporation Limited in this regard and the recipient should carry out such virus and other checks as it considers appropriate.
