Combinations possible are: 1. If users are building an image for a virtual machine, it's possible to 'SAVE IMAGE AS TEMPLATE' or 'RUN IMAGE'. 2. If users are building an image for a physical machine, it's possible to 'SAVE IMAGE AS TEMPLATE' OR TO 'WRITE TO STORAGE'(deploy). 3. If users are building an image that is not for a virtual machine and the output does not include a live image, it will only be possible to 'SAVE AS TEMPLATE' or 'VIEW IMAGE FILES. (Our thinking here is that we will not offer the option to run physical machines in an emulator, and if no live image is created as part of the output it will not be possible to deploy it via a USB key.)
Transfer to Dongxiao since he is working on that.
The oe-core patch was in at http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=5b86fb09c57d738bc4dde3e7ca6f11aafe0ccc3c
The bitbake patch was also in at http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=bc73876964578d324e5953480b68f7f22a94033c.
Created attachment 432 [details] Image Detail screen after built
This issue has not been fixed. All 3 buttons 'Save as Template' Run image' and 'Deploy Image' are displayed even when they can't be selected for any of the extension available. Only 2 buttons should be displayed at one time as explained in this bug. The scenario where all buttons are available doesn't exist. Also, can anyone explain me why the 'live' image is not available by default? I have attached an example of how the 'image detail' screen looks at the moment when users create an image. The disabled buttons provide a bad user experience as users see the disabled buttons but they have no explanation on why these buttons are disabled, neither they can make them active from that screen anyway. I also attached how the 'image detail' looks like when opening an 'image' again from the image folder. What happened to the 'Edit configuration' and 'Edit package' information and buttons? How can users modify an image?
Created attachment 433 [details] Image Detail screen she opening an already built image
Also, can anyone explain me why the 'live' image is not available by default? Because probably it is not an image which can be deployed on a real hardware. For instance, it is an image for emulator without any BSP support.
(In reply to comment #5) > This issue has not been fixed. All 3 buttons 'Save as Template' Run image' and > 'Deploy Image' are displayed even when they can't be selected for any of the > extension available. Only 2 buttons should be displayed at one time as > explained in this bug. The scenario where all buttons are available doesn't > exist. > > Also, can anyone explain me why the 'live' image is not available by default? > > I have attached an example of how the 'image detail' screen looks at the > moment when users create an image. The disabled buttons provide a bad user > experience as users see the disabled buttons but they have no explanation on > why these buttons are disabled, neither they can make them active from that > screen anyway. > > I also attached how the 'image detail' looks like when opening an 'image' again > from the image folder. What happened to the 'Edit configuration' and 'Edit > package' information and buttons? How can users modify an image? If users open an already built image, Hob doesn't have the information of its configuration/package, therefore we didn't provide these buttons.
P
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=6486d39fb1c626d65e9119046bae088f69fa06b3 This patch is to fix when a button is not applicable, it will be hidden. For what Dongxiao said: If users open an already built image, Hob doesn't have the information of its configuration/package, therefore we didn't provide these buttons. That is true. We also can't add the configuration information into the image. Otherwise, the community won't agree.
verified, thanks!