<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 12/08/2015 08:20, Archana Singh
wrote:<br>
</div>
<blockquote cite="mid:55CB2BE7.7000404@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
Please find my comment inline. <br>
<br>
<blockquote
cite="mid:OFCC5ABC95.F005EE4C-ON65257E9F.003B648A-65257E9F.003B6EDE@in.ibm.com"
type="cite"> <br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font
size="1" face="sans-serif">Aline Manera <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:alinefm@linux.vnet.ibm.com"><alinefm@linux.vnet.ibm.com></a></font>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font
size="1" face="sans-serif"><a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:ginger-dev-list@nongnu.org">ginger-dev-list@nongnu.org</a></font>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">Date: </font><font
size="1" face="sans-serif">08/11/2015 08:12 PM</font> <br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">[Ginger-dev-list]
[RFC] Inheriting Kimchi's Host tab</font> <br>
<font size="1" color="#5f5f5f" face="sans-serif">Sent by:
</font><font size="1" face="sans-serif"><a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:ginger-dev-list-bounces+archanasingh=in.ibm.com@nongnu.org">ginger-dev-list-bounces+archanasingh=in.ibm.com@nongnu.org</a></font>
<br>
<hr noshade="noshade"> <br>
<br>
<br>
<tt><font size="2">Hi all,<br>
<br>
As we have agreed on Kimchi mailing list, the Ginger
community will be <br>
responsible for the Host tab (today part of Kimchi) in a way
of 2 <br>
different plugins: ginger-basic and ginger.<br>
ginger-basic will provide host basic information, host
statistics and <br>
debug reports support. And among the current Ginger
features, it will <br>
also provide software updates and repositories management.<br>
<br>
For Kimchi perspective, we need to transform part of the
Host tab into <br>
the ginger-basic plugin and add it as a Kimchi dependency.<br>
To move the discussion as soon as possible to Ginger
community, my <br>
suggestion is to move the entire Host tab into ginger-basic
plugin in <br>
the first moment.<br>
Once we do that, we can move software update and
repositories management <br>
APIs to Ginger.<br>
<br>
Here is my proposal:<br>
<br>
1) Create ginger-basic plugin which will launch the Host tab
as it is today.<br>
It will be done on Kimchi community.<br>
<br>
2) Move software update and repositories management *APIs*
from <br>
ginger-basic to ginger.<br>
Only the API will be updated. The UI will keep the same.<br>
<br>
3) Add ginger-basic as a Ginger dependency.<br>
In this step, Ginger standalone will launch 2 tabs: Host
and <br>
Administration.<br>
<br>
All that can be done by the end of September.<br>
<br>
Once we have the new UI widgets done, Samuel will start
working on <br>
merging those 2 tabs into one as we just need the update how
UI is built.<br>
The idea is to release Ginger as one single Host tab in the
December <br>
</font></tt></blockquote>
<tt><font size="2">@Samuel: As I was looking into current UI
implementation to understand how to merge two plugins into one
tab. But now it does not make sense to spend time on
understanding this in exiting UI, as the plan is to do this on
new UI.<br>
As I am not expert on bootstrap, is bootstrap already has some
feature to merge two plugins into one tab?<br>
If not, then do you think it is better to consider this point
while implementing new UI, so that merging</font></tt><tt><font
size="2"><tt><font size="2">(two plugins into one tab)</font></tt>
can be easier wherever required. <br>
Or do you think still it make sense to spend some time to
understand how can this be done in exiting UI?<br>
I hope I make sense to you. Please let me know your input.<br>
</font></tt><br>
<tt><font size="2">Or spending some time in current UI
implementation on how to merge will be required?<br>
</font></tt></blockquote>
<br>
Nope! There is no need to any work in the current UI.<br>
<br>
In the new UI design the merge will be very simple.<br>
<br>
Let's say ginger-base will launch the Host tab with a <div
id='host-content'> and the plugins which want to extend it will
append the appropriated XML to this <div><br>
<br>
In Jquery, it would be something like the following:<br>
<br>
$('.host-content').append(<new XML to add to the host
content>)<br>
<br>
<br>
<blockquote cite="mid:55CB2BE7.7000404@linux.vnet.ibm.com"
type="cite"><tt><font size="2"> </font></tt>
<blockquote
cite="mid:OFCC5ABC95.F005EE4C-ON65257E9F.003B648A-65257E9F.003B6EDE@in.ibm.com"
type="cite"><tt><font size="2"> release - in addition to wok and
Kimchi as a plugin.<br>
<br>
Let me know what you think about it.<br>
<br>
Regards,<br>
Aline Manera<br>
<br>
<br>
</font></tt> </blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>