Compiere has a similar "auto-deploy" mechanism. So that solves the "deploy" issue. There's still
the issue of creating and maintaining 2 separate UI modules: one for Java app, the other for browser.
Which reminds me. OFBiz browser UIs don't care about the case where javascript is disabled.
Anyway, javascript can be selectively enabled (in the browser) for sites that the end-user trusts.
The only place where this could be a problem is in the ecommmerce side, the public-facing end. In
backoffice UIs, it's to mandate javascript.
Jonathon
Raj Saini wrote:
I was thinking more in terms of IT department savings. The
"create/maintain/deploy" human activities can be quite a bit more
expensive (IT consultants) than backoffice personnel, I would think.
Is that the case where you are?
With the new update technologies, I don't think this is a issue now.
Take example how Firefox updates itself without going through the pain
of manual deployment. Eclipse RCP has similar update manager, which is
used by Eclipse RCP based applications for auto update the new releases.
Thanks,
Raj
