OFBiz › OFBiz - User

Alternative UI: Vaadin proof of concept

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

14 messages Options

Hans Bakker

Alternative UI: Vaadin proof of concept

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

Deepak Agarwal-2

Re: Alternative UI: Vaadin proof of concept

This looks very interesting!

On Mon, Aug 28, 2017 at 9:36 PM, Hans Bakker <[hidden email]>
wrote:

> 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
>

--
Deepak Agarwal

+1 407 342 6910

marcopaul

Re: Alternative UI: Vaadin proof of concept

In reply to this post by Hans Bakker

Haven’t had time to dig into the code, but at a high level I feel Vaadin is one of the best bets for helping OFbiz get a modern UI and as a result much greater adoption!
—P

On Aug 28, 2017, 8:37 PM -0500, Hans Bakker <[hidden email]>, wrote:

> 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

Aishwary Shrivastava

Re: Alternative UI: Vaadin proof of concept

Vaadin looks amazing, definitely, a good and modern UX will make OFBiz an
Ace of all trades.

On Thu, Sep 7, 2017 at 1:16 AM, Paul Mandeltort <[hidden email]> wrote:

> Haven’t had time to dig into the code, but at a high level I feel Vaadin
> is one of the best bets for helping OFbiz get a modern UI and as a result
> much greater adoption!
> —P
>
> On Aug 28, 2017, 8:37 PM -0500, Hans Bakker <[hidden email]>,
> wrote:
> > 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
>

--
Best regards,
Aishwary Shrivastava
Enterprise Software Engineer
HotWax Systems <http://www.hotwaxsystems.com/>

Hans Bakker

Re: Alternative UI: Vaadin proof of concept

In reply to this post by Hans Bakker

Seeing that we get now more interest in this activity I can report that
we already made the demo version working with Groovy instead of Java for
the Vaadin screen definitions. This allows to change the OFBiz screens
and without restart show the generated Vaadin screens.

our current list of activity, yes, we need help:
1. use the Valo theme for the demo.

2. use the OFBiz controller.xml for Vaadin requests

3. retrieve data using OFBiz Groovy dsl

4. Complete the ftl macro file so we can generate Vaadin screens from
OFBiz screens/forms

Yes the current demo you can still clone from the GIT repository at:
https://gerrit.antwebsystems.com/#/admin/projects/vaadin-test
and use on the ofbiz-framework trunk which you can find at the SVN
repository at:
https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/trunk

comments and contributions welcome, we can give you access to this Git
repository.
Yes, just as OFBiz, everything is open source Apache 2.0

--

Regards,

Hans Bakker
CEO, http://antwebsystems.com

On 29/08/17 08:36, Hans Bakker wrote:

Michael Brohl-3

Re: Alternative UI: Vaadin proof of concept

In reply to this post by Hans Bakker

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

smime.p7s (5K) Download Attachment

Rajesh Mallah

Re: Alternative UI: Vaadin proof of concept

Hi Michael / All ,

I feel ERP kind of applications are mostly used from desktops.
Like desktop applications , The UI of OfBiz should empower endusers with
productivity features available in desktop applications.

One such feature is of accelerator or short cut keys which are very popular
among
users of accounting applications in particular.

I feel this factor should also be considered before making a consensus on
the choice
of UI technology.

Another factor is the performance of UI itself. No one likes to see their
primary
application lagging / hanging at workplace everyday. I would any day prefer
to use
a less aesthetic performant app to a nice looking sluggish app.

my 2 cents.

regds
mallah.

On Thu, Sep 7, 2017 at 1:32 PM, Michael Brohl <[hidden email]>
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
>>
>
>
>

Julien NICOLAS

Re: Alternative UI: Vaadin proof of concept

In reply to this post by Hans Bakker

Hello,

If I don't make mistakes, with common theme (thanks to Nicolas for
that), we don't need to 'define' a new technology. We don't need to
choose bootstrap or vaadin.

We only need one thing, we need somebody to make a new theme. If this
theme is using vaading, we wil see the power behind it.

My 2 cents,

Julien.

On 29/08/2017 03:36, Hans Bakker wrote:

> 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
>

taher

Re: Alternative UI: Vaadin proof of concept

I agree with Julien, and it is the reason we suggested in the first to
place starting the themes refactoring exercise. We needed to move
anything "web" related _outside_ the framework and then automate stuff
through macros.

If the work being done is isolated from the framework, then that would
be great and a good potential for incorporation into the themes
directory. If not, then maybe it needs to be refactored accordingly.

I think it is essential to stress the importance of keeping "web"
features outside the framework, which is clean separation between the
DSL driving the widgets and the underlying implementation (web is
_only one_ implementation).

On Thu, Sep 7, 2017 at 1:04 PM, Julien NICOLAS
<[hidden email]> wrote:

> Hello,
>
> If I don't make mistakes, with common theme (thanks to Nicolas for that), we
> don't need to 'define' a new technology. We don't need to choose bootstrap
> or vaadin.
>
> We only need one thing, we need somebody to make a new theme. If this theme
> is using vaading, we wil see the power behind it.
>
> My 2 cents,
>
> Julien.
>
>
>
> On 29/08/2017 03:36, Hans Bakker wrote:
>>
>> 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
>>
>

Jacques Le Roux

Re: Alternative UI: Vaadin proof of concept

Administrator

I totally agree with Julien and Taher, we need to think about the future...

Jacques

Le 07/09/2017 à 12:17, Taher Alkhateeb a écrit :

> I agree with Julien, and it is the reason we suggested in the first to
> place starting the themes refactoring exercise. We needed to move
> anything "web" related _outside_ the framework and then automate stuff
> through macros.
>
> If the work being done is isolated from the framework, then that would
> be great and a good potential for incorporation into the themes
> directory. If not, then maybe it needs to be refactored accordingly.
>
> I think it is essential to stress the importance of keeping "web"
> features outside the framework, which is clean separation between the
> DSL driving the widgets and the underlying implementation (web is
> _only one_ implementation).
>
> On Thu, Sep 7, 2017 at 1:04 PM, Julien NICOLAS
> <[hidden email]> wrote:
>> Hello,
>>
>> If I don't make mistakes, with common theme (thanks to Nicolas for that), we
>> don't need to 'define' a new technology. We don't need to choose bootstrap
>> or vaadin.
>>
>> We only need one thing, we need somebody to make a new theme. If this theme
>> is using vaading, we wil see the power behind it.
>>
>> My 2 cents,
>>
>> Julien.
>>
>>
>>
>> On 29/08/2017 03:36, Hans Bakker wrote:
>>> 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
>>>

Hans Bakker

Re: Alternative UI: Vaadin proof of concept

In reply to this post by Michael Brohl-3

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

Rishi Solanki

Re: Alternative UI: Vaadin proof of concept

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 <[hidden email]>
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
>

Jacques Le Roux

Re: Alternative UI: Vaadin proof of concept

Administrator

Thanks Rishi,

Yes, there should be no kind of vendor lock-in, even with an ASL2 licensed product with a vibrant community. If we would have to introduce important
modifications in OFBiz to work with Vaadin, I don't see myself participating to both.

Hans you rightly chose the user ML for this thread to ask questions, they are

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.

Those are my personal answers:

1. I already quickly gave you my architectural opinion. Getting to /#!TestView today is very slow, actually even not responding. So it's hard to give
a design opinion today.
2. I did not get into code details, but if it was as an alternative UI with no core modifications (ie a plugin or a theme) then why not. I'd be
against core modifications, by core I mean current ofbiz-framework code.
3. I'd not, we have already so much to do in other places. Of course if you eventually provide something like a plugin or theme then I'll be happy to
maintain it like I do for all the others. We can even discuss about minor parametrised core modifications which would allow for you to provide a
plugin or more likely a theme. I suggest you look at the (heavy) work Nicolas did with common-theme (thanks again Nicolas), maybe there is a way there
that you can accommodate with Vaadin.

Thanks for asking

Jacques

Le 08/09/2017 à 16:45, Rishi Solanki a écrit :

> 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 <[hidden email]>
> 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
>>

Richard Siddall

Re: Alternative UI: Vaadin proof of concept

In reply to this post by Rishi Solanki

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 <[hidden email]>
> 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
>>
>