We should really do the other way round: if there are issues in the
current widget implementation that we should discuss them in details and
find the best way to fix them.
I really think it is a waste of time to discuss these subjects for the
sake of discussion... there are so many options and technologies
available in the World and if we start a thread for each of them then we
will completely stop the development of OFBiz, i.e. the development of
an open source ERP system.
Jacopo
Jacques Le Roux wrote:
David,
It would be very interesting if you could dress a list of all these problems or
maybe the more importants. Then we (OFBiz
developpers and users) would have solids arguments to choose between the future
JPublish version and the widgets. BTW I like to work
with the widgets but I don't know much about JPublish...
Thanks
Jacques
PS : I may help to retrieve them from the old MLs and such if some pointers
still exist...
De : "David E Jones" <[EMAIL PROTECTED]>
Adrian Crum wrote:
David E Jones wrote:
Even still, I think it is more than just a matter of preference. There
are significant developer efficiency, design flexibility, and code
organization problems with JPublish that were solved with the Screen
Widget. Our motive with the Screen Widget was to solve those problems
and improve various things... not to just get rid of JPublish (there
was no library conflict at the time, that was about 2 years later).
This point may be moot now, but at the time OFBiz was using JPublish I
was able to solve many of those problems on my local copy. It turned out
that JPublish wasn't configured correctly in OFBiz. By the time I
submitted my fixes to Jira, the decision had already been made to switch
over to widgets, so the fixes never made their way into the project.
So, from my perspective the change from JPublish to screen widgets was
imperceptible - because the "problems" the widgets solved didn't exist
on my copy.
Could you be more specific about the "problems" you were working on?
My reason for asking is probably fairly clear: there were lots of issues and
limitations and things that weren't terribly
efficient or flexible... the list goes into the dozens of items so I'm
wondering which you found solutions to.
-David
