Based on a recent dev mailing list discussion, I added a page to the Example component that demonstrates some basic layout concepts. The idea is to display the page, then look at the screen widget definition and the HTML markup to see how the page is constructed.
The page can also be used for visual theme development - because most of the common UI elements are all on one page.
This could be improved - it needs a multi-column layout example, a tree widget example, and a form widget field group example.
Internationalization note: This commit contains new UI labels.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1059429 13f79535-47bb-0310-9956-ffa450edef68
This cames from Adam's advice: http://markmail.org/message/kai5lfvlnsz7xwki
Sascha comes to this solution
The Idea is to have a method which takes a JSON Object with uiLabel Resources and label entries and returns the resolved labels in a JSON Object which can be used directly in the JS Code.
The advantage of this way, is that we have only one Ajax request which reads all labels. The alternative is an Ajax request for each label, which simplify the request (because you haven't to create a complex JSON Object) but is very expansive.
* Replaces all JS alerts with the new fancy error boxes
* Adds a few uiLabels
I simply fixed some typos. I did not test all cases but did a good review.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1056497 13f79535-47bb-0310-9956-ffa450edef68
Using this widget, a PortalPage can now be easily rendered in any screen.
At the bottom of the page an "Edit ON/OFF" button can be used to switch the PortalPage edit mode ON and OFF so that the Portal Page can be edited "in place".
All the portlet editing requests are handled using the "save-last-view" request attribute so that a dedicated screen can be shown to set the Portlet attributes and the column width and, when submitted, the user is taken back to the portal page he was editing.
Those new requests will be used in a later commit to eliminate all the duplicated ****Adm requests that have been introduced when the Webtools portal admin screen has been created.
A simple use of the widget has been added in the Example application.
TODO:
- At the moment the portal page editing is performed on the portal page itself and no portal derivation from the "main" one is performed. This will be done in a later commit.
- The portlet moving controls both manually and by drag and drop have not been implemented yet.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@998570 13f79535-47bb-0310-9956-ffa450edef68
The 1st one, country/states, is a common one and does not need (ie it's better to not) to be generalized. It can be used as is. It needs some pieces which are all included, see comments and follow...
The 2d, category/products, have been taken as example but is not a good candidate. What if you get much categ or/and products? Anyway it's a good OOTB example and I had it at hand, so I used it. I have tried to generalize (abstract the couple of dropdowns) and it's almost there. The only issue I crossed, is when you want to use a couple of dependent drop-downs in the same form. As it's not a common case, the setDependentDropdownValuesJs.ftl template-script can be used in most cases...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@986370 13f79535-47bb-0310-9956-ffa450edef68
For the pagination issue in bluelight and droppingcrumbs, the calendar issue in bluelight still exists
I have also added 2 lookup and calendar test fields in the 2d lookups.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@940234 13f79535-47bb-0310-9956-ffa450edef68
Simply encoding the tooltip (why I did not think about that before, really sometimes I wonder how my brain is working, I need to stop working for it to begin to work)
There are no needs to encode char like >, but of course < is needed (in he XML file) since else there is a problem in the XML labels file (always the same issue: around vs inside)
So yes, it's only a matter of encoding at the right place, ie before the "around vs inside" issue arises
Good night ;)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@921643 13f79535-47bb-0310-9956-ffa450edef68
+ some correct changes done with this update of Labels Manager (I updated some wrong ones by hand to keep going forward...)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@739955 13f79535-47bb-0310-9956-ffa450edef68
It was a real mess. I wondered if I should put them all under a ComonCompanySubtitle label and remove all others.
But I guess they could be used with other meaning in real world applications (ie not OOTB). So I kept them all.
There are some duplicates in some languages. I kept them commentent out at end of each line.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@728061 13f79535-47bb-0310-9956-ffa450edef68
The original Ajax work was a great start, but there were limitations. These changes open things up a bit: 1) Ajax rendering falls back to plain HTML when the user has JavaScript disabled. 2) You can have more than one area updated during an event.
IE7 updates only <div> elements, so be aware of that when using the Ajax feature.
See the Example component for a demonstration.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@658281 13f79535-47bb-0310-9956-ffa450edef68
I used Subclipse to rename the file so hopefully it comes through as a rename rather than delete and add
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@607828 13f79535-47bb-0310-9956-ffa450edef68