If you define a dateTime field like that :
<field name="estimatedStartDate"><date-time input-method="time-dropdown" step="10"/></field>
and pass in context : estimatedStartDate = "2011-06-016 20:30:00"
when you edit the form, estimatedStartDate takes the good value 2011-06-016 on date, but takes nowTimestamps.hour for dropdown hour instead of 20 and nowTimestamps.minutes for dropdown minutes instead of 30
To test the patch :
go to ofbiz example component with given date : "https://localhost:8443/example/control/FormWidgetExamples?field4=2001-01-01 02:21:000"
the field 4 must have hour to 02 and minutes to 21
The patch also corrects multiple definition : sr.append("\" value=\"");
and removes unneeded escape at end line : if (UtilValidate.isEmpty(requiredStyle)) requiredStyle = "required";
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1139385 13f79535-47bb-0310-9956-ffa450edef68
When I open a form which include lookup field and then click the expand/collapse button around the upper right corner in the the header, the page will go to "main" after user preference is settled.
The cause is the requests initiated by lookup field does not remember the last view name. It simply use "main" instead.
Patch to make lookup requests remember the LAST_VIEW_NAME correctly.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1137433 13f79535-47bb-0310-9956-ffa450edef68
A slightly modified patch from Leon which corrects the href tag of empty leaf nodes.
OrigMsg:
like department and employee tree in main page of human resource management application, if you click the expand/collpase link of a leaf node, the wrong request error occurs. Since there's a empty link href value set for leaf node, browser will treat it as the request "https://.../humanres/control".
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1135929 13f79535-47bb-0310-9956-ffa450edef68
When I 1st wrote this I used delay instead of defaultDelay. I then changed the name but forgot to change in widget.properties file. I wanted to keep it commented out to have default value commented out (Convention over configuration) but it would be more complicated and anyway would not follow how it's done in widget.properties
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1129036 13f79535-47bb-0310-9956-ffa450edef68
Lookup tag has a attribute "disabled" that is used to set disabled="disabled" property for lookup input element and it create also a clear button just after lookup field to clear the field value.
But if we set disabled="disabled" for any input field then that field does not passes as parameter and we can't accesses it from parameters or request parameters , so it should be "readonly".
If we set readonly-"readonly" then user can't change the field value directly, and this field passes as parameters.
Only difference between readonly and disabled is that in case of disabled field does not passes as parameter buy in case of readonly field passes as a parameter.
Thanks Deepak for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1098082 13f79535-47bb-0310-9956-ffa450edef68
Initial demand by Michael Pätzold
At the moment we concentrate on increasing the usability of the backend application. One thing we recognized is the way form errors are reported to the users. Now it's done by showing a list of entity fields, that are required. A more common approach would be to highlight the form controls, that were not/wrongly filled. Was/Is there any task related to that or something similar?
Nicolas's solution
With integration of JQuery and validate function integrate by Sascha, I extend the Form renderer to apply required class and alert the form when she submitted to pass by JQuery validate function.
JLR: I have added a required field to InternalName field in Edit Product Form. There are maybe other cases like that which should be improved...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1096293 13f79535-47bb-0310-9956-ffa450edef68
When you use auto-field-entity on a form , you get a nullPointer :
java.lang.NullPointerException
org.ofbiz.widget.form.ModelFormField$DisplayField.getImageLocation(ModelFormField.java:2122)
org.ofbiz.widget.form.MacroFormRenderer.renderDisplayField(MacroFormRenderer.java:193)
org.ofbiz.widget.form.ModelFormField$DisplayField.renderFieldString(ModelFormField.java:2104)
org.ofbiz.widget.form.ModelFormField.renderFieldString(ModelFormField.java:600)
org.ofbiz.widget.form.ModelForm.renderItemRow(ModelForm.java:1707)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1096140 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
This allows the Navigation bar to be rendered closed to the form itself.
It seems very hard to reduce the BR height using the CSS only.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1091487 13f79535-47bb-0310-9956-ffa450edef68
An improved patch for target-parameter functionality, now paramI indexing start with I=0 instead of 1.
JLR: I have updated the XSD to tell it must begin at 0
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1085671 13f79535-47bb-0310-9956-ffa450edef68
The sort-order block was not extended when you extend a form. So you had to duplicate it in case it was the same.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1082134 13f79535-47bb-0310-9956-ffa450edef68