Return-Path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7705AE01217 for ; Mon, 6 Feb 2012 05:54:37 -0800 (PST) Received: from azsmga002.ch.intel.com ([10.2.17.35]) by azsmga101.ch.intel.com with ESMTP; 06 Feb 2012 05:54:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208,217";a="63740818" Received: from irsmsx601.ger.corp.intel.com ([163.33.7.164]) by AZSMGA002.ch.intel.com with ESMTP; 06 Feb 2012 05:54:29 -0800 Received: from irsmsx104.ger.corp.intel.com (163.33.3.159) by irsmsx601.ger.corp.intel.com (163.33.7.164) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 6 Feb 2012 13:54:03 +0000 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.99]) by IRSMSX104.ger.corp.intel.com ([169.254.5.165]) with mapi id 14.01.0355.002; Mon, 6 Feb 2012 13:54:02 +0000 From: "Barros Pena, Belen" To: "Wang, Shane" , Joshua Lock , "Xu, Dongxiao" Thread-Topic: [yocto] Hob 1.2 design - visuals Thread-Index: AQHM5NbHHh6YUORDy0KS4NiMLZICTw== Date: Mon, 6 Feb 2012 13:54:01 +0000 Message-ID: In-Reply-To: <3AB6CE7F274E534CAFD089D127A8A1FC0FCEDE87@SHSMSX102.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.14.0.111121 x-originating-ip: [10.252.18.204] MIME-Version: 1.0 Cc: "yocto@yoctoproject.org" , "Metthey, Mikael" Subject: Re: Hob 1.2 design - visuals X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2012 13:54:38 -0000 X-Groupsio-MsgNum: 4690 Content-Language: en-US Content-Type: multipart/mixed; boundary="_002_CB558AF2739Abelenbarrospenaintelcom_" --_002_CB558AF2739Abelenbarrospenaintelcom_ Content-Type: text/plain; charset="us-ascii" Content-ID: <94C3175D529D0444B60DF40D38A699C5@intel.com> Content-Transfer-Encoding: quoted-printable >>3. Inherit colour scheme from applied OS theme in host computer >Is it to say we use the default colors from OS, and don't specify any >color? >For example, Jessica wants progress bars to be green but in Ubuntu it >should be orange. >If so, Belen, I agree with you. Yes, I think that's what Joshua recommended, and I can see why it makes sense. Joshua, could you confirm when you have a chance? If we decide to implement this way, people will need to understand that this applies to all UI elements without exceptions. Any particular requests (like Jessica's) could be looked at on a case by case basis. Cheers Belen On 06/02/2012 11:42, "Wang, Shane" wrote: >Barros Pena, Belen wrote on 2012-02-06: > >> Hi all, >>=20 >> It looks like there are some design implementation principles laid out >>on >> the email below. Just to summarise: >>=20 >> 1. Implement the Hob design with the toolkit provided widgets and OS >>theme >> and review which things we might want to enhance later. I understand >>this >> excludes icons: we will use the ones provided by the visual design. >>=20 >> 2. Make sure that all action buttons in windows and dialogues follow up >> the spacing GNOME rules set by the Human Interface Guidelines at >> http://developer.gnome.org/hig-book/3.0/index.html.en >>=20 >> 3. Inherit colour scheme from applied OS theme in host computer >>=20 >Is it to say we use the default colors from OS, and don't specify any >color? >For example, Jessica wants progress bars to be green but in Ubuntu it >should be orange. >If so, Belen, I agree with you. > >> Shane, Dongxiao: if you have any comments about the above, please let us >> know. >>=20 >> Cheers >>=20 >> Belen --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. --_002_CB558AF2739Abelenbarrospenaintelcom_ Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 06 Feb 2012 13:54:01 GMT"; modification-date="Mon, 06 Feb 2012 13:54:01 GMT" Content-ID: User-Agent: Microsoft-MacOutlook/14.14.0.111121 Date: Mon, 6 Feb 2012 11:53:51 +0000 Subject: Re: RFC: Hob 1.2 design From: "Barros Pena, Belen" To: "Wang, Shane" , "Xu, Dongxiao" , "Lu, Lianhao" CC: "Eggleton, Paul" , "Purdie, Richard" , "Zhang, Jessica" , "Lock, Joshua" , "Liu, Song" , "Stewart, David C" , "yocto@yoctoproject.org" Message-ID: Thread-Topic: RFC: Hob 1.2 design In-Reply-To: <3AB6CE7F274E534CAFD089D127A8A1FC0FCEBEDF@SHSMSX102.ccr.corp.intel.com> Content-Type: multipart/alternative; boundary="B_3411374031_5472995" MIME-Version: 1.0 --B_3411374031_5472995 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Hi Shane and team, In general all sounds good. I just have a couple of small comments, which I've added below. Belen From: "Wang, Shane" Date: Fri, 3 Feb 2012 05:29:57 +0000 To: "Xu, Dongxiao" , "Belen Barros Pena (Intel)" , "Lu, Lianhao" Cc: "Eggleton, Paul" , "Purdie, Richard" , "Zhang, Jessica" , "Lock, Joshua" , "Liu, Song" , "Stewart, David C" , "yocto@yoctoproject.org" Subject: RE: RFC: Hob 1.2 design Dongxiao and I have a discussion on that again. =20 Belen, please ignore the issue for the deployment button below, and we have several suggestions. =20 1. To make the Packages Screen and the Packages dialog the same. The Packages Screen is shown after users click =B3Build packages=B2. That is on= e step of the process. However, the content shown in the Package dialog is all what we have built out last time. It is very possible users start from there and don=B9t want to go back to the Image configuration screen and click =B3Build Image=B2. Sorry, I am not sure I understand. What you seem to be saying is that we will eliminate the 'View packages' button from the Image configuration screen and the Packages dialogue. Users will access packages information vi= a the 'Build packages' option, which will bring them to the Packages screen. Is this correct? =20 2. As mentioned in my last email, we want to add =B3Clean=B2 in the GUI. The reason is the build will fail, say, do_fetch, then we have an option to allow users to clean what we built out and rebuild. Otherwise, the sstate could be reused for the next build. Users can do it by running =B3bitbake =ADc cleanall=B2 in the command line. But we hope to provide this feature in the GUI. If you agree the above, then the action =B3Clean=B2 is for a recipe or multiple recipes, and clicking =B3Clean=B2 will go to the screen at 4:00, since cleaning includes some tasks. Then we could make the Recipes dialog to be a screen, do you agree? Yes: I agree with you. Making Recipes a screen instead of a dialogue seems like a good solution. However, I am not sure the 'Clean' function should be in the Recipes screen: it should probably be an option that is displayed when the build fails. If you select it you go to the screen at 4:00 to provide information about the cleaning tasks and once they are done, you ge= t the Recipes screen ready for you to build again. I think this 'build failed= ' scenario is very important, and I would like to design it carefully. Would it be ok if I work on it this week and send you some suggestions? The other reason is users can view recipes and click =B3Build Packages=B2, no need go back to the Image configuration screen. The use case is:=20 1) View Recipes in the Image configuration -> the Recipes screen -> Select recipes and Build packages -> Log -> the Packages screen =8A 2) View Recipes in the Image configuration -> the Recipes screen -> Select recipes and Build packages -> Log -> Failure -> Go back to the Recipes screen -> Clean something -> Log -> the Recipes screen -> Build packages again -> Log -> Success -> the Packages screen =8A 3) View Recipes in the Image configuration -> the Recipes screen -> Select recipes -> Go back to the Image configuraion -> =B3Build Image=B2 4) Nothing want to view in the Image configuration after choosing =B3base image=B2 -> =B3Build packages=B2 -> Log -> the Packages screen =8A 5) Nothing want to view in the Image configuration after choosing =B3base image=B2 -> =B3Build packages=B2 -> Log -> Failure -> Go back to the Image configuration -> View Recipes -> the Recipes screen -> Clean something -> Log -> the Recipe screen -> =8A 6) Nothing want to view in the Image configuration after choosing =B3base image=B2 -> =B3Build Image=B2 -> Log -> the Image details =8A and so on=8A This seems to make sense. Just a small comment about the use case number 3. I think the Recipes screen should have 2 actions: "build packages" and "build image", so that users who want to build an image directly from the Recipes screen don't need to go back to the Image configuration screen in order to build the image. =20 3. When build is failed, there is a =B3Back=B2 button. But go back to where is determined by where you come from. I'll keep this in mind when designing the 'build failed' scenario. =20 4. After users open an image by =B3My images=B2, some time there should not be = a =B3Save Template=B2 because we don=B9t have build process. Let=B9s show =B3Save Template=B2 when =B3Congratulations! Your image is ready!=B2 is shown, OK? This sounds ok to me. Should we have a 'save as template' option in the Image configuration screen? Or will we just have it in the Image details screen when you get there after completing the build process? =20 5. In the Image details screen, =B3Settings=B2 is obviously not good to be show= n there. Can we remove =B3Load Template=B2? Because it will initiate a new build. Let=B9s ask users to click =B3Build new image=B2 to be on the Image configuration and click =B3Load Template=B2. We just keep =B3My Images=B2 in the last screen (the Image details screen), is it OK? And remove =B3Edit Packages=B2 and =B3Edit Configuration=B2, if the build process i= s not executed this time. (ditto for =B3Save Template=B2 in 4.) Happy with this. =20 6. In Josh=B9s email, FRI 2 image can also be run, though it is an image for real machine. Can we keep two buttons =B3Run=B2 and =B3Deploy=B2 on the Image details screen and let uses decide what he/she wants? I admit an error possibly happens if the image doesn=B9t match the action, but we just report the error. Not so happy with this one ;) If an option is going to generate an error when selected, it should not be there at all. GUI's must be defensive: they must prevent user errors. This is a fundamental principle of interaction design. We should only present the 'Run' (on qemu) option if the image is suitable for qemu running. We should only display the 'Deploy' option for live images. If there is no way to reliably determine what type of image we are dealing with and which options are suitable for them, the 'Run' and 'Deploy' functionality should not be there at all. Better wait until we fin= d a work around. Having said that, it seems to me that using the file extension to determine what's the appropriate action for each image should work the vast majority of times. If someone has changed the extension of the image, well, that would be an edge case (how likely are people to do that?), and we should no= t get into the trap of designing for the edge case, which is what we would be doing if we were to display both 'run' and 'deploy' for all images. =20 Thoughts? Thanks. -- Shane =20 From: Xu, Dongxiao=20 Sent: Friday, February 03, 2012 8:57 AM To: Wang, Shane; Barros Pena, Belen; Lu, Lianhao Cc: Eggleton, Paul; Purdie, Richard; Zhang, Jessica; Lock, Joshua; Liu, Song; Stewart, David C; yocto@yoctoproject.org Subject: RE: RFC: Hob 1.2 design =20 One more from me that, Hob may work as a deploy tool, and in the new movie, the approach is to select =B3My images=B2 and then click deploy button. I think normal user may not have such knowledge. I am still wondering if adding a =B3deploy=B2 button in the tool bar? =20 Thanks, Dongxiao =20 From: Wang, Shane=20 Sent: Friday, February 03, 2012 8:26 AM To: Wang, Shane; Barros Pena, Belen; Xu, Dongxiao; Lu, Lianhao Cc: Eggleton, Paul; Purdie, Richard; Zhang, Jessica; Lock, Joshua; Liu, Song; Stewart, David C; yocto@yoctoproject.org Subject: RE: RFC: Hob 1.2 design =20 I get one more: =20 In the Image details screen, after opening an image file by clicking =B3My images=B2, we don=B9t allow to =B3Edit Package=B2, I think. Because with an image only, we can=B9t generate the packages from it, you can=B9t assume there is a build directory (tmp/), is my understanding correct= ? =20 -- Shane --B_3411374031_5472995 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Shane and team,

=
In general all sounds good. I just have a couple of small commen= ts, which I've added below.

Belen

From: "Wang, Shane&q= uot; <shane.wang@intel.com&g= t;
Date: Fri, 3 Feb 2012 05:29:= 57 +0000
To: "Xu, Dong= xiao" <dongxiao.xu@intel.c= om>, "Belen Barros Pena (Intel)" <belen.barros.pena@intel.com>, "Lu, Li= anhao" <lianhao.lu@intel.co= m>
Cc: "Eggleton, P= aul" <paul.eggleton@inte= l.com>, "Purdie, Richard" <richard.purdie@intel.com>, "Zhang, Jessica"= ; <jessica.zhang@intel.com>, "Lock, Joshua" <joshua.lock@intel.com>, "Liu, Song" <song.liu@intel.com>, "Stewart, David C&qu= ot; <david.c.stewart@intel.= com>, "yocto@yoctopro= ject.org" <yocto@yoct= oproject.org>
Subject: R= E: RFC: Hob 1.2 design

Dongxiao and I have a discussion on that again.

<= o:p> 

Belen, please ignore the issue for the deployment button below, an= d we have several suggestions.

=  

1. To make the Packages Screen and = the Packages dialog the same.

<= span lang=3D"EN" style=3D"font-size: 10.5pt; color: rgb(31, 73, 125); font-= family: Calibri, sans-serif; ">The Packages Screen is shown after users cli= ck “Build packages”. That is one step of the process.

However,= the content shown in the Package dialog is all what we have built out last= time. It is very possible users start from there and don’t want to go back to the Image configuration screen and click “Build Image&= #8221;.


Sorry,= I am not sure I understand. What you seem to be saying is that we wil= l eliminate the 'View packages' button from the Image configuration screen = and the Packages dialogue. Users will access packages information via the '= Build packages' option, which will bring them to the Packages screen. Is th= is correct?

<= p class=3D"MsoNormal"> 

2. As mention= ed in my last email, we want to add “Clean” in the GUI. The rea= son is the build will fail, say, do_fetch, then we have an option to allow users to clean what we built out and rebuild. Otherwise, the sstate could = be reused for the next build. Users can do it by running “bitbake = 211;c cleanall” in the command line. But we hope to provide this feat= ure in the GUI.

If you agree the above, then the action “Clean”= ; is for a recipe or multiple recipes, and clicking “Clean” wil= l go to the screen at 4:00, since cleaning includes some tasks.

Then we could make the Recipes dialog to be a screen= , do you agree?


Yes: I agree with you. Making Recipes a screen instead of a dialogue seem= s like a good solution. However, I am not sure the 'Clean' function should = be in the Recipes screen: it should probably be an option that is displayed= when the build fails. If you select it you go to the screen at 4:00 to pro= vide information about the cleaning tasks and once they are done, you get t= he Recipes screen ready for you to build again. I think this 'build failed'= scenario is very important, and I would like to design it carefully. Would=  it be ok if I work on it this week and send you some suggestions?

=

The other reason i= s users can view recipes and click “Build Packages”, no need go= back to the Image configuration screen.

The use case is:

2) View Recipes in the Image configuration -> the Recipes screen -&= gt; Select recipes and Build packages -> Log -> Failure -> Go back= to the Recipes screen -> Clean something -> Log -> the Recipes screen -> Buil= d packages again -> Log -> Success -> the Packages screen …<= o:p>

3) View Recipes in the Image configuration -> the Recipes screen -> = Select recipes -> Go back to the Image configuraion -> “Build I= mage”

4) Nothing want to view in the Image configuration after choos= ing “base image” -> “Build packages” -> Log -= > the Packages screen …

5) Nothing want to view in the Image conf= iguration after choosing “base image” -> “Build packag= es” -> Log -> Failure -> Go back to the Image configuration -> View Recipes -> the Recipes screen -> Clean something -> Lo= g -> the Recipe screen -> …

6) Nothing want to view in the Ima= ge configuration after choosing “base image” -> “Build= Image” -> Log -> the Image details …

and so on…


This seems to m= ake sense. Just a small comment about the use case number 3. I think the Re= cipes screen should have 2 actions: "build packages" and "bu= ild image", so that users who want to build an image directly from the= Recipes screen don't need to go back to the Image configuration screen in = order to build the image. 

=  

3. When build is failed, there is a “Back” button. But= go back to where is determined by where you come from.


I'll keep this in mind when desig= ning the 'build failed' scenario.

 

4. After users open an image by “My images”, some = time there should not be a “Save Template” because we don’= ;t have build process.

Let’s show “Save Template” when &= #8220;Congratulations! Your image is ready!” is shown, OK?

=

This sounds ok to me. Sh= ould we have a 'save as template' option in the Image configuration screen?= Or will we just have it in the Image details screen when you get there aft= er completing the build process?

=  

5. In the Image details screen, “Settings” is obviousl= y not good to be shown there. Can we remove “Load Template”? Be= cause it will initiate a new build. Let’s ask users to click “Build new image” to be = on the Image configuration and click “Load Template”.

We just = keep “My Images” in the last screen (the Image details screen),= is it OK?

And remove “Edit Packages” and “Edit Configur= ation”, if the build process is not executed this time. (ditto for &#= 8220;Save Template” in 4.)

<= div>
Happy with this.
=

 

6. In Josh’s email, FRI 2 image can also be run, though = it is an image for real machine. Can we keep two buttons “Run” = and “Deploy” on the Image details screen and let uses decide what he/she wants? I admit an error possibly ha= ppens if the image doesn’t match the action, but we just report the e= rror.


Not so h= appy with this one ;) If an option is going to generate an error when selec= ted, it should not be there at all. GUI's must be defensive: they must prev= ent user errors. This is a fundamental principle of interaction design. We = should only present the  'Run' (on qemu) option if the image is suitab= le for qemu running. We should only display the 'Deploy' option for live im= ages. If there is no way to reliably determine what type of image we are de= aling with and which options are suitable for them, the 'Run' and 'Deploy' = functionality should not be there at all. Better wait until we find a work = around.

Having said that, it seems to me that usin= g the file extension to determine what's the appropriate action for each im= age should work the vast majority of times. If someone has changed the exte= nsion of the image, well, that would be an edge case (how likely are people= to do that?), and we should not get into the trap of designing for the edg= e case, which is what we would be doing if we were to display both 'run' an= d 'deploy' for all images.

&= nbsp;

Thanks.

<= span lang=3D"EN-US" style=3D"font-size: 10.5pt; color: rgb(31, 73, 125); fo= nt-family: Calibri, sans-serif; ">--

Shane

 =

From:<= span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Tahoma, sans-ser= if; "> Xu, Dongxiao
Sent: Friday, February 03, 2012 8:57 AM
To: Wang, Shan= e; Barros Pena, Belen; Lu, Lianhao
Cc: Eggleton, Paul; Purdie, Ri= chard; Zhang, Jessica; Lock, Joshua; Liu, Song; Stewart, David C; yocto@yoctoproject.org
Subject= : RE: RFC: Hob 1.2 design

 

One more from me that, Hob may work as a deploy tool= , and in the new movie, the approach is to select “My images” a= nd then click deploy button. I think normal user may not have such knowledge. I am still wondering if adding a “= deploy” button in the tool bar?

 

Thanks,

 

From: Wang, Shane
Sent: Friday, February 03, 2012 8:26 AM
To: Wang, Shan= e; Barros Pena, Belen; Xu, Dongxiao; Lu, Lianhao
Cc: Eggleton, Pa= ul; Purdie, Richard; Zhang, Jessica; Lock, Joshua; Liu, Song; Stewart, Davi= d C; yocto@yoctoproject.orgSubject: RE: RFC: Hob 1.2 design

=

 

I get one more:=

 

In the Image details screen, after opening an image file by= clicking “My images”, we don’t allow to “Edit Pack= age”, I think.

Because with an image only, we can’t generat= e the packages from it, you can’t assume there is a build directory (= tmp/), is my understanding correct?

 

--

=

Shane<= /span>

--B_3411374031_5472995-- --_002_CB558AF2739Abelenbarrospenaintelcom_--