Thanks Raul.
I see your diagram shows a tree view for designing a blueprint (similar
to how the "applications" tab shows the runtime view).
I personally was more imagining a drag-and-drop graph of nodes + edges.
Dragging an entity onto the canvas would mean it gets added to the YAML
behind-the-scenes; creating an edge between two entities would trigger a
way to choose how they are connected (e.g. if connecting database to
app-server, then what configuration of the database is injected into the
app-server; the direction the line is drawn / dragged could indicate
which component is having the config injected into it perhaps).
I do see that containment could get fiddly. For example, a "dynamic
cluster" would contain as config an entity type for its members.
Similarly (but not exactly the same!) an entity could contain multiple
child entities.
---
The tree-view in your diagrams feels optimised for the "containment"
use-case, rather than for the configuration-injection / dependencies
use-case.
---
Also, let's not include this under the "applications" tab at the top.
That view is normally about viewing existing apps (except when the "+"
in the top-left is clicked!). We probably want an entirely different
section for blueprint definition.
The result (i.e. what is designed with that blueprint designer) could be
either added to the catalog or be used immediately for creating a new app.
Thoughts?
Aled
On 14/07/2015 10:47, Raul Canta wrote:
Hello,
I've looked over Adrian Nieto post and it looks that we had the same
idea using AngularJS and Material Designhttps://material.angularjs.org
<https://material.angularjs.org/>
Yes, it's about the drag and drop which Thomas Bouron proposed. I
tried to do a first design based on the mokcup Thomas did.
https://dl.dropboxusercontent.com/u/38051787/ApacheBrooklyn-Editor-Application.jpg
https://dl.dropboxusercontent.com/u/38051787/ApacheBrooklyn-Editor-YAML.jpg
I would like to get some feedback on the mokcups i did.
Thanks,
Raul C.
P.S. For the mockups I used the design guideline of the Apache
Brooklyn look-and-feel
On Tue, Jul 14, 2015 at 11:21 AM, Adrián Nieto Pérez
<[email protected] <mailto:[email protected]>> wrote:
My idea was to start the project during August, but I already did
some work on the landing view. For the server log it would be nice
to have an API call to retrieve the console output, or at least
the last message. Currently i’m working on the applications view.
El 14/7/2015, a las 4:32, Hadrian Zbarcea <[email protected]
<mailto:[email protected]>> escribió:
Hi Raul,
Can you please share some wireframes or screenshots of what you
are working on?
The second link Aled posted is an interesting one for me (and I
am not a UI expert by any measure). It looks like Adrian Nieto is
working on some changes of the UI. The initial thread he started
died off unfortunately.
I cc'ed Adrian explicitly in the hope that he could share more
about his plans.
Cheers,
Hadrian
On 07/13/2015 06:09 PM, aled sage wrote:
Hi Raul, excellent!
Can you elaborate for the mailing list what area of the Brooklyn
GUI you
are working on? From other comms, I presume it is the drag and
drop editor
which Thomas proposed on the list previously [1].
In terms of guidelines, are you thinking of look-and-feel or coding
standards?
For look-and-feel, I'd go for community feedback: propose some
wire-frame
diagrams / mockups early to get feedback, iterate on those until
we have
sufficient consensus, and then implement!
---
Another discussion about the Brooklyn GUI is the e-mail thread
"A proposal
of a new Apache Brooklyn GUI" [2].
Aled
[1]
http://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201506.mbox/%3CCAH20XTZPdcfXBam9WcGD_%3DWbWnuzMKeTOVoK3vkiXgvEBJ5zpw%40mail.gmail.com%3E
[2]
http://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201507.mbox/%3CFEC0FF77-671B-455C-A29E-6ABF6E4028D3%40lcc.uma.es%3E
On Mon, Jul 13, 2015 at 8:38 PM, Raul Canta <[email protected]
<mailto:[email protected]>> wrote:
Hi,
I am working on some improvements to the Brooklyn gui. Where
can I find
some guidelines?
Thanks,
Raul
