Hi Hadrian, I did some proof of concept of my idea, you can find it on my repository [1], it’s very basic AngularJS application and it’s in a very early stage so it doesn’t include fancy things like Grunt neither tests and it’s pretty empty so just “npm start" to start playing. Anyway, this is how it looks just in case you don’t want to download my repo.
[1] https://github.com/adriannieto/incubator-brooklyn-material-gui <https://github.com/adriannieto/incubator-brooklyn-material-gui> Thank you! > El 23/7/2015, a las 11:27, Adrián Nieto Pérez <[email protected]> escribió: > > Hi Hadrian, > > I did some proof of concept of my idea, you can find it on my repository [1], > it’s very basic AngularJS application and it’s in a very early stage so it > doesn’t include fancy things like Grunt neither tests and it’s pretty empty > so just “npm start" to start playing. Anyway, this is how it looks just in > case you don’t want to download my repo. > > <PastedGraphic-1.tiff> > > [1] https://github.com/adriannieto/incubator-brooklyn-material-gui > <https://github.com/adriannieto/incubator-brooklyn-material-gui> > >> El 23/7/2015, a las 2:33, Hadrian Zbarcea <[email protected] >> <mailto:[email protected]>> escribió: >> >> Hi Adrian, >> >> The library is cool. I would like however to pick your brain on how exactly >> the concepts in brooklyn could be conveyed graphically. >> >> From my previous experience, this kind of representation occupies much more >> real estate on a screen (vertically at least) than one line in an editor >> that conveys practically the same information. While I totally agree that a >> visual representation is crucial, I am not sure this is the right one. >> >> To make it clear, this is not criticism in any way. I hope to encourage you >> and others who've seen orders of magnitude more ways to represent things >> graphically than me to bounce some ideas and come up with something great. >> >> Thanks, >> Hadrian >> >> On 07/22/2015 11:51 AM, Adrián Nieto Pérez wrote: >>> Hello all, >>> >>> I found an awesome drag & drop library for AngularJS [1]. It allows the >>> developer to define containers inside each drop zone dynamically among >>> with container types to avoid mixing incompatible components with >>> containers [2]. I think that this kind of implementation could work with >>> Brooklyn YAML philosophy. For example a Location container can has >>> virtual (SameServerEntity for example) and real entities (JBoss7Server), >>> but if you try the oposite it will not work. Also with a confirmation >>> toast the user will be able to input all required and optionals configkeys. >>> >>> What do you think? >>> >>> [1] http://marceljuenemann.github.io/angular-drag-and-drop-lists/ >>> <http://marceljuenemann.github.io/angular-drag-and-drop-lists/> >>> [2] >>> http://marceljuenemann.github.io/angular-drag-and-drop-lists/demo/#/nested >>> <http://marceljuenemann.github.io/angular-drag-and-drop-lists/demo/#/nested> >>> [3] >>> http://marceljuenemann.github.io/angular-drag-and-drop-lists/demo/#/types >>> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
