From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id BF649E00592 for ; Thu, 2 Feb 2012 21:30:03 -0800 (PST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 02 Feb 2012 21:30:02 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208,217";a="120117352" Received: from pgsmsx603.gar.corp.intel.com ([10.221.43.87]) by fmsmga002.fm.intel.com with ESMTP; 02 Feb 2012 21:30:01 -0800 Received: from pgsmsx101.gar.corp.intel.com (10.221.44.78) by pgsmsx603.gar.corp.intel.com (10.221.43.87) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 3 Feb 2012 13:29:59 +0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by PGSMSX101.gar.corp.intel.com (10.221.44.78) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 3 Feb 2012 13:29:59 +0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.36]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.91]) with mapi id 14.01.0355.002; Fri, 3 Feb 2012 13:29:57 +0800 From: "Wang, Shane" To: "Xu, Dongxiao" , "Barros Pena, Belen" , "Lu, Lianhao" Thread-Topic: RFC: Hob 1.2 design Thread-Index: AQHM1ghN2ta+vDnY0kiXcbK0irRQ85YS108ggAGuLCCAAHlrgIAGmYWAgAb8MNCAAqn0gIACotQAgABGdBCAAFS8AIAAmk2AgABm6zCAAOoDcIAACL3wgAA+c2A= Date: Fri, 3 Feb 2012 05:29:57 +0000 Message-ID: <3AB6CE7F274E534CAFD089D127A8A1FC0FCEBEDF@SHSMSX102.ccr.corp.intel.com> References: <3AB6CE7F274E534CAFD089D127A8A1FC0FCE9F5F@SHSMSX102.ccr.corp.intel.com> <3AB6CE7F274E534CAFD089D127A8A1FC0FCEB255@SHSMSX102.ccr.corp.intel.com> <3AB6CE7F274E534CAFD089D127A8A1FC0FCEBC20@SHSMSX102.ccr.corp.intel.com> <40776A41FC278F40B59438AD47D147A90FCD04D6@SHSMSX102.ccr.corp.intel.com> In-Reply-To: <40776A41FC278F40B59438AD47D147A90FCD04D6@SHSMSX102.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Cc: "Purdie, Richard" , "Lock, Joshua" , "yocto@yoctoproject.org" , "Eggleton, Paul" Subject: Re: RFC: Hob 1.2 design 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: Fri, 03 Feb 2012 05:30:04 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3AB6CE7F274E534CAFD089D127A8A1FC0FCEBEDFSHSMSX102ccrcor_" --_000_3AB6CE7F274E534CAFD089D127A8A1FC0FCEBEDFSHSMSX102ccrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dongxiao and I have a discussion on that again. Belen, please ignore the issue for the deployment button below, and we have= several suggestions. 1. To make the Packages Screen and the Packages dialog the same. The Packages Screen is shown after users click "Build packages". 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't want to= go back to the Image configuration screen and click "Build Image". 2. As mentioned in my last email, we want to add "Clean" in the GUI. The re= ason 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 -c cleana= ll" in the command line. But we hope to provide this feature in the GUI. If you agree the above, then the action "Clean" is for a recipe or multiple= recipes, and clicking "Clean" will go to the screen at 4:00, since cleanin= g includes some tasks. Then we could make the Recipes dialog to be a screen, do you agree? The other reason is users can view recipes and click "Build Packages", no n= eed go back to the Image configuration screen. The use case is: 1) View Recipes in the Image configuration -> the Recipes screen -> Select = recipes and Build packages -> Log -> the Packages screen ... 2) View Recipes in the Image configuration -> the Recipes screen -> Select = recipes and Build packages -> Log -> Failure -> Go back to the Recipes scre= en -> Clean something -> Log -> the Recipes screen -> Build packages again = -> Log -> Success -> the Packages screen ... 3) View Recipes in the Image configuration -> the Recipes screen -> Select = recipes -> Go back to the Image configuraion -> "Build Image" 4) Nothing want to view in the Image configuration after choosing "base ima= ge" -> "Build packages" -> Log -> the Packages screen ... 5) Nothing want to view in the Image configuration after choosing "base ima= ge" -> "Build packages" -> Log -> Failure -> Go back to the Image configura= tion -> View Recipes -> the Recipes screen -> Clean something -> Log -> the= Recipe screen -> ... 6) Nothing want to view in the Image configuration after choosing "base ima= ge" -> "Build Image" -> Log -> the Image details ... and so on... 3. When build is failed, there is a "Back" button. But go back to where is = determined by where you come from. 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 "Congratulations! Your image is ready!" is = shown, OK? 5. In the Image details screen, "Settings" is obviously not good to be show= n there. Can we remove "Load Template"? Because it will initiate a new buil= d. Let's ask users to click "Build new image" to be on the Image configurat= ion 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 Configuration", if the build process i= s not executed this time. (ditto for "Save Template" in 4.) 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 detai= ls screen and let uses decide what he/she wants? I admit an error possibly = happens if the image doesn't match the action, but we just report the error= . Thoughts? Thanks. -- Shane From: Xu, Dongxiao 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, Son= g; 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" and then click deploy button. I thin= k normal user may not have such knowledge. I am still wondering if adding a= "deploy" button in the tool bar? Thanks, Dongxiao From: Wang, Shane 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, Son= g; Stewart, David C; yocto@yoctoproject.org Subject: RE: RFC: Hob 1.2 design I get one more: In the Image details screen, after opening an image file by clicking "My im= ages", we don't allow to "Edit Package", I think. Because with an image only, we can't generate the packages from it, you can= 't assume there is a build directory (tmp/), is my understanding correct? -- Shane --_000_3AB6CE7F274E534CAFD089D127A8A1FC0FCEBEDFSHSMSX102ccrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dongxiao and = I have a discussion on that again.

 

Belen, please= ignore the issue for the deployment button below, and we have several sugg= estions.

 

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

The Packages = Screen is shown after users click “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;.

 

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” will go to the screen at 4:00, si= nce cleaning includes some tasks.

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

The other rea= son is users can view recipes and click “Build Packages”, no ne= ed go back to the Image configuration screen.

The use case = is:

1) View Recip= es in the Image configuration -> the Recipes screen -> Select recipes= and Build packages -> Log -> the Packages screen …<= /span>

2) View Recip= es 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 -> Buil= d packages again -> Log -> Success -> the Packages screen …<= o:p>

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

4) Nothing wa= nt to view in the Image configuration after choosing “base image̶= 1; -> “Build packages” -> Log -> the Packages screen &= #8230;

5) Nothing wa= nt to view in the Image configuration after choosing “base image̶= 1; -> “Build packages” -> Log -> Failure -> Go back= to the Image configuration -> View Recipes -> the Recipes screen -> Clean something -> Lo= g -> the Recipe screen -> …

6) Nothing wa= nt to view in the Image configuration after choosing “base image̶= 1; -> “Build Image” -> Log -> the Image details …= ;

and so onR= 30;

 

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

 

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

Let’s s= how “Save Template” when “Congratulations! Your image is = ready!” is shown, OK?

 

5. In the Ima= ge details screen, “Settings” is obviously not good to be shown= there. Can we remove “Load Template”? Because 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 i= t OK?

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

 

6. In Josh= 217;s email, FRI 2 image can also be run, though it is an image for real ma= chine. Can we keep two buttons “Run” and “Deploy” o= n 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.

 

Thoughts?

Thanks.

--

Shane=

 = ;

From: Xu, Dongxiao
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; L= iu, Song; Stewart, David C; yocto@yoctoproject.org
Subject: RE: RFC: Hob 1.2 design

 

One more from me that, Hob may w= ork as a deploy tool, and in the new movie, the approach is to select ̶= 0;My images” and 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,

Dongxiao

 

From: Wang, Shane
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; L= iu, Song; Stewart, David C; yocto@yoctoproject.org
Subject: RE: RFC: Hob 1.2 design

 

I get one = more:

 = ;

In the Ima= ge details screen, after opening an image file by clicking “My images= ”, we don’t allow to “Edit Package”, I think.<= /o:p>

Because wi= th an image only, we can’t generate the packages from it, you canR= 17;t assume there is a build directory (tmp/), is my understanding correct?=

 = ;

--

Shane=

--_000_3AB6CE7F274E534CAFD089D127A8A1FC0FCEBEDFSHSMSX102ccrcor_--