In the Webtools we can asociate Geos but we have yet no means to untie them
This patch adds a new grid in EditGeoScreen to see/delete GeoAssoc and CommonEntityLabels default-resource-name on GeoAssocType for translation purpose.
jleroux: On Pierre's Smits suggestion Gil also added a clickable link to open the associated Geo and a column to show the geoTypeId of the associated Geo.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1687259 13f79535-47bb-0310-9956-ffa450edef68
Fix the following problems:
- The search screen results take you to the link geos.
it should go directly to create / edit instead
- You cannot edit a geo because the parameter is not passed across
the tabs link and edit / create. The menus should be redefined
to pass the parameter around
- The primary key is enforced in the service definition when
it should be optional to create new geos
- finally, the geoId should not be a lookup field as
an entity cannot lookup itself
Refs https://issues.apache.org/jira/browse/OFBIZ-6229
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1682415 13f79535-47bb-0310-9956-ffa450edef68
* Now the link from the Find list goes to the Link Geo screen. It opens (focus on Geo field) with selected multiples (in function of assoc type) for the geo selected in Find list, and changes accordingly. In jQuery branch it will use asmselect for that
* So the Create screen is now a Create/Edit screen with a lookup for Geo choice
This continues to allow geos Edition/Creation and to links them, but now shows also the links between geos in the Link screen. Due to native limitations of select multiples, it's not very useful in trunk but interesting in jQuery branch (I did not try to find an equivalent to asmselect in the Prototype worls, still doable...)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1000586 13f79535-47bb-0310-9956-ffa450edef68
For the moment in trunk the Link Geos screen use a standard multiple dropdown. It's not easy to use (see why at http://www.ryancramer.com/journal/entries/select_multiple). In the jQuery branch I have used the asmselect plugin, much easier for end users. Actually I'm not totally satisfied by it either. It's a beta and seems to be freezed. Also the way the field is shown is not flexible enough. It's a fixed size area and I tried to work around. I could be done better though. I will have a look. Sascha thought we could use jQuery.ui.sortable but I don't think it exactly corresponds to the feature needed.
I have also changed some labels names and removed/grouped some requests (only in common now)
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@996658 13f79535-47bb-0310-9956-ffa450edef68