This proposal is a package, this work is link to another big (huge) task
to rebuild the entire UI \o/
It always start with a first step, this is it ;)
On 01/12/2016 09:36, Jacques Le Roux wrote:
At least by review in new committed code. It would not be impossible
technically but very difficult to enforce else, I mean in not OOTB
code (just a thought)
Also we have still to discuss if we will apply to all existing code or
if it will be only applied alongside in the "other" way (which still
need to be clarified/defined)
I think the best is to review the POC Nicolas provided in his GitHub
account. I did not get a chance yet, so I was mostly asking to better
understand the proposition
Le 30/11/2016 à 21:16, Pierre Smits a écrit :
So when you speak of
a super-structure that will be used in place of currently conventions
are not always respected
how do you envision that with that new 'super-structure' conventions
OFBiz based solutions & services
OFBiz Extensions Marketplace
On Wed, Nov 30, 2016 at 9:00 PM, Jacques Le Roux <
Le 30/11/2016 à 10:02, Julien NICOLAS a écrit :
On 30/11/2016 08:51, Jacques Le Roux wrote:
This structure is to follow the a UI standard that can be managed
- Each screen must be linked to a screen structure.
What would be this screen structure? You don't need to develop
this stage, just that I can't vision what it would be.
theme. For example, the find screen can be define as :
- A research field area
- A result area
Ah, I see, we have already this concept in screen widget.
You mean that it would be a super-structure that will be used in
If all the find screen could be linked to this structure, it will be
easier for theme to manage it's own template of search screen.
currently conventions which are not always respected, I see.
It will be included in the main decorator that will also linked to a
structure, so theme can manage to change the template. And when you
the theme, it could be a completely different look and feel :)
I hope I explain well my thought.
Got it, thanks :)
No, I mean to define a component (party, product, facility, etc.)
start to re-implement (using the existing services) but in a more
You mean we could take and existing component, say example for
and would simply it at the UI level. I picked example because it's
Why we need a new component to test new theme ?
When I start working with OFBiz, I was so surprised that the UI
heavy. Then I was thinking that I have to improve the UI to
provide a best
one. After several try I understand that the actual UI is not a
interface. It is a developer one. It's a developer UI because it
all the features developed. But definitively, we can't provide
this kind of
UI to final users, we have to simplify it. In the same times, we
delete the current UI because developers need to improve it with new
features that will help us to deploy new features to our final
For this new component, we can implement an existing component but
simplified and ready for the new theme(s).
rather simple and contains demonstration of features.
way (without all the features, selecting only the main ones).
Yes, too many thing to explain, I have to add details about this
Another thing I can't vision at this stage, no hurry, I guess I'll
In conclusion, if the new component dedicated for test a new theme
match to the community needs, Taher think to a super simplified
user interface that facilitate developers to improve the
software. A new
interface without any constraint that allow developers to develop
I'll do it soon ^^
I did not get a chance to look yet at the POC Nicolas, Gil and you are
working on. I guess I'd get the ideas from there then?