And definitively fixes issues with i18n of geolocation
It introduces a "locale" attribute to the "set" operation in widget (I only tested screen, form is quite similar, should be ok) and minilang.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1554681 13f79535-47bb-0310-9956-ffa450edef68
Actually it does paginate but the value is not dependent on widget property widget.form.defaultViewSize which default value is 20. It uses a default value of 50 which is defined by
<set field="viewSize" from-field="parameters.VIEW_SIZE" type="Integer" default-value="3"/>
You can easily test it using https://localhost:8443/manufacturing/control/FindRouting?VIEW_SIZE=3
This is legacy from pre Apache era. I found 143 cases where a default-value is defined in screens for VIEW_SIZE.
I did not look into details for the 143 cases but I believe most are also legacy.
There are few default values: 10, 20, 30, 50, 500 and even an extreme case of 10000 for InventoryItemTotalsExport!
There is only one comment for LookupBulkAddProducts which is also legacy: <!-- 10 rows seems more appropriate given screen size, etc. -->
I suggest to OOTB replace all those by the widget.form.defaultViewSize value.
Things will then be consistent and easily changeable on a global scale using the widget property.
Or if really needed forcing the default-value as it's done now.
So this would be applied on the 143 cases (I checked, viewSizeDefaultValue does not exist in any screen)
<property-to-field resource="widget" property="widget.form.defaultViewSize" field="viewSizeDefaultValue"/>
<set field="viewSize" from-field="parameters.VIEW_SIZE" type="Integer" default-value="${viewSizeDefaultValue}"/>
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1526387 13f79535-47bb-0310-9956-ffa450edef68
"other-field-size" of drop-down form element is a very nice feature, but it's crippled in current version.
attached a patch to make it works and added an example section for that into FormWidgetExample.
jleroux: Interesting, I did not know this feature existed, it was committed long ago by David (before ASF era)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1511279 13f79535-47bb-0310-9956-ffa450edef68
Application menu item should be link not hidden form. As if its hidden form then you can not open it in new tab.
Default menu item link type auto, and its create an hidden for for link if controller request call an event, but in menu item this should be link.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1500382 13f79535-47bb-0310-9956-ffa450edef68
1) layered lookup std
2) read only layered lookup std
Changes the way the explanation are displayed, now using tooltips for an easier reading
Changes all explanation tooltips style to button-text for a better legibility
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1369558 13f79535-47bb-0310-9956-ffa450edef68
Problem path 1:
Find Example > Find Example
Select EX01
Click Items Tab (or Features)
Click Example Tab
Expected: Example Details form in the context of the Example menus
Actual: New Example Form under Example Application menus
Problem path 2:
Example > click New Example
Enter a new example
Expected: Example Details form to add Items and Features to the New Example
Actual: Example page filtered on newly created example
(this is a problem for a new user who will not know how to clear the Example Id from the Search Options form. A better path would be to go to the edit forms where the user can add additional information on the example i.e. Items and Features)
Problem path 3:
Features > New Example Features
Enter a Description > Click Create
Enter a Type and Sequence Num
Click Add
Expected: Create a new Example Feature Appl
Actual: Error Problem 3: Error missing exampleFeatureId
jleroux: just put comments about checks Tom wanted to remove: <!-- This is a check useful when only seed data are loaded -->
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1361662 13f79535-47bb-0310-9956-ffa450edef68
Now it will be very easy to extract the birt component (for OFBiz Extras) or to disable it when deploying to production or when interested in sparing some hardware resources. I did some cursory tests but since the work has been challenging and rather complex I would appreciate testing help and also reviews to finds chunks of code that I could have missed and that could be moved out as well.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose@1361130 13f79535-47bb-0310-9956-ffa450edef68