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