[
https://issues.apache.org/jira/browse/OFBIZ-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234389#comment-13234389
]
Olivier Heintz commented on OFBIZ-4742:
---------------------------------------
Technical choices :
- add some fields in PortalPortlet entity (add fieldDescription in entityLabel
to have auto help)
- add PortletType entity, which link id to a screenLocation#screenName for
portlet Template
- portlet template are based on screenlet
- add portalPortletId and portletSeqId as optional attributes in
include-portal-page
- update include-portal-page java process to put in context some of
PortalPortlet fields, to be usable by portlet templates. Value coming from
entity or default value calculation.
- add show-portlet as field type in Form with similar properties than
hyperlink. Same for Menu.
Sub Task of this Jira :
1) icon-purpose : same concept as uiLabel but for icons, a property file to
address icons by a logical name
2) portlet-example : example portalPage with portlet using new functionality
3) portlet-help : help file on development using portlet
4) portletUilabel : add a portlet decorator by component to be sure that a
portlet from a component can be used in an other component without label problem
5) Some generic PortletEditForm, usually needed
6) screenlet list navigation : solve two problems,
first) screenlet navigation bar currently generate problem with listIterator,
second) currenlty not working with ajax (on-event-update-area)
7) add field new-line in PortalColumn, to be able to have multiple "line" in
PortalPage, ex: top of screen two column and bottom only one column, like in
ProjectPage
> Portlet Widget
> --------------
>
> Key: OFBIZ-4742
> URL: https://issues.apache.org/jira/browse/OFBIZ-4742
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Olivier Heintz
>
> Description: Goals of this enhancement are :
> - simplification of portlet development by use of portlet Templates
> (PortletType), so most of the time, it's sufficient to define a form to have
> a portlet
> - default value of formName, menuName, ScreenName, ScriptName, Title, ...
> (name and location) based on component, subcomponent, webapp of the portlet
> - ajax call defined with xml syntax (new show-portlet on form and menu)
> - default parameters list in ajax link (show-portlet or on-event-update-area)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
