Hi Divesh,
As a first step, because we have a lot of work before starting UX part,
I want to use POC to show how the screen structure (for find, entity
details sheet, etc.) is important.
Nicolas start to create the common-theme and I start to make it blank.
The theme without theme (with
Thanks Taher,
Your explanations are sharper than mine, I was on the consistency
benefit, you explain about technical benefits.
Anyway, I'll provide also the explanation drawing and screenshot of the
UI consistency benefits. That is as important as the technical part :)
Have a nice day,
Very good initiative. I see lots of discussions of technology part. So I
will not add on that part. I would like to give some inputs on our approach
to make UI/UX of OFBiz better.
As Jacopo also suggested to take small step at a time, I would say we start
with one use story at a time and then
Hi Sharan,
Thanks for starting this thread. I really liked the idea of doing OFBiz
meet ups or events. Events can be specific to any topic. Few ways we can
organise these events are:
1) Invite people from business community and help them to understand how
they can use Apache OFBiz for free to
Hi all,
This is really a good thread and I see lots of good discussions. I liked
inputs given by Taher to increase the adaptability of OFBiz. Recently I
met few end users who are looking for Open Source ERP options, however they
are not choosing Apache OFBiz. When I asked Why ? I got few
I'm sure Julien has good ideas on how to move things about and I'll let gim
express those, I just want to add a conceptual frame for why probably both
Julien and myself sort of agree on the seperation of FTL templates from
screen widgets, so here goes ...
Aside from the great data model and
Hi Michael,
I'll provide drawings and some examples to be clearer.
Anyway, we start a proof of concept to show pros and cons of our tough.
It'll mustn't affect the good old fashion themes. The explanation about
the guidelines will also not affect the old version, it's to be sure
that our
Hi Julien,
thanks for your explanations.
It is indeed difficult to explain and understand, I suggest to provide
some kind of diagram or maybe some very simple examples, if you can.
Please also have in mind that we need to have a migration plan from old
to new and we should be able to run
It's a proposal for best practices, because of my own experience on
making new theme and the impact for a consistency UI.
For example, party details screen is a patchwork of xml screens and ftl
screens. If you manage to change the HTML structure of a form, it'll
affect only xml screen thanks
I am wondering how to understand this:
better to not use ftl elsewhere than in macro
Is not every ftl template providing macro functionalities? Do you desire
that this project moves away from using ftl templates in any other place
than in a theme?
Best regards,
Pierre Smits
ORRTIZ.COM
If I understand well, yes.
All html structure must be managed by the theme. In OOTB, it could be
really better to not use ftl elsewhere than in macro. This is a way that
could be good to follow to have consistency for all screens in OFBiz.
Julien.
On 06/12/2016 11:59, Pierre Smits wrote:
Love you Jacques.
I removed the duplicated labels and committed (rev. 1773058).
Shi Jinghai
-邮件原件-
发件人: Jacques Le Roux [mailto:jacques.le.r...@les7arts.com]
发送时间: 2016年12月7日 17:16
收件人: dev@ofbiz.apache.org
主题: Re: svn commit: r1770621 [1/5] - in /ofbiz/trunk/specialpurpose/pricat: ./
Thanks Jinghai,
I just noticed these labels are duplicated
ExcelTableNoRow
ExcelTableNoRow
ExcelTableColumnNumberNotMatch
ExcelTableColumnNumberNotMatch
ExcelTableColumnNotMatch
ExcelTableColumnNotMatch
ExcelParsingRow
ExcelParsingRow
Jacques
Le 05/12/2016 à 16:34, Shi Jinghai a écrit :
13 matches
Mail list logo