Sounds good Julien. Order process was just an example. I agree with you to start with other common components.
Thanks -- Divesh Dutta On Thu, Dec 8, 2016 at 1:25 PM, Julien NICOLAS <julien.nico...@nereide.fr> wrote: > 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 minimal UI) ;) > > In that way, we will able to show how will work this structure screens. > I'll to provide example to explain better my tough (I'll work on it this > week-end). > > Because the order process contain a lot of specific process that will be > only used by the order process, I think that first components to be migrate > will probably simple components. It will be faster and easier than the > order process to show a new modern and UX user interface :) > > What do you think ? > > Julien. > > > > > On 08/12/2016 08:19, Divesh Dutta wrote: > >> 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 improve UI and UX of that story. For >> example: "CSR creates a sales order". We overhaul UI and UX of sales order >> creation work flow and Order over view page. Once this is done, it will be >> good POC for others to learn how to do UI overhaul. And then others can >> participate by picking up other user stories . We can also prioritise user >> stories and components. >> >> Besides this , before writing code, we can finalise UI and UX of one >> workflow by drawing some thing or preparing wireframes. Once we have >> wireframes finalised, we can start writing code. >> >> This will be lot of work to change UI and UX of whole OFBiz and starting >> one user story at at time is good idea according to me. Having >> technologies >> defined is important thing, however defining UX for particular workflow >> (on >> paper or via wireframes) is also important. >> >> Thanks >> -- >> Divesh Dutta. >> >> >
