[
https://issues.apache.org/jira/browse/OFBIZ-13049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845587#comment-17845587
]
Daniel Watford commented on OFBIZ-13049:
----------------------------------------
Hi [~pierresmits]
{quote}Regarding the feedback from Daniel, I repeat what I commented earlier:
I am just utilising what is available OOTB. implemented and reviewed by quite a
few contributors in the period between 2008 and 2010 (amongst other Bruno
Busco, David Jones and even you) under ticket OFBIZ-1999 and follow-ups.
{quote}
I don't think you addressed my comment other than saying their is prior-art for
your suggestion. We also support mini-lang OOTB, but would not encourage its
use. A lot has changed in development approaches in the ~15 years since the
portlets proposed to try and contain definitions of systems as version
controllable code (e.g. infrastructure-as-code movements).
That being said, I do see frequent use of 'Dashboard Builders' in systems where
users can build their own dashboards out of 'widgets' to display information to
meet their needs. But the crucial difference is that these dashboard widgets
then provide links to standard pages where the users interact with entities.
The dashboards are a separate concern to the main system screens.
{quote} Introducing another layer of indirection via the database will reduce
the navigability of the UI further.
We use data everywhere to showcase the flexibility and usability of OFBiz. The
user experience (the appeal of OFBiz as an Open Source business management and
e-commerce solution) is dependent on data.
{quote}
Perhaps you it would help us understand your position if you provide some
non-portlet examples of how OFBiz uses data to dynamically to affect the user
experience.
{quote}I can imagine that a lot of developers (and their employers) could be
angry with their customization experience.
If only they would come forward and would make actionable suggestions (e.g. in
the form of Jira ticket), the project (and its contributors) would have
something to work with.
{quote}
Is there any evidence that people are angry with the customisation experience?
Users/Customisers are unlikely to monitor Jira, but they might raise their
concerns on the user mailing list if prompted.
However, even if users/customisers did highlight issues, portlets still might
not be a good solution.
With forthcoming work around REST, I think we might solutions on the
client-side might offer a customisation route without impacting on server-side
implementation.
As an example, SharePoint Online offers UI extension points in the
header/footer of a page where Javascript can render whatever if needs without
intereferring with SharePoint's own UI implementation -
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/extensions/overview-extensions
{quote}...can be improved by the community in a SMART way.
{quote}
Is SMART an acronym or are you just highlighting the word to try and imply that
an alternative approach is not smart? Use of the later technique is something
that really annoys me as they are normally an attempt to shutdown debate. I
have read the riot act to many a sales person that has begun a sentence with
'obviously'!
{quote}...seems to be something to discuss in dev ML. But IIRW you can't write
there, right?
{quote}
I think Jacques is right. This topic is too large to discuss in a Jira ticket's
comments as it will need support from the wider OFBiz developer community which
utilises the Dev mailing list.
Therefore I think you need to find a way to resolve the matters that currently
prevent your writing to the dev mailing list before we can progress this topic
further.
> 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
> Attachments: CommonPortletData.xml
>
>
> 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)
