Hi Taher, I like your proposal, adding bootstrap as common theme looks good idea,
Just as note: While transforming macros to bootstrap pattern we need to avoid use bootstrap classes like pullright, pullLeft, etc. instead we will write css rule based on element hierarchy. It will help designer to theme as per need. I am not familier with vue.js so I can;t say anything about vue.js, I'll explore it. +1 for POC, we can do POC on branch. Thanks & Regards -- Deepak Dixit www.hotwax.co On Sun, May 13, 2018 at 4:55 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > HI Taher, > > I agree about doing it directly in the trunk. Else we will get conflict > issues, because it will be a long task. > > +1 for a POC > > Jacques > > > > Le 12/05/2018 à 20:02, Taher Alkhateeb a écrit : > >> Hello Everyone, >> >> Recently, we at Pythys had some interactions with clients, and the >> user interface proved to be a sour point. It is functioning well, but >> looks too classic, too rigid, too 2000s really :) We had many >> discussion and attempts in the past like [1] [2] [3] [4] [5] [6] [7] >> [8] [9] [10] just to name a few all of which seemed not to follow >> through. >> >> So what is the problem? Why is this hard to get right? I'm not sure I >> have the magic answer, but it seems to me like part of the problem is >> simply .. TOO BIG >> >> So I was thinking about a possible solution, and after some initial >> research, I think maybe the solution (like everything else) needs to >> be slow, incremental and evolutionary rather than revolutionary. So I >> am suggesting the following ideas to try and move forward: >> >> - We include the assets for Bootstrap in the common theme. Bootstrap >> will give us the Grid system which allows for a responsive website >> that works on all devices, it will also give us beautiful widgets to >> work with. >> - We include Vue.js assets in the common theme. Vue.js is an excellent >> framework for creating Single Page Applications (SPAs) to give dynamic >> behavior to our pages and create ajax-heavy pages >> - We slowly migrate our old CSS to bootstrap constructs. We can begin >> for example by replacing our menus, then tables, then headers, then >> buttons etc .. >> - We slowly introduce dynamic screens using controller logic in Vue.js >> - We slowly update our macro library to migrate to the above mentioned >> libraries and widgets >> - We do all of this live in Trunk, without branching. This means that >> for some period of time, there will be transitional code (a little bit >> of bootstrap and a little bit of our current code) >> >> We can start with an initial proof of concept skeleton, and if that >> gets consensus, then we can move forward with a full implementation in >> trunk. I think this issue is many years over due. Our interface looks >> oooooooooooooold and really needs a face lift. >> >> What do you think? Ideas? Suggestions? >> >> [1] https://s.apache.org/rf94 >> [2] https://s.apache.org/g5zr >> [3] https://s.apache.org/XpBO >> [4] https://s.apache.org/YIL1 >> [5] https://s.apache.org/836D >> [6] https://s.apache.org/DhyB >> [7] https://s.apache.org/Lv9E >> [8] https://s.apache.org/zKIo >> [9] https://s.apache.org/D6jx >> [10] https://issues.apache.org/jira/browse/OFBIZ-5840 >> >> >
