Hello Michael,
Michael Brohl writes:
> I am still not sure why we need the new mechanism.
>
> And if we decide to use both, we should make sure that the old version
> is the default at least for the lifecycle of one release with proper
> an clear dopcumentation for users.
>
> Thanks,
>
>
Hello, inline,
On 13/12/2019 12:47, Olivier Heintz wrote:
Hello Community,
[...]
1. homogeneous in each component and between components
This is the way started with the common-theme creation. Move all
structural and technical concept on the theming, promoting decorator
usage for screen
Chapter One: How to manage the updating area
Hello,
After different discussions already listed by Taher [1-9], Leila,
Nicolas and me tried another approach.
Instead of analyzing how to implement different functionalities offered
by modern js framework, we did analyzed how end user use, in
I am still not sure why we need the new mechanism.
And if we decide to use both, we should make sure that the old version
is the default at least for the lifecycle of one release with proper an
clear dopcumentation for users.
Thanks,
Michael
PS: I'm asking myself why some people have such
Hi All,
Have we a lazy consensus here?
Jacques
Le 10/12/2019 à 06:17, Jacques Le Roux a écrit :
Hi Michael, Mathieu,
Why not keeping both features and have a simple way (if it does not exist yet)
to choose the one to use?
BTW Michael, you are certainly aware, you have a mail certificate
Hello Community,
After Nicolas remarks (thanks to the team for sharing their experiences and
thoughts)
I propose to discuss about GUI best practice in OFBiz, which one are the most
priority for the future.
I have already described my point of view and approach 3 years ago in a mail
[1] and I
Hi Tomek,
Sorry a bit late, please subscribe to the user ML for such questions and then
use your email client
See why here http://ofbiz.apache.org/mailing-lists.html
You will get a better support , the wider the audience the better the answers
you might get
This said, you should better
