into a global helper method. Eventually, this method will be altered to
be able to 'change' which screen is actually included, based on various
conditions at runtime. This will be used to eventually support partial
ajax page updates.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@995206 13f79535-47bb-0310-9956-ffa450edef68
1: product detail hard-coded the width of the image, even if the actual
image was smaller.
2: products with surveys(gift card purchase) were overly large, which
caused them to float below the left content.
3: the header on productcategory listings had background lines that
overflowed underneath the left and right columns.
The ecommerce app is now closer to something we'd actually show a real
customer, in its default configuration.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@995198 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
It uses the description (Id) shown with the Name. Hence the Lookup screen must be set in order to show a description in the autocomplete part.
It seems this is not always easy notably when you need to show at least 2 parts for the Name (eg Person).
At least it easy to set and it works well for simples case for now (eg PartyGroup)
I did not find another way since Ajax.Autocompleter can't update another field.
The alternative would be navigation to the next hidden field, at least it would avoid the mandatory Id/Name pair.
But it's more difficult to demonstrate in Example component
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@993508 13f79535-47bb-0310-9956-ffa450edef68
It should be further improved since at the moment numbers are sorted as strings (10 is sorted before 2).
This is a new pattern that can be used to sort columns in forms where data come from Maps not directly retrieved from Entities.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@992682 13f79535-47bb-0310-9956-ffa450edef68
Tried to invoke method UtilIO.writeObject() but found the following code
try {
StringWriter writer = new StringWriter();
if (encodeObject(writer, value, allowJsonResolve)) { sb.append(writer.toString()); return; }
} catch (Exception e) {
}
throw new IOException("Can't write (" + value + ")");
It caused the method to always throw an IOException.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@991485 13f79535-47bb-0310-9956-ffa450edef68
UPS Online shipping rates are showing wrong values when product weight having different weightUomId. It doesn't support UOM Conversion as it is working in USPS services.
So fixing this bug, following work is done.
1) Calling generic methods "getPackageSplit", "getProductItemInfo" & "calcPackageWeight" methods from ShipmentWorker.java
2) Removed duplicate methods from UpsServices.java
Thanks Amit for the contribution.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@990751 13f79535-47bb-0310-9956-ffa450edef68
The condition-object element used to have an attribute named "field-name" which was later replaced with "field" but the code was instead checking for "field-name" and then "name".
Fixed so that the code checks for "field" and then "field-name".
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@990347 13f79535-47bb-0310-9956-ffa450edef68
Issue with the Xml Export: it seems that there is an issue with the each() loop in Groovy, during the export OFBiz throws a lot of warnings which regards to an wrong used iterator.
So i changed the each() loop into a normal iterator which solves the issue.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@990339 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