The assertion in
https://stackoverflow.com/questions/9431352/vaadin-vs-bootstrap that
Vaadin is desktop-only appears to be wrong. The notice for the
discontinuation of the TouchKit add-on for Vaadin
(https://vaadin.com/blog/-/blogs/touchkit-is-dead-long-live-touchkit)
cites Vaadin's improving support for mobile as the reason for
discontinuing the add-on.
Obviously we need OFBiz to be usable on both desktops (think back-office
users) and mobiles (think warehouse, fleet operations, POS, road
warriors, etc.)
There's at least one add-on to use Bootstrap with Vaadin
(https://vaadin.com/directory#!addon/vaadstrap).
Disclaimer: my total experience with Vaadin is installing it once or twice.
Richard.
Rishi Solanki wrote:
Team,
I have gone thru the basic tutorial
<https://vaadin.com/docs/-/part/framework/tutorial.html> and setup vaadin
at my machine to understand and compare it with bootstrap.
Found this is very effective library to build UI as per our requirement.
But it won't give control over HTML and CSS, rather it generates the it.
The UI behavior can be override but we won't have the full control over the
markup and css generated. Also discussion on google says it has limit to
develop only the desktop application or ui. With all these details I'm also
agree with Julien, Taher and Jacques on fact we should have theme uses
vaadin, bootstrap and any other ui framework in future.
Here is good reference:
https://stackoverflow.com/questions/9431352/vaadin-vs-bootstrap
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co
On Fri, Sep 8, 2017 at 7:14 AM, Hans Bakker <h.bak...@antwebsystems.com>
wrote:
Hi Michael,
The main advantage i see is that Vaadin is like ofbiz screens/forms in
that you do not need to know css/html/javasccript to create an application,
but Vaadin is developed much further having much more add-ons. Further
Vaadin has a much larger user base.
They both have limitations in the html layout although in Vaadin they are
much less of a disadvantage.
A further advantage is that it is possible to convert from ofbiz
screens/forms to Vaadin so we do not have to re-create the 2000+
screens/forms we have, not sure about bootstrap?
As I see it Bootstrap is a further development of the ofbiz screens/forms
which functions however are currently already available in Vaadin but
allows you full flexibility of the html interface which you do not have in
Vaadin.
So in my opinion both Bootstrap and Vaadin have their pros/cons.
More opinions on the internet, search for 'Why Vaadin'
Regards,
Hans
On 07/09/17 15:02, Michael Brohl wrote:
Hi Hans,
can you give us some thoughts how Vaadin would be a better approach than
using a modern bootstrap theme (see Nicolas' efforts on the common theme)?
Thanks and regards,
Michael
Am 29.08.17 um 03:36 schrieb Hans Bakker:
Users/developers,
I would like to present an alternative UI which can be generated from
the existing OFBiz screens and forms but can also be used independently.
What is Vaadin: https://vaadin.com/introduction
Vaadin has the Apache 2.0 license.
We have now completed a proof of concept which can display Vaadin
screens in Java generated from OFBiz screens and forms using the existing
ftl macro file which currently generates html but now for a very limited
number of screen elements can generate also Vaadin Java screen files.
To demonstrate this in a component which can be either installed in the
OFBiz trunk or in V16 can be cloned from our git repository at:
https://gerrit.antwebsystems.com/#/admin/projects/vaadin-test
Check the readme file for installation notes.
To save you the installation we have also a demo system:
Ofbiz screen and form:
https://vaadin-test.growerpdemo.com/vaadin-test/control/ofbiz/main
Generated Vaadim screen:
https://vaadin-test.growerpdemo.com/vaadin-test/control/ofbiz/#!TestView
We would like to know from the community:
1. Technical opinion about this proof of concept implementation.
2. Is this something to be included in the OFBiz trunk as alternative UI?
3. Are there developers who like to work together to extend this
implementation:
a. cover all screen elements
b. use Groovy instead of Java.
Looking forward to your replies,
Regards,
Hans Bakker
Antwebsystems.com
T
--
Regards,
Hans Bakker
CEO, http://antwebsystems.com
