David E Jones wrote:
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

Oh geez, that was years ago... I vaguely remember the main complaint being you couldn't share scripts and templates between components. There were one or two more issues I can't recall - I just remember thinking to myself that those issues could be fixed by changing a few JPublish configuration xml files.

With a little research and a little effort we were able to have global scripts and global templates. In addition, components shared bits of bsh and ftl, etc. We broke down common screen elements into reusable pieces and shared them between components.

I'm sure you are aware of issues that I'm not aware of. Maybe this is a good time to go over them and see if they have been fixed. Not that I'm trying to push JPublish or anything, but since the subject has come up, why not look into it again?

-Adrian

Reply via email to