I agree with the "gem" ranking level at which widgets are placed and find it a worthy effort to convert as much FTL to widgets as possible because widgets extremely faster to interpret than FTL files. However, sometimes the framework has to be extended to support all of the FTL features which adds some inconveniency (less polished). Moqui supports widgets similar to OFBiz also which suggests its value.
On Thu, 2015-05-14 at 12:20 +0200, Jacques Le Roux wrote: > Below are some, but this question is more to shake things a bit and know what > people think > > I think everybody will agree that the Entity Engine is the gem of this > project, follows the Service Engine. I believe, though less polished, the > widgets are 3rnd, but that's only my opinion and I'd really like to know > others > > Jacques > > > Le 14/05/2015 10:45, Pierre Smits a écrit : > > But what are the proposals? Where can these be found? > > > > Best regards, > > > > Pierre Smits > > > > *ORRTIZ.COM <http://www.orrtiz.com>* > > Services & Solutions for Cloud- > > Based Manufacturing, Professional > > Services and Retail & Trade > > http://www.orrtiz.com > > > > On Thu, May 14, 2015 at 9:14 AM, Jacques Le Roux < > > jacques.le.r...@les7arts.com> wrote: > > > >> Actually maybe I'm misunderstanding you and I also want to clarify with > >> everybody. I will try to be brief and right to the point! > >> > >> Do you (we) want to replace the widgets by something like Ean and Anil > >> proposed many times, or do we want to improve them using these new tools? > >> > >> Jacques > >> > >> Le 13/05/2015 22:15, Julien NICOLAS a écrit : > >> > >>> Le 13/05/2015 16:35, Jacques Le Roux a écrit : > >>> > >>>> Le 13/05/2015 15:04, Julien NICOLAS a écrit : > >>>> > >>>>> Hello Pierre, > >>>>> > >>>>> Le 13/05/2015 12:35, Pierre Smits a écrit : > >>>>> > >>>>>> For what it is worth, the BOOTSTRAP_theme dev branch is a other way to > >>>>>> enhance the user experience. Unfortunately the work is not done yet. > >>>>>> > >>>>> The problem is that the GUI is a demo GUI. Then all the time you spend > >>>>> to solve all GUI problems, will potentially lost because nobody use it > >>>>> (and > >>>>> when I say that I think in particular to the order screen that is a > >>>>> nightmare...). > >>>>> It's better that OFBiz embedded GUI web framework (like bootstrap but > >>>>> not only, it can be bootstrap based tool for dashboard, etc.) and a > >>>>> documentation on how to use it. > >>>>> > >>>> I don't know if nobody is using it (I guess some are ;)), but I believe > >>>> a lot are reusing parts of it. The idea is not only to provide a demo but > >>>> also to provide ideas, bricks to be reused. Did you wrote your own > >>>> totally > >>>> from scratch :-o (I guess not even considering ideas) ? > >>>> > >>>> Is the BOOTSTRAP_theme dev branch not a way to embed one "HTML, CSS, and > >>>> JavaScript framework" and use its artefacts inside widgets? > >>>> What are actually the parts you found so bad? > >>>> > >>> I mean if you need to adapt the actual visual theme to bootstrap, it may > >>> take a lot of time but the gain is very low. > >>> It will be more interesting to add tool (like bootstrap or some js tool > >>> or widget) and use it for the future demo screen. To have a good screen > >>> render by using a new HTML/CSS/JS framework (like bootstrap), you must to > >>> define your global solution rendering and create GUI specifications that > >>> contain all visual cases. > >>> If we speak about create a bootstrap theme not for demo but for a good > >>> user experience, we'll have to create the GUI specifications first. Then > >>> we > >>> need a GUI developer group that define the guidance and validate new > >>> screen. In my opinion, changing colour of the actual demo GUI is a waste > >>> of > >>> time. But use new feature for new demo screen, that change the demo > >>> version > >>> into a patchwork but it's not a problem :) > >>> > >>> How the widgets are generated, the CSS class used, how js is used inside > >>>> of that, etc. ? > >>>> > >>>> If we go this way (embed a HTML framework in OFBiz) I remember some > >>>> proposed to use rather foundation, we would need to pick one and only > >>>> one. > >>>> Like wed did with jQuery as the main js lib that BTW we need to keep! > >>>> > >>> I agree. We have to make the choice of a framework and use it. But we can > >>> keep in mind that maybe somebody want use another one so we can have > >>> detail > >>> documentation to explain how to change it. > >>> Another point, prefer to use heritage for the default css class. > >>> And with the next add-on management, it may be possible to have a > >>> specific add-on by css framework ;) > >>> > >>>> Also some have proposed to get further and use something like Angular > >>>> https://issues.apache.org/jira/browse/OFBIZ-5040?focusedCommentId=13887287 > >>>> or Backbone > >>>> https://issues.apache.org/jira/browse/OFBIZ-5522?focusedCommentId=13885989 > >>>> you name it... > >>>> > >>>> https://cordova.apache.org/ ("aka" PhoneGap) is also worth considering > >>>> see > >>>> https://cwiki.apache.org/confluence/download/attachments/48792051/mobile_web.pdf?version=1&modificationDate=1429534402000&api=v2 > >>>> > >>> PhoneGap is a very interesting project but I'm not sure that a phone app > >>> is a priority but it's only my opinion :D > >>> > >>>> We need to make delicate choices and quickly, time is flying... > >>>> > >>> So true... > >>> > >>> Julien. > >>> > >>>> Jacques > >>>> > >>> > >>> > >>>
