Mailing-List: contact dev-help@brooklyn.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <55A51AC9.5030501@gmail.com>
References: 
 <CAJ2LgwTk6BFo1=0uWdreFC0k7VVAUFbc30oJAha+E4bodHpX8g@mail.gmail.com>
	<CAPnQ1Dh2Ozvz1fBr6b+jCdidpQ1mFNLvC0fg1sLAS2UG7AHY7w@mail.gmail.com>
	<55A474C8.5070103@gmail.com>
	<CAC3F2AA-40A6-4840-A0A0-2BE910455257@lcc.uma.es>
	<CAJ2LgwSc5Og3kmokVgms+nNOOBLX5PZGbwD87PWTNz449n=9Ag@mail.gmail.com>
	<55A4F0F8.3080300@lcc.uma.es>
	<55A50B24.0@gmail.com>
	<55A50E9F.4050600@gmail.com>
	<55A51AC9.5030501@gmail.com>
Date: Tue, 14 Jul 2015 18:07:09 +0300
Message-ID: 
 <CAJ2LgwQTh0ncX-GG8yuzkUiHY3UvaU8qTDHaKcfvZGuiAxA2VA@mail.gmail.com>
Subject: Re: Question about the Brooklyn webui
From: Raul Canta <raul@apifocal.com>
To: dev@brooklyn.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a1134bae03245b0051ad73127

--001a1134bae03245b0051ad73127
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi all,


Aled, I used the Balsamiq tool and reconstructed the mockups i sent earier
and made some changes on the "applications" view.

It's just an rough mockup to know if this is what you had in mind for the
"drag & drop graph"
https://dl.dropboxusercontent.com/u/38051787/ApacheBrooklyn-Editor.pdf
 Similar to what Adrian Nieto proposed.


Adri=C3=A1n Nieto, as Aled said earier in the email, i think is better to d=
o
first some basic mockups for the editor and after everyone is happy with
the result i can do a more "realistic" mockup.


Let me know your thoughts,
Raul C.


On Tue, Jul 14, 2015 at 5:20 PM, Aled Sage <aled.sage@gmail.com> wrote:

> Hi all,
>
> I've put together some draft use-cases for the blueprint designer.
> Feedback extremely welcome:
>
>
> https://docs.google.com/document/d/1A1oaIbGPDXgJsum0QnE9gmYfLwRotEOTPnoi3=
zqXTD8/edit?usp=3Dsharing
>
> Aled
>
>
>
> On 14/07/2015 14:29, Aled Sage wrote:
>
>> Hi Adrian,
>>
>> I agree it's on the right track, with drag-and-drop of services
>> (analogous to existing entities/blueprints), and settings on each of tho=
se
>> services (analogous to config options).
>>
>> An important difference from Microsoft Robotics Studio is that we are
>> mostly talking about a deployment configuration, whereas the robotics
>> studio is a graphical programming language. Therefore, the analogy will
>> break down so we have to be careful about what ideas we take from that.
>>
>> ---
>> Labels/layers sounds sensible.
>>
>> We should also write up some use-cases. I volunteer to make a start on
>> that.
>>
>> ---
>> In terms of mockups, I love wire frames and tools like Balsamiq [1]. It
>> allows for extremely fast iterations, fast feedback, and avoids
>> (time/emotional) investment in more "realistic" mockups. I suggest we al=
l
>> agree that any mockup code is throw-away. If it's not, then we're at ris=
k
>> of spending too much time on a single phase of the mockup, rather than
>> getting our ideas out there for fast feedback.
>>
>> Aled
>>
>> [1] https://balsamiq.com/products/mockups/
>>
>> On 14/07/2015 14:14, Hadrian Zbarcea wrote:
>>
>>> Hi Adrian,
>>>
>>> This looks very interesting to me. Complex approach or not, I believe
>>> this is what is needed and you're on the right track.
>>>
>>> I spent quite a bit of time thinking about this problem. My intuition
>>> tells me now that we need to introduce some metadata like labels and la=
yers
>>> to handle complexity. However, I don't have a concrete proposal at this
>>> point and I am not sure how productive it would be to just throw ideas.
>>>
>>> Best,
>>> Hadrian
>>>
>>>
>>> On 07/14/2015 07:22 AM, Adri=C3=A1n Nieto wrote:
>>>
>>>> What do you think about trying to mockup something based directly on
>>>> material design?
>>>>
>>>> About how it the App designer should work I would suggest something li=
ke
>>>> Microsoft Robotics Studio[1] but maybe this is a very complex approach=
.
>>>>
>>>> [1]
>>>>
>>>> http://3.bp.blogspot.com/_w8zmcBHHhdk/TD9ewicbGdI/AAAAAAAAB6o/8nEsQNzw=
8eI/s1600/UltrasonicExplorer.png
>>>>
>>>> El 14/07/2015 a las 11:47, Raul Canta escribi=C3=B3:
>>>>
>>>>> Hello,
>>>>>
>>>>> I've looked over Adrian Nieto post and it looks that we had the same
>>>>> idea
>>>>> using AngularJS and Material Design 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-Ap=
plication.jpg
>>>>>
>>>>>
>>>>> https://dl.dropboxusercontent.com/u/38051787/ApacheBrooklyn-Editor-YA=
ML.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 Brookl=
yn
>>>>> look-and-feel
>>>>>
>>>>> On Tue, Jul 14, 2015 at 11:21 AM, Adri=C3=A1n Nieto P=C3=A9rez <
>>>>> adrian@lcc.uma.es>
>>>>> wrote:
>>>>>
>>>>>  My idea was to start the project during August, but I already did so=
me
>>>>>> work on the landing view. For the server log it would be nice to hav=
e
>>>>>> an
>>>>>> API call to retrieve the console output, or at least the last messag=
e.
>>>>>> Currently i=E2=80=99m working on the applications view.
>>>>>>
>>>>>>
>>>>>>
>>>>>> El 14/7/2015, a las 4:32, Hadrian Zbarcea <hzbarcea@gmail.com>
>>>>>> escribi=C3=B3:
>>>>>>
>>>>>> 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/2015=
06.mbox/%3CCAH20XTZPdcfXBam9WcGD_%3DWbWnuzMKeTOVoK3vkiXgvEBJ5zpw%40mail.gma=
il.com%3E
>>>>>> [2]
>>>>>>
>>>>>>
>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/2015=
07.mbox/%3CFEC0FF77-671B-455C-A29E-6ABF6E4028D3%40lcc.uma.es%3E
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 13, 2015 at 8:38 PM, Raul Canta <raul@apifocal.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I am working on some improvements to the Brooklyn gui. Where can I
>>>>>> find
>>>>>> some guidelines?
>>>>>>
>>>>>> Thanks,
>>>>>> Raul
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>
>

--001a1134bae03245b0051ad73127--