Third step, move macro ftl libraries and ftl template present on framework common to common theme
At this step, the common-theme is forced like the common component previously.
Main common screens present on CommonScreens.xml, LookupScreens.xml and HelpScreens.xml are moved to common screen with a forced rewrite to common-theme
Warning this commit is going to follow with a other commit for CommonScreens.xml because LookupScreens.xml and HelpScreens.xml are recreated on common-theme, but to keep the history of CommonScreens.xml it was moved entirely, the second commit restore it with redirect call.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk@1806091 13f79535-47bb-0310-9956-ffa450edef68
I request all developers working on trunk to do a clean data load after this commit.
Thanks Swapnil M Mane for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1748924 13f79535-47bb-0310-9956-ffa450edef68
I reorganized the main style sheet and pushed the deprecated styles down to the bottom. I also moved the jQuery styles to a separate file.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1059564 13f79535-47bb-0310-9956-ffa450edef68
A new help system is implemented which is compatible with the current system which uses the ofboz.docs.org site to store the data.
The new help system has a number of advantages over the old version:
1. complete multilanguage without config xml files, using the locale.
2. Having an automatic multilevel index of all help pages using the ContentAssoc entity
3. Using the content manager for retrieval.
4. Template driven, aware of the different visual themes.
5. A first step towards the storage of OFBiz documentation within the OFBiz system itself.
6. Easy update via normal svn in seed data.
7. Aware of portlets on (userdefined) Portal pages.
8. Create awareness of the capabilities of the content component
The reason of this development was the requirement to provide user documents to the customers of Antwebsystems Co.Ltd
Some of the possible extensions could be:
1. a search function
2. print all or specific help files in PDF format
3. make the help screens work better with the business theme
4. Explain how help can be extended
5. In the help screen be able to send a message to the local support team
6. But most of all, create more help content!
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@804546 13f79535-47bb-0310-9956-ffa450edef68