[ https://issues.apache.org/jira/browse/OFBIZ-13049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845546#comment-17845546 ]
Jacques Le Roux edited comment on OFBIZ-13049 at 5/11/24 8:00 AM: ------------------------------------------------------------------ Hi Pierre, I re-read the comments above where Daniel and Michael were not enthusiast. This happened already with Mathieu and Nicolas in https://lists.apache.org/thread/wk0q5m409mm96kqsgymq6fhrsy7j7xvo. And Nicolas had a not so postive experience with portals. So there are obviously drawbacks. What are the advantages that decided you to use portals? In this thread, there is a point that held my attention. Mathieu said: bq. In any case providing a precise XML schema for screen/form elements is definitely a good idea. We already have that, that maybe could be improved. But we really miss the same for data used to define portals. So I strongly suggest that we create a shema for *PortletData.xml files. It should not be hard to create. It would help possible customers to create their own portals with a bit of documentation that seriously lacks for now. I also note that while adding the reference to a new PortletData.xsd in *PortletData.xml files we should correctly format files that are difficult to read when needed. CommonPortletData.xml comes to mind. Would you mind to assume this task before we continue with subtasks here? Edit: I just realise that Mathieu was answering to Olivier's idea: bq. create a widget-portal.xsd was (Author: jacques.le.roux): Hi Pierre, I re-read the comments above where Daniel and Michael were not enthusiast. This happened already with Mathieu and Nicolas in https://lists.apache.org/thread/wk0q5m409mm96kqsgymq6fhrsy7j7xvo. And Nicolas had a not so postive experience with portals. So there are obviously drawbacks. What are the advantages that decided you to use portals? In this thread, there is a point that held my attention. Mathieu said: bq. In any case providing a precise XML schema for screen/form elements is definitely a good idea. We already have that, that maybe could be improved. But we really miss the same for data used to define portals. So I strongly suggest that we create a shema for *PortletData.xml files. It should not be hard to create. It would help possible customers to create their own portals with a bit of documentation that seriously lacks for now. I also note that while adding the reference to a new PortletData.xsd in *PortletData.xml files we should correctly format files that are difficult to read when needed. CommonPortletData.xml comes to mind. Would you mind to assume this task before we continue with subtasks here? > Configurable Main page > ---------------------- > > Key: OFBIZ-13049 > URL: https://issues.apache.org/jira/browse/OFBIZ-13049 > Project: OFBiz > Issue Type: Improvement > Components: ALL APPLICATIONS > Reporter: Pierre Smits > Priority: Major > > Currently the OFBiz product has configurable Main pages in applications > Accounting, Order, SFA, and plugin MyPortal. Unfortunately, none in the > community felt the urge to implement the concept further in other > applications. > Having a configurable Main page of an application improves both the appeal of > OFBiz to (potential) adopters and their users, and to developers. > With a configurable Main page, developers have less screens to consider when > doing customisation, while at the same time trying to stay in sync with > changes from the project. -- This message was sent by Atlassian Jira (v8.20.10#820010)