This theme is identical to the Smoothfeather theme in look and feel. However, the markup, stylesheets, and functions in the original Smoothfeather theme required a significant overhaul in order to give it the best foundation to be flexible enough to support all browsers. Therefore, it was nearly impossible to simply patch the Smoothfeather theme. The patch would end up being as large as the new theme, and a whole lot more complicated. This revised theme addresses OFBIZ-2309, as well as issues linked to OFBIZ-2309.

Ryan Foster
added a comment - 01/May/09 01:43 This theme is identical to the Smoothfeather theme in look and feel. However, the markup, stylesheets, and functions in the original Smoothfeather theme required a significant overhaul in order to give it the best foundation to be flexible enough to support all browsers. Therefore, it was nearly impossible to simply patch the Smoothfeather theme. The patch would end up being as large as the new theme, and a whole lot more complicated. This revised theme addresses OFBIZ-2309 , as well as issues linked to OFBIZ-2309 .

This patch incorporates OFBIZ-2306 by adding internationalized (i18n) support for the "Applications" mega-dropdown, as well as OFBIZ-2308, which adds "Primary Apps" and "Secondary Apps" headings to business area with i18n support.

Patch also makes new Bizznesstime theme the default theme, adds an Identifier to the leftbar screen definition, and cleans up the BI and Webtools application dashboards.

Ryan Foster
added a comment - 01/May/09 02:00 This patch incorporates OFBIZ-2306 by adding internationalized (i18n) support for the "Applications" mega-dropdown, as well as OFBIZ-2308 , which adds "Primary Apps" and "Secondary Apps" headings to business area with i18n support.
Patch also makes new Bizznesstime theme the default theme, adds an Identifier to the leftbar screen definition, and cleans up the BI and Webtools application dashboards.

I would say that let's check with people in the community before we totally remove the original smooth feather - but let's get this one in as soon as possible. Everyone will enjoy this one a lot more than the last one and it's a more solid foundation to build upon.

Tim Ruppert
added a comment - 01/May/09 18:08 I would say that let's check with people in the community before we totally remove the original smooth feather - but let's get this one in as soon as possible. Everyone will enjoy this one a lot more than the last one and it's a more solid foundation to build upon.

Oops I put a wrong link before, it's OFBIZ-2312 and not 2298
******************************************************************
Commited in CTR mode (Commit Then Review) though already well tested (see OFBIZ-2312)
in trunk at r770997
R9.04 at r770998.

As Tim closed OFBIZ-2312, here are the points that where still pending there and actually related to this issue (I was a fool to try to have many issues in one. Though it helped to speed things at the beginning, as ever it ends as a mess)

Jacques Le Roux
added a comment - 08/May/09 19:57 As Tim closed OFBIZ-2312 , here are the points that where still pending there and actually related to this issue (I was a fool to try to have many issues in one. Though it helped to speed things at the beginning, as ever it ends as a mess)
So I create now subtasks even for trivial issues

I have decreased the priority because this theme is no more enabled by default; for the same reason I have also removed the reference to the 09.04 release branch (I will do the same for all the subtasks).

Jacopo Cappellato
added a comment - 13/Dec/11 10:01 I have decreased the priority because this theme is no more enabled by default; for the same reason I have also removed the reference to the 09.04 release branch (I will do the same for all the subtasks).

As far as I can tell, there is not much interest in this theme. What if we resolve this task and its subtasks and just create a new one with a simple list of the open issues reported in this group of tasks?

Jacopo Cappellato
added a comment - 26/Mar/14 07:09 As far as I can tell, there is not much interest in this theme. What if we resolve this task and its subtasks and just create a new one with a simple list of the open issues reported in this group of tasks?