Use the Screen Widget. You can use FTL/BSH/etc with the screen widget where 
needed (as is done in the ecommerce webapp), but the Form and other widgets 
will make things easier for most applications where look and feel is not the #1 
priority.

The Screen Widget is far more flexible, powerful, and easier to maintain than 
either JPublish or Region based views.

JPublish is no longer maintained as an open source project and hasn't seen 
activity in years. It is being 100% phased out from OFBiz.

Region based views with JSPs have no good method of separating data preparation 
from presentation and are in general a nightmare to maintain and usually 
require significantly more code and more complicated code than an equivalent 
implementation with the newer tools.

This is the established best practice for OFBiz. For more information, see the 
Best Practices Guide and review the Framework Introduction videos.

-David


Fabian Gorsler wrote:
Hi,

after my data model is ready, I know how to use services, the next
question for me is which UI-layer to choose. I've read, listened to the
videos, reviewed apps (i.e. webtools), but the more I look for possible
ways, the more I loose a real oppinion what to use.

- Freemarker, JPublish and BSH look nice and quite simple.
- Screens/Widgets seem to be a very good technic for RAD, but for me it looks as if this wouldn't be as flexible as FTL/JP/BSH or JSPs.
- JSPs combined with Regions seem to be a very powerful and quick way
for developing with much flexibility.

I hope you can understand my problem: There are so many possibilities, but
up to now I got no real opinion what I should use. The most important
thing is, that I don't know which way offers me all features OFBiz has.
Ok, it's possible to combine things, but I prefer a clear solution with
a strict way. I think for later developers it'll be much easier to
develop the app.

Can anybody of you push me to the most effective way? At the moment I'm
thinking about using FTL/JP/BSH or JSPs, but... Yes, I can't get an real
opinion...

TIA :)

Best regards,
     Fabian.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to