Bug 1588

Summary:	Hob v2 - Interface updates?
Product:	[Build System, Metadata & Runtime] Hob	Reporter:	Richard Purdie <richard.purdie>
Component:	hob	Assignee:	Jessica <jessica.zhang>
Status:	VERIFIED MOVED	QA Contact:
Severity:	enhancement
Priority:	Low	CC:	alexandru.c.georgescu, david.c.stewart, jessica.zhang, jiajun.xu, jjardon, limingx.l.an, poky.bs.watcher, poky.watcher, yilongx.y.sun
Version:	unspecified
Target Milestone:	1.4
Hardware:	x86
OS:	Multiple
Whiteboard:	Umbrella Bug For Tracking Only
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---
Bug Depends on:	991, 992, 1221, 1241, 1272, 1277, 1303, 1441, 1450, 1572, 1574, 1575, 1576, 1577, 1688, 1742, 1743, 1744, 1745, 1746, 1747, 1748, 1749, 1750, 1751, 1752, 1753, 1764, 1792
Bug Blocks:

Description Richard Purdie 2011-10-04 07:05:13 UTC

We need to consider how we could massively update and improve the interface for Hob, perhaps similar to SuSE Studio. This is for both local (non-network) builds as well as network.

One prospective ideas include having a web server style UI.

Another idea might be to split the UI into two sections, a "build" section and then an "image construction" section which is only accessed after components are built. This would remove some of the challenges in the existing UI where dependencies aren't 100% clear until after the build completes.

Comment 1 Dave Stewart 2011-10-06 12:23:56 UTC

A requirement is to enable commercial partners, such as an OSV, to add their own enhancements to hob. So Hob should be architected in such a way as to make it easy for a partner to take the existing Hob and extend it with new functionality, brand it with their own color schemes and logos, etc.

Comment 2 Joshua Lock - Disabled 2011-10-06 12:44:18 UTC

It would be useful to have more of an idea what constitutes an enhancement. Branding is one thing, and a fairly trivial one at that, and we have other ideas for enabling a 'distributor' to affect things such as the images shown in the 'Base Image' dropdown (see bug 1581).

Comment 3 Joshua Lock - Disabled 2011-10-06 12:50:12 UTC

Furthermore, within the framework of the existing GUI, it should be fairly trivial to allow extensible menu entry points which launch an external program re-parented so as to appear as a dialog of hob.

To allow true plugins will be a more significant, but likely worthwhile, endeavour.

Comment 4 Dave Stewart 2011-10-06 16:39:10 UTC

Yeah, I was a little rushed when I typed my earlier comment.

An OSV that we talked with today told me that they would likely have their own build tool rather than use the Hob. But then again, why redo Hob when it's already there? Wouldn't it be better if the interface would expand based on files or directories which can be added in another layer.

An analogy was drawn to kconfig, which (I was told) stores configuration in text files and has a variety of front ends to manage it.

So a nice goal for Hob to improve its re-useability would be to enable it to extend its function based on things which can be added to the system later.

Comment 5 Shane Wang 2012-04-04 12:15:14 UTC

Because some of bugs are put into v1.3, I am going to put this bug to v1.3 still for tracking purpose.

Comment 6 Jessica 2013-01-09 18:33:16 UTC

Since this bug was opened for 1.2 work and now things have much changes for hob.  Close this one and using the current hob bugs to track issues.

Comment 7 Alexandru Georgescu 2013-02-19 14:52:08 UTC

Verified as per Jessica's comments.