Hi Julien, I think it might be a bit challenging and early to start creating teams specialized in certain functions this early on. We did not yet define what we're going to do nor do we have a real feel for the size of this job and the best way to split efforts, not to mention that some of the tasks are probably dependent on each other.
If I may suggest instead, we need to perhaps go through the tasks themselves and see what needs to be accomplished. To that end, I would focus on the deliverables themselves in the beginning such as: - Identify the major milestones or objectives - Discuss and decide upon the best methodology for implementation of the above objectives - Decide on a collaboration platform (in addition to what exists) if any. - Dive into code directly and just hand off tasks to volunteers who find them interesting / appealing from the team Once we get the project into momentum and you have enough interested and dedicated people then you can put some structure and specialization into it. Now to that end, I would suggest the following major milestones as necessary - Integration of bootstrap and its dependencies to the framework, specifically into the widget system - The utilization of bootstrap into the themes (each theme as a milestone) - Documentation including XSD file definitions, wiki, DocBook stuff etc ... - Standardization of the UI everywhere (perhaps each component as a milestone) What do you think? Taher Alkhateeb On Tue, Oct 21, 2014 at 11:18 AM, Julien NICOLAS <julien.nico...@nomaka.fr> wrote: > Hi, > > My apologize for answering late, I was deep under the annual balance sheet > for my company... > Thanks Jonatan for informations. > > I try to find specific theme for the front end in the branch that you told > me but I can't find were it can be enable... I didnt' search a lot so maybe > it was just closed to my nose and I didn't seen it... ^^ > Anyway I think a lot about the work we have to do and I think it could be > interesting to go deeper in the GUI modifications. > Including bootstrap framework in OFBiz will be a step but maybe we can go > ahead and modify best practices of screen creation. Define a design pattern > that developers can follow to create standardized screens. > > So we can define teams to work simultaneously : > - Team 1 - Framework modifications > - Team 2 - List actual standard screens, list actual tools and send > survey to know tools that people need in the GUI (like breadcrumb, better > treeview, calendar, etc.) > - Team 3 - Create the new GUI design. Define new standardization for > screen listed by Team 2. > A fourth team could be work on new tools integration, tests and > validations. > > Maybe it's too ambitious and we have to go step by step but I think if we > have enough good soul to work on, we can do it ! > > Let me know your feeling about this. > > Julien. > > PS : I can't modify the wiki that contain bootstrap integration > definition. Is it possible to have modifications right ? Maybe it's better > to create specific wiki page ? > > Le 14/10/2014 22:52, Jonatan Soto a écrit : > >> Hi all, >> >> I made a similar proposition a year ago (see >> http://markmail.org/message/jc7nfodhtoordqli) but unfortunately I >> couldn't >> find the time to work on that. I'm not sure if I'll be able to join on >> this >> but I'll try. >> >> On the other hand, I seem to remember that there was a branch already >> created for this ( >> https://fisheye6.atlassian.com/browse/ofbiz/branches/ >> frontendNewTheme2013-05-10) >> and a Jira ticket (https://issues.apache.org/jira/browse/OFBIZ-5040). >> >> Cheers, >> >> >> >> >> >> >> On Tue, Oct 14, 2014 at 8:32 AM, Adrian Crum < >> adrian.c...@sandglass-software.com> wrote: >> >> You can create a branch for this effort. >>> >>> Adrian Crum >>> Sandglass Software >>> www.sandglass-software.com >>> >>> On 10/14/2014 1:44 AM, Nicolas Malin wrote: >>> >>> Hi, >>>> >>>> The best way will be open a issue and manage by sub task each step. >>>> >>>> After that dev mailing list is good to sharing. Webconf and jabber are >>>> interesting for dynamic and quick exchange but keep in mind to report >>>> the talking result on the mailing or issue. >>>> It's important for the follow-up :) >>>> >>>> Nicolas >>>> >>>> Le 2014-10-13 09:56, Julien NICOLAS a écrit : >>>> >>>> Hi Taher, >>>>> >>>>> I think that we can use the OFBiz wiki to write the action plan and >>>>> tasks to do, etc. >>>>> I was thinking about regular webconf and we can be connected via >>>>> jabber. >>>>> >>>>> But maybe ofbiz dev use other collaborative tools ? >>>>> >>>>> Any suggestions ? >>>>> >>>>> Regards, >>>>> >>>>> Julien. >>>>> >>>>> >>>>> Le 13/10/2014 09:48, Taher Alkhateeb a écrit : >>>>> >>>>> Hi Nicolas, >>>>>> >>>>>> Great! I'm rubbing hands in excitement. What is the next action now? >>>>>> open a JIRA, have a discussion on mailing list? Furthermore, such a >>>>>> project requires a lot of collaboration. Do we have a platform or a >>>>>> solution for easier collaboration on this project? >>>>>> >>>>>> Regards, >>>>>> >>>>>> Taher Alkhateeb >>>>>> >>>>>> ----- Original Message ----- >>>>>> >>>>>> From: "Nicolas Malin" <malin.nico...@librenberry.net> >>>>>> To: u...@ofbiz.apache.org >>>>>> Sent: Monday, 13 October, 2014 4:47:05 AM >>>>>> Subject: Re: Theme bootstrap >>>>>> >>>>>> Hi all, >>>>>> I updated the page >>>>>> >>>>>> https://cwiki.apache.org/confluence/display/OFBADMIN/ >>>>>> New+Features+Roadmap+-+Living+Document, >>>>>> >>>>>> >>>>>> Now the best way will be move the discussion on dev and set your >>>>>> battle >>>>>> line on jira ;) >>>>>> >>>>>> Nicolas >>>>>> >>>>>> >>>>>> Le 2014-10-10 15:50, Julien NICOLAS a écrit : >>>>>> >>>>>> Hi Gavin, Pierre, Florient and Taher, >>>>>>> >>>>>>> It's a good news that you all join the team :) >>>>>>> >>>>>>> Other thanks to Adrian for informations ! >>>>>>> >>>>>>> Maybe the first step could be to create a setting which allow to >>>>>>> switch from old management to the new one because it seems to be hard >>>>>>> to change the framework without breaking old css themes. >>>>>>> >>>>>>> Another important point is to define a mock-up for the basic >>>>>>> navigation and apply it for easiest navigation. This will be helpful >>>>>>> to work with the other points. >>>>>>> >>>>>>> Taher, I think that it's a big task because we can find several types >>>>>>> of screens (widget, ftl, form, etc.) and many technologies very >>>>>>> helpful but maybe it's time to unify the main software UI. >>>>>>> Even if we keep all technologies that make the software flexibility, >>>>>>> it's important to be coherent in standard UI. >>>>>>> >>>>>>> So I suggest this following steps : >>>>>>> 1 - Create themes switch >>>>>>> 2 - Submit several mock-up for the basic navigation (ask community >>>>>>> feeling) >>>>>>> 3 - Implement basic navigation >>>>>>> 4 - Mock-up for standard to unify standard UI (ask community feeling) >>>>>>> 5 - Screen widgets >>>>>>> 6 - Form Widgets >>>>>>> 7 - Styling >>>>>>> >>>>>>> I think point 2 and 4 could be running during working on the others >>>>>>> but we have to start to submit mock-ups to the community because >>>>>>> discussions could take a lot of time ;) >>>>>>> >>>>>>> Julien. >>>>>>> >>>>>>> >>>>>>> Le 10/10/2014 11:49, Gavin Mabie a écrit : >>>>>>> >>>>>>> Hi Julien >>>>>>>> >>>>>>>> I'd like to join the team. I've done some work with bootstrap, >>>>>>>> albeit on >>>>>>>> ecommerce and front-end sites. For backend apps I believe that the >>>>>>>> task >>>>>>>> should be approached systematically and that this could also be an >>>>>>>> opportunity to bed down some ui design principles - which could >>>>>>>> captured in >>>>>>>> the wiki - as a page on its own. The wiki already contains >>>>>>>> information on >>>>>>>> widgets ( >>>>>>>> >>>>>>>> >>>>>>>> https://cwiki.apache.org/confluence/display/OFBIZ/ >>>>>>>> Understanding+the+OFBiz+Widget+Toolkit), >>>>>>>> >>>>>>>> but nowhere does it recommend best practices for ui design. A >>>>>>>> suggested >>>>>>>> approach: >>>>>>>> 1. Start with screen widgets - the widget-screen.xsd will need to be >>>>>>>> revisited to align this with the Bootstrap CSS (grid-system amongst >>>>>>>> others); >>>>>>>> 2. Form widgets - revisit widget-form.xsd; >>>>>>>> 3. Menus and navigation - widget-menu.xsd; >>>>>>>> 4. Styling - customisation and theming. >>>>>>>> >>>>>>>> What do you think? >>>>>>>> >>>>>>>> Gavin >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Oct 10, 2014 at 9:21 AM, Julien NICOLAS >>>>>>>> <julien.nico...@nomaka.fr> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>>> I'm working on a basic bootstrap theme for OFBiz. >>>>>>>>> My goal is that OFBiz project uses bootstrap standard classes to >>>>>>>>> work. >>>>>>>>> >>>>>>>>> I encountered some issues that I've fixed. The problem is that I >>>>>>>>> change >>>>>>>>> the framework and if I want to share my work with the community, it >>>>>>>>> could >>>>>>>>> be better to do it in the best way. >>>>>>>>> >>>>>>>>> I know that it's a task in the roadmap, so I hope somebody is >>>>>>>>> already >>>>>>>>> working on or waiting for team mate :) >>>>>>>>> >>>>>>>>> I'm actually focused on : >>>>>>>>> - Portlet-widget structure >>>>>>>>> - KeywordSearchform >>>>>>>>> - Multi-menu management >>>>>>>>> >>>>>>>>> Who can help me on this topic ? >>>>>>>>> >>>>>>>>> Thanks by advanced, >>>>>>>>> >>>>>>>>> Julien. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>> >> >
