[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882307#comment-13882307
]
Paul Piper edited comment on OFBIZ-5040 at 1/26/14 2:06 PM:
------------------------------------------------------------
I am still not in favor of either the guideline or misusing this thread to push
"widgets" into the app-creation process. This ticket was mainly here for
clean-up purposes and to find a common ground for introducing html changes in
the future, not for pushing the widget technology, which is another debate.
To add my two cents, however, here is why i think the first point of the
guideline should not be added:
1) The guideline is marked to fail, since developers will always go with a
technology that is easy to adapt & learn, as well as commonly used. OFBiz is
the only system that uses the Widget-Language and lacks a decent documentation
for it. If you were to enforce it, you would have to deny any contribution to
the project that doesn't follow this approach, which, given the already
mentioned unlikeliness of the technology to be picked up, is not only unwise,
but also unfair.
2) The tools you mention do not exist. You have an auto-complete function, yes,
but that's where the "toolset" ends. There are not navigational tools to go
through the often encapsuled widgets, so you have to dig through them
recursively.
3) Widgets are xml-based and xml-based languages have the tendency to create
cluttered source files. The already existent apps are actually a proof of point
in this regard and not much of a help to newcomers.
I could go on about the pros and cons, but in the end i believe that although
your goal is admirable (and i agree to it being a good idea to get apps back to
conformity before introducing html or js based frameworks), you will still have
to clean-up the html first and then rather focus on the introduction of a
replacement framework rather than switching over to "our own little technology".
This being said, I do agree with point 2. of your list.
was (Author: madppiper):
I am still not in favor of either the guideline or misusing this thread to push
"widgets" into the app-creation process. This ticket was mainly here for
clean-up purposes and to find a common ground for introducing html changes in
the future, not for pushing the widget technology, which is another debate.
To add my two cents, however, here is why i think the first point of the
guideline should not be added:
1) The guideline is marked to fail, since developers will always go with a
technology that is easy to adapt & learn, as well as commonly used. OFBiz is
the only system that uses the Widget-Language and lacks a decent documentation
for it. If you were to enforce it, you would have to deny any contribution to
the project that doesn't follow this approach, which, given the already
mentioned unlikeliness of the technology to be picked up, is not only unwise,
but also unfair.
2) The tools you mention do not exist. You have an auto-complete function, yes,
but that's where the "toolset" ends. There are not navigational tools to go
through the often encapsuled widgets, so you have to dig through them
recursively.
3) Widgets are xml-based and xml-based languages have the tendency to create
cluttered source files. The already existent apps are actually a proof of point
in this regard and not much of a help to newcomers.
I could go on about the pros and cons, but in the end i believe that although
your goal is admirable (and i agree to it being a good idea to get apps back to
conformity before introducing html or js based frameworks), you will still have
to clean-up the html first and then rather focus on the introduction of a
replacement framework rather than switching over to "our own little technology".
This being said, I do agree with points 2. of your list.
> Backend widget & application HTML clean-up
> ------------------------------------------
>
> Key: OFBIZ-5040
> URL: https://issues.apache.org/jira/browse/OFBIZ-5040
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
> Reporter: Paul Piper
> Labels: html, webapp, widget, widgetrendering
>
> I am sure that this is a common thing to know: the current backoffice
> application relies heavily on widgets. This is good, but the current
> standard-html-structure is not flexible enough and often lacks proper w3c
> implementation.
> To make matters worse, you can often find applications avoiding widgets at
> all and rather overriding the standards with custom ftl implementations. It
> is these customizations that break the html on numerous screens and make it
> difficult, if not tedious to create new themes for the backoffice.
> This task is hence to:
> * Find a consensus on a new widget standard
> * Go over each of the application ftls and convert these to the new standard
> * Recreate the themes and simplify/clean-up special rules
> Since redoing the theme is a rather large task, we should consider to add an
> additional css for now which stylises the replacement html instead of working
> with the old.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
