[RFC] Removal of of developer UI
Background Developer UI is a legacy way for Kimchi to render html page to the front end. And the font end can display the html page directly without creating the page dynamically. After the design UI code went into Kimchi, developer UI is attracting less and less attention and have been broken for a while. Further, design UI is good enough and can replace the developer UI without any encumbrance. Maintaining two sets of UI brings a lot of extra works and is unnecessary. So it is reasonable to remove the design UI code from Kimchi repository. Work to be done: * Remove the code to support rendering html text in controller * Remove the code to generate html page from the cheetah template
have tried: Developer UI can not works well on my host. On 01/02/2014 03:40 PM, Shu Ming wrote:
Background
Developer UI is a legacy way for Kimchi to render html page to the front end. And the font end can display the html page directly without creating the page dynamically. After the design UI code went into Kimchi, developer UI is attracting less and less attention and have been broken for a while. Further, design UI is good enough and can replace the developer UI without any encumbrance. Maintaining two sets of UI brings a lot of extra works and is unnecessary. So it is reasonable to remove the design UI code from Kimchi repository.
Work to be done:
* Remove the code to support rendering html text in controller * Remove the code to generate html page from the cheetah template
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
-- Thanks and best regards! Sheldon Feng(???)<shaohef@linux.vnet.ibm.com> IBM Linux Technology Center
If I understood correctly, the design UI you mean is the current kimchi UI. What is the developer UI? Something used for testing rest API? On 1/2/2014 3:40 PM, Shu Ming wrote:
Background
Developer UI is a legacy way for Kimchi to render html page to the front end. And the font end can display the html page directly without creating the page dynamically. After the design UI code went into Kimchi, developer UI is attracting less and less attention and have been broken for a while. Further, design UI is good enough and can replace the developer UI without any encumbrance. Maintaining two sets of UI brings a lot of extra works and is unnecessary. So it is reasonable to remove the design UI code from Kimchi repository.
Work to be done:
* Remove the code to support rendering html text in controller * Remove the code to generate html page from the cheetah template
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
If I understood correctly, the design UI you mean is the current kimchi UI. What is the developer UI? Something used for testing rest API?
On 01/02/2014 03:49 PM, Yu Xin Huo wrote: please run: http://localhost:8000/dev-ui.html
On 1/2/2014 3:40 PM, Shu Ming wrote:
Background
Developer UI is a legacy way for Kimchi to render html page to the front end. And the font end can display the html page directly without creating the page dynamically. After the design UI code went into Kimchi, developer UI is attracting less and less attention and have been broken for a while. Further, design UI is good enough and can replace the developer UI without any encumbrance. Maintaining two sets of UI brings a lot of extra works and is unnecessary. So it is reasonable to remove the design UI code from Kimchi repository.
Work to be done:
* Remove the code to support rendering html text in controller * Remove the code to generate html page from the cheetah template
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
-- Thanks and best regards! Sheldon Feng(???)<shaohef@linux.vnet.ibm.com> IBM Linux Technology Center
+1 On 01/02/2014 05:40 AM, Shu Ming wrote:
Background
Developer UI is a legacy way for Kimchi to render html page to the front end. And the font end can display the html page directly without creating the page dynamically. After the design UI code went into Kimchi, developer UI is attracting less and less attention and have been broken for a while. Further, design UI is good enough and can replace the developer UI without any encumbrance. Maintaining two sets of UI brings a lot of extra works and is unnecessary. So it is reasonable to remove the design UI code from Kimchi repository.
Work to be done:
* Remove the code to support rendering html text in controller * Remove the code to generate html page from the cheetah template
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
+1 On 01/02/2014 03:40 PM, Shu Ming wrote:
Background
Developer UI is a legacy way for Kimchi to render html page to the front end. And the font end can display the html page directly without creating the page dynamically. After the design UI code went into Kimchi, developer UI is attracting less and less attention and have been broken for a while. Further, design UI is good enough and can replace the developer UI without any encumbrance. Maintaining two sets of UI brings a lot of extra works and is unnecessary. So it is reasonable to remove the design UI code from Kimchi repository.
Work to be done:
* Remove the code to support rendering html text in controller * Remove the code to generate html page from the cheetah template
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
participants (5)
-
Aline Manera -
Hongliang Wang -
Sheldon -
Shu Ming -
Yu Xin Huo