To test :
* apply patch
* apply patch from OFBiz-4262
* load seed
* Go to example and add examplePortlet2 to an example pagePortal
* Edit examplePortlet2
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1096290 13f79535-47bb-0310-9956-ffa450edef68
Adds the possibility to use famfamfam icons contained in framework/images/webapp/images/famfamfam/icons.
If you want use a specific icon, it's possible to define an attribute VT_ICONS_LOC that contains the location to themes icons directory to use
It improves form rendering to pass a flexible string on image-location attribute and screen and form renderer to display an image with a text.
JLR: I just added à before menus texts
After Erwan's remark I wondered If I should remove the CSS on buttons. But I finally found that it was complementary. Because when no image is used on a specific button you still have the default CSS style applied (typical for Add buttons as Erwan outlined). And when no default CSS style is applied you can have an image like now shown OTTB on print button when editing an Example. So I see these 2 features as complementary for now. Maybe one day, one will replace the other, but at this stage both are welcome IMO.
BTW the famfamfam (strange name ;o) icons lib is well done and really full of possibilities...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1095984 13f79535-47bb-0310-9956-ffa450edef68
Orig. Msg.:
now there is a problem when you click on an example to edit it, the decorator is no more present on the form.
to reproduce
In example component, search all examples the click on an id.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1072303 13f79535-47bb-0310-9956-ffa450edef68
I created a new Screen <link feature. Similar to the Form Lookups a link can be opened in a layered JS Box (see Screenshot in Jira Task). It looks nice and is helpful in some cases.
You can add any screen u want. It's expected that you create a certain screen for the layered link which only contains the information you need.
The layered box doesn't contain any logic it's just a container for the screen which should be opened. So the screen it self can decide what to show. i.e if you load a form, the form itself implement the way how it react on a submit (either reload the site or perform the submit as Ajax request in the background).
There is also an example in the example section. Try to create a new Example on the mainpage.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1071698 13f79535-47bb-0310-9956-ffa450edef68
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
The issues already fixed were
* A Save File dialog box pop up to save a json file
* Creation did not update the list
* You can't edit the column "Name" content
* Sometimes it worked on an instance, not another (both with same configuration)
* Sometimes the same instance, which did not work before, worked
I found another issue, the line
<on-event-update-area event-type="submit" area-id="EditExampleAjax" area-target="CreateExampleFormOnly">
was duplicating the list and hiding the create section.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1056824 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
All Portlet screens should always load all needed UI resources since they can be rendered in different PortalPages that cannot be aware of what resources are needed.
This change will allow to eliminate all UI label resources loading in MyPortal decorators so that MyPortal will not depend on so many other components.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@995975 13f79535-47bb-0310-9956-ffa450edef68
I began to clean and make things consistent for lookups (in order to demonstrate the new Name/id mechanism) but then I realized that it should use Example entity and not Party. I will change that later and will remove all out-of-framework dependencies in the Example component
* I have added an example of the new Name/id mechanism
* I removed deprecated snippets in ExampleForms (some were already commented out) and used rather LookupExampleFeature enhanced with autocomplete
* In FormWidgetExampleForms.xml I tried to clean things for the autocomplete in the 1st lookup, but I thing there is an issue when more than one name field is retrieved. It does not behave consistently, try for a Person and a PartyGroup for instance...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@993527 13f79535-47bb-0310-9956-ffa450edef68
I finally decided to use the new Dependent Dropdowns mechanim.
I have also refined how it's used in Example to avoid confusion, so changed setDependentDropdownValuesJs.ftl to pass paramKey when it's different from mainId
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@988508 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