You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "David E. Jones (JIRA)" <ji...@apache.org> on 2006/06/27 07:19:30 UTC
[jira] Commented: (OFBIZ-52) Add target-date and map-key to
sub-content widget
[ http://issues.apache.org/jira/browse/OFBIZ-52?page=comments#action_12417958 ]
David E. Jones commented on OFBIZ-52:
-------------------------------------
What would be really nice for the date to use thingy (we might want something better for the names than target-dates, unless I'm misunderstanding what it is supposed to mean) is something more global that would be used for things other than just this one little sub-widget of the screen widget. It would be really cool in fact to be able to specify a virtual date/time override to use... Perhaps per-action and per-widget and such attributes will be the only real way to go.
As for the "map-key" element: do you mean to replace the current attribute for that? It doesn't have a name that is consistent with the entity name (which I would love to change because I hate it when things are like that), instead of the current one, namely the "assoc-name" attribute.
There is actually an example that uses this stuff now in the ecommerce component, just search for "sub-content" in the CommonScreens.xml file in the ecommerce component.
> Add target-date and map-key to sub-content widget
> -------------------------------------------------
>
> Key: OFBIZ-52
> URL: http://issues.apache.org/jira/browse/OFBIZ-52
> Project: The Open For Business Project
> Type: Improvement
> Components: framework
> Versions: SVN trunk
> Reporter: Al Byers
> Priority: Minor
>
> The sub-content widget displays data related to the supplied contentId. It has probably never been used, but if it were used, it would be nice to specify specific map-key values and target-dates (now, it defaults to the current time). That way it could be used to show "back issues" of content.
> I would create the patch if this is a go.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira