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" <[hidden email]> > To: [hidden email] > 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 >>> <[hidden email]> >>> 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. >>>> > > |
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" <[hidden email]> >> To: [hidden email] >> 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 >>>> <[hidden email]> >>>> 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. >>>>> >> >> |
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" <[hidden email]> >>> To: [hidden email] >>> 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 >>>>> <[hidden email]> >>>>> 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. >>>>>> >>> >>> > |
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 < [hidden email]> 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" <[hidden email]> >>>> To: [hidden email] >>>> 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 >>>>>> <[hidden email]> >>>>>> 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. >>>>>>> >>>>>>> >>>> >>>> >> -- ----- Jonatan Soto |
Administrator
|
Thanks Joanatan,
BTW, @All: I think we can start from the wiki page Nicolas updated (see below) Unfortunately, like Jonatan, I will not be available much. I can help in the organisation though. Jacques 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 < > [hidden email]> 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" <[hidden email]> >>>>> To: [hidden email] >>>>> 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 >>>>>>> <[hidden email]> >>>>>>> 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. >>>>>>>> >>>>>>>> >>>>> > |
In reply to this post by JulienNicolas
Hi Julien,
Great move, count me in please. Cheers, Shi Jinghai 在 2014-10-13,下午3:56,Julien NICOLAS <[hidden email]> 写道: > 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" <[hidden email]> >> To: [hidden email] >> 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 >>>> <[hidden email]> >>>> 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. >>>>> >> >> > > |
In reply to this post by jonatan soto
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 < > [hidden email]> 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" <[hidden email]> >>>>> To: [hidden email] >>>>> 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 >>>>>>> <[hidden email]> >>>>>>> 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. >>>>>>>> >>>>>>>> >>>>> > |
Administrator
|
Hi Julien,
Le 21/10/2014 10:18, Julien NICOLAS a écrit : > 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... ^^ It's there https://svn.apache.org/viewvc/ofbiz/branches/frontendNewTheme2013-05-10/ > 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 ? Only the wiki https://cwiki.apache.org/confluence/display/OFBIZ/Home is open to contributors The idea is you can always add comments (possibly formatted, they use the same editor) and we can use them to complete the Confluence not open workspaces (members of the OFBiz team monitor changes in Confluence) Jacques > > 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 < >> [hidden email]> 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" <[hidden email]> >>>>>> To: [hidden email] >>>>>> 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 >>>>>>>> <[hidden email]> >>>>>>>> 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. >>>>>>>>> >>>>>>>>> >>>>>> >> > > > |
Hi Jacques,
Le 21/10/2014 11:29, Jacques Le Roux a écrit : > Hi Julien, > > Le 21/10/2014 10:18, Julien NICOLAS a écrit : >> 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... ^^ > > It's there > https://svn.apache.org/viewvc/ofbiz/branches/frontendNewTheme2013-05-10/ demo data and lauching, I still can't see any modifications in the front-end... I never use front-end so maybe I didn't use the good path... (http://localhost:8080/ecommerce/) > >> 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 ? > > Only the wiki https://cwiki.apache.org/confluence/display/OFBIZ/Home > is open to contributors > The idea is you can always add comments (possibly formatted, they use > the same editor) and we can use them to complete the Confluence not > open workspaces (members of the OFBiz team monitor changes in Confluence) > > Jacques > >> >> 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 < >>> [hidden email]> 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" <[hidden email]> >>>>>>> To: [hidden email] >>>>>>> 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 >>>>>>>>> <[hidden email]> >>>>>>>>> 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. >>>>>>>>>> >>>>>>>>>> >>>>>>> >>> >> >> >> |
Administrator
|
Le 21/10/2014 16:50, Julien NICOLAS a écrit : > Hi Jacques, > > Le 21/10/2014 11:29, Jacques Le Roux a écrit : >> Hi Julien, >> >> Le 21/10/2014 10:18, Julien NICOLAS a écrit : >>> Hi, >>> >>> 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... ^^ >> >> It's there https://svn.apache.org/viewvc/ofbiz/branches/frontendNewTheme2013-05-10/ > Yes, I've downloaded this branch as you told me but after building, load demo data and lauching, I still can't see any modifications in the > front-end... I never use front-end so maybe I didn't use the good path... (http://localhost:8080/ecommerce/) You are right Julien, I did not check. I created this branch in May 2013 (IIRW at Jonatan's - and others - request) but nothing happened since. SO it's simply trunk the 10th May 2013 :/ Can still be useful if we update it? The creation comment was <<Following the thread "Converting frontend themes to Twitter Bootstrap" here is a new branch for that. Actually the thread subject was misleading since we agreed that Twitter Bootstrap is not the only solution. The idea is though to introduce and use a HTML5/CSS framework, Bootstrap, H5Boilerplate and Zurb Foundation will be tried in the process... So I changed the thread subject to Converting frontend themes using HTML5/CSS framework/s.>> Maybe things have changed since? http://markmail.org/message/i7fnxid55cq5uiiz Jacques |
Le 21/10/2014 17:26, Jacques Le Roux a écrit :
> > Le 21/10/2014 16:50, Julien NICOLAS a écrit : >> Hi Jacques, >> >> Le 21/10/2014 11:29, Jacques Le Roux a écrit : >>> Hi Julien, >>> >>> Le 21/10/2014 10:18, Julien NICOLAS a écrit : >>>> Hi, >>>> >>>> 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... ^^ >>> >>> It's there >>> https://svn.apache.org/viewvc/ofbiz/branches/frontendNewTheme2013-05-10/ >>> >> Yes, I've downloaded this branch as you told me but after building, >> load demo data and lauching, I still can't see any modifications in >> the front-end... I never use front-end so maybe I didn't use the good >> path... (http://localhost:8080/ecommerce/) > > You are right Julien, I did not check. I created this branch in May > 2013 (IIRW at Jonatan's - and others - request) but nothing happened > since. SO it's simply trunk the 10th May 2013 :/ > Can still be useful if we update it? > > The creation comment was > <<Following the thread "Converting frontend themes to Twitter > Bootstrap" here is a new branch for that. > Actually the thread subject was misleading since we agreed that > Twitter Bootstrap is not the only solution. > The idea is though to introduce and use a HTML5/CSS framework, > Bootstrap, H5Boilerplate and Zurb Foundation will be tried in the > process... > So I changed the thread subject to Converting frontend themes using > HTML5/CSS framework/s.>> it's to create tools in the OFBiz framework that allow to use any HTML5/CSS frameworks. I've encountered problems to integrate bootstrap (the first one was the submenu structure) but I'm quite sure that it's the same with other HTML5/CSS frameworks. We have to think on how we can customize div container and class to use several HTML5/CSS frameworks without modifying OFBiz framework. I don't know how to use a specific branch to work with a team (I work daily with the addon manager) but if you can explain how to have commit right... or explain me how to share source code with a specific branch. Thanks, Julien. > > Maybe things have changed since? > http://markmail.org/message/i7fnxid55cq5uiiz > > Jacques |
In reply to this post by JulienNicolas
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 <[hidden email]> 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 < >> [hidden email]> 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" <[hidden email]> >>>>>> To: [hidden email] >>>>>> 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 >>>>>>>> <[hidden email]> >>>>>>>> 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. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>> >> > |
Looks like a very professional approach.
Ron On 21/10/2014 12:26 PM, Taher Alkhateeb wrote: > 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 <[hidden email]> > 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 < >>> [hidden email]> 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" <[hidden email]> >>>>>>> To: [hidden email] >>>>>>> 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 >>>>>>>>> <[hidden email]> >>>>>>>>> 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. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
In reply to this post by taher
Hi Taher,
Le 21/10/2014 18:26, Taher Alkhateeb a écrit : > Hi Julien, > > I think it might be a bit challenging and early to start creating teams > specialized in certain functions this early on. Maybe team is not the word, we could tell "work group". Work group will probably contain same people. > 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. Yes, it was a suggestion. And as you mention, tasks are dependent on each other. That's why I wanted to go further. > > 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 For this point I suggest to work on this way : Create tool to delegate HTML widget structure (and other structure) into theme framework. To be clear, I suggest to not integrate bootstrap only but modify the framework to allow any other HTML/CSS frameworks integration without modifying the OFBiz framework. But we'll do it for bootstrap first. > - 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? If everybody is ok, we can start the first step \o/ Thanks Taher, Julien. > > Taher Alkhateeb > > On Tue, Oct 21, 2014 at 11:18 AM, Julien NICOLAS <[hidden email]> > 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 < >>> [hidden email]> 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" <[hidden email]> >>>>>>> To: [hidden email] >>>>>>> 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 >>>>>>>>> <[hidden email]> >>>>>>>>> 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. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> |
Hi all,
One thing which seems to me important: It would be great to add a milestone of screens customisation. Even if screens are thought well, for very numerous customer projects, it is often necessary to modify screens to adapt them. The idea is to make customizable screens without having to modify the source code. I see at least 3 levels of configuration: - the menu: mask / show items - the general structure of page : Be able to add or mask a "portlet" or " widget " - the structure of a form : be able to mask / to show fields. All this should be done by a configuration in basis. There is a technique of portlets already existing into OFBiz, I find that it may be a good starting point. Do you think it could be added as a milestone? Pierre On 23/10/2014 08:12, Julien NICOLAS wrote: > Hi Taher, > > Le 21/10/2014 18:26, Taher Alkhateeb a écrit : >> Hi Julien, >> >> I think it might be a bit challenging and early to start creating teams >> specialized in certain functions this early on. > Maybe team is not the word, we could tell "work group". Work group > will probably contain same people. >> 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. > Yes, it was a suggestion. And as you mention, tasks are dependent on > each other. That's why I wanted to go further. >> >> 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. > Right ! >> >> 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 > For this point I suggest to work on this way : Create tool to delegate > HTML widget structure (and other structure) into theme framework. > To be clear, I suggest to not integrate bootstrap only but modify the > framework to allow any other HTML/CSS frameworks integration without > modifying the OFBiz framework. > But we'll do it for bootstrap first. >> - 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? > If everybody is ok, we can start the first step \o/ > > Thanks Taher, > > Julien. >> >> Taher Alkhateeb >> >> On Tue, Oct 21, 2014 at 11:18 AM, Julien NICOLAS >> <[hidden email]> >> 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 < >>>> [hidden email]> 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" <[hidden email]> >>>>>>>> To: [hidden email] >>>>>>>> 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 >>>>>>>>>> <[hidden email]> >>>>>>>>>> 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. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> > > -- Pierre Gaudin Consultant Fonctionnel Apache-OFBiz, ERP en logiciel Libre Société Néréide 3b Les isles 37270 Veretz http://www.nereide.fr Tel : 09 74 53 36 12 Mob : 06 08 40 25 70 Membre d'OFBiz-France http://www.ofbiz-fr.org |
In reply to this post by JulienNicolas
On 10/23/2014 7:12 AM, Julien NICOLAS wrote:
> Hi Taher, > > Le 21/10/2014 18:26, Taher Alkhateeb a écrit : >> Hi Julien, >> >> I think it might be a bit challenging and early to start creating teams >> specialized in certain functions this early on. > Maybe team is not the word, we could tell "work group". Work group will > probably contain same people. >> 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. > Yes, it was a suggestion. And as you mention, tasks are dependent on > each other. That's why I wanted to go further. >> >> 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. > Right ! >> >> 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 > For this point I suggest to work on this way : Create tool to delegate > HTML widget structure (and other structure) into theme framework. > To be clear, I suggest to not integrate bootstrap only but modify the > framework to allow any other HTML/CSS frameworks integration without > modifying the OFBiz framework. > But we'll do it for bootstrap first. You don't need to modify the framework. The screen widgets allow you to substitute alternate macros for the rendering engine. See widget.properties. Adrian Crum Sandglass Software www.sandglass-software.com |
In reply to this post by pierre-29
Hi Pierre, All,
Using an umbrella task in JIRA with for each app/component a sub task and for each set of elements (menus, screens, forms, etc) a sub of sub task, you'll have the structure that will also deliver the milestones. As an alternative, you could use OFBiz ProjectMgr to manage this (components as phases, component elements as tasks, but then you'll need to have access to an OFBiz implementation that is available over a longer period of time (demo doesn't cut it as it is cleaned every night). A structure could look like: Bootstrapping HTML5 CSS ETC (the umbrella Task) - Theme aspects (sub task) - CSS (sub of sub task) - etc - App 1 - menus - screens - forms - etc - App 2 - . - . - App N - Development documentation This way the completion of each sub of sub and sub task is a mile stone. And as soon as all tasks are completed it can be considered implementation ready. I believe that we shouldn't consider revamping all themes currently available in this.. If people want to have a specific theme revamped, they can create the appropriate JIRA issues and work on that after this major endeavour is completed. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Thu, Oct 23, 2014 at 8:46 AM, pierre <[hidden email]> wrote: > Hi all, > > One thing which seems to me important: > It would be great to add a milestone of screens customisation. Even if > screens are thought well, for very numerous customer projects, it is often > necessary to modify screens to adapt them. > > The idea is to make customizable screens without having to modify the > source code. > > I see at least 3 levels of configuration: > - the menu: mask / show items > - the general structure of page : Be able to add or mask a > "portlet" or " widget " > - the structure of a form : be able to mask / to show fields. > > All this should be done by a configuration in basis. > > There is a technique of portlets already existing into OFBiz, I find that > it may be a good starting point. > > Do you think it could be added as a milestone? > > Pierre > > > On 23/10/2014 08:12, Julien NICOLAS wrote: > >> Hi Taher, >> >> Le 21/10/2014 18:26, Taher Alkhateeb a écrit : >> >>> Hi Julien, >>> >>> I think it might be a bit challenging and early to start creating teams >>> specialized in certain functions this early on. >>> >> Maybe team is not the word, we could tell "work group". Work group will >> probably contain same people. >> >>> 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. >>> >> Yes, it was a suggestion. And as you mention, tasks are dependent on each >> other. That's why I wanted to go further. >> >>> >>> 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. >>> >> Right ! >> >>> >>> 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 >>> >> For this point I suggest to work on this way : Create tool to delegate >> HTML widget structure (and other structure) into theme framework. >> To be clear, I suggest to not integrate bootstrap only but modify the >> framework to allow any other HTML/CSS frameworks integration without >> modifying the OFBiz framework. >> But we'll do it for bootstrap first. >> >>> - 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? >>> >> If everybody is ok, we can start the first step \o/ >> >> Thanks Taher, >> >> Julien. >> >>> >>> Taher Alkhateeb >>> >>> On Tue, Oct 21, 2014 at 11:18 AM, Julien NICOLAS < >>> [hidden email]> >>> 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 < >>>>> [hidden email]> 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" <[hidden email]> >>>>>>>>> To: [hidden email] >>>>>>>>> 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 >>>>>>>>>>> <[hidden email]> >>>>>>>>>>> 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. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >> >> > > -- > Pierre Gaudin > Consultant Fonctionnel Apache-OFBiz, ERP en logiciel Libre > > Société Néréide > 3b Les isles > 37270 Veretz > http://www.nereide.fr > Tel : 09 74 53 36 12 > Mob : 06 08 40 25 70 > > Membre d'OFBiz-France > http://www.ofbiz-fr.org > > > |
Administrator
|
Le 23/10/2014 09:57, Pierre Smits a écrit : > Hi Pierre, All, > > Using an umbrella task in JIRA with for each app/component a sub task and > for each set of elements (menus, screens, forms, etc) a sub of sub task, You can't have sub-sub-tasks in Jira, only sub-tasks Jacques > you'll have the structure that will also deliver the milestones. > > As an alternative, you could use OFBiz ProjectMgr to manage this > (components as phases, component elements as tasks, but then you'll need to > have access to an OFBiz implementation that is available over a longer > period of time (demo doesn't cut it as it is cleaned every night). > > A structure could look like: > > Bootstrapping HTML5 CSS ETC (the umbrella Task) > > - Theme aspects (sub task) > - CSS (sub of sub task) > - etc > - App 1 > - menus > - screens > - forms > - etc > - App 2 > - . > - . > - App N > - Development documentation > > > This way the completion of each sub of sub and sub task is a mile stone. > And as soon as all tasks are completed it can be considered implementation > ready. > > I believe that we shouldn't consider revamping all themes currently > available in this.. If people want to have a specific theme revamped, they > can create the appropriate JIRA issues and work on that after this major > endeavour is completed. > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Thu, Oct 23, 2014 at 8:46 AM, pierre <[hidden email]> wrote: > >> Hi all, >> >> One thing which seems to me important: >> It would be great to add a milestone of screens customisation. Even if >> screens are thought well, for very numerous customer projects, it is often >> necessary to modify screens to adapt them. >> >> The idea is to make customizable screens without having to modify the >> source code. >> >> I see at least 3 levels of configuration: >> - the menu: mask / show items >> - the general structure of page : Be able to add or mask a >> "portlet" or " widget" >> - the structure of a form : be able to mask / to show fields. >> >> All this should be done by a configuration in basis. >> >> There is a technique of portlets already existing into OFBiz, I find that >> it may be a good starting point. >> >> Do you think it could be added as a milestone? >> >> Pierre >> >> >> On 23/10/2014 08:12, Julien NICOLAS wrote: >> >>> Hi Taher, >>> >>> Le 21/10/2014 18:26, Taher Alkhateeb a écrit : >>> >>>> Hi Julien, >>>> >>>> I think it might be a bit challenging and early to start creating teams >>>> specialized in certain functions this early on. >>>> >>> Maybe team is not the word, we could tell "work group". Work group will >>> probably contain same people. >>> >>>> 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. >>>> >>> Yes, it was a suggestion. And as you mention, tasks are dependent on each >>> other. That's why I wanted to go further. >>> >>>> 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. >>>> >>> Right ! >>> >>>> 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 >>>> >>> For this point I suggest to work on this way : Create tool to delegate >>> HTML widget structure (and other structure) into theme framework. >>> To be clear, I suggest to not integrate bootstrap only but modify the >>> framework to allow any other HTML/CSS frameworks integration without >>> modifying the OFBiz framework. >>> But we'll do it for bootstrap first. >>> >>>> - 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? >>>> >>> If everybody is ok, we can start the first step \o/ >>> >>> Thanks Taher, >>> >>> Julien. >>> >>>> Taher Alkhateeb >>>> >>>> On Tue, Oct 21, 2014 at 11:18 AM, Julien NICOLAS < >>>> [hidden email]> >>>> 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 < >>>>>> [hidden email]> 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" <[hidden email]> >>>>>>>>>> To: [hidden email] >>>>>>>>>> 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 >>>>>>>>>>>> <[hidden email]> >>>>>>>>>>>> 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. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>> >> -- >> Pierre Gaudin >> Consultant Fonctionnel Apache-OFBiz, ERP en logiciel Libre >> >> Société Néréide >> 3b Les isles >> 37270 Veretz >> http://www.nereide.fr >> Tel : 09 74 53 36 12 >> Mob : 06 08 40 25 70 >> >> Membre d'OFBiz-France >> http://www.ofbiz-fr.org >> >> >> |
Tja....
We have to make due with what we have got. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Thu, Oct 23, 2014 at 10:48 AM, Jacques Le Roux < [hidden email]> wrote: > > Le 23/10/2014 09:57, Pierre Smits a écrit : > >> Hi Pierre, All, >> >> Using an umbrella task in JIRA with for each app/component a sub task and >> for each set of elements (menus, screens, forms, etc) a sub of sub task, >> > > You can't have sub-sub-tasks in Jira, only sub-tasks > > Jacques > |
Administrator
|
Le 23/10/2014 10:52, Pierre Smits a écrit :
> Tja.... > > We have to make due with what we have got. https://jira.atlassian.com/browse/JRA-4446 I don't think the infra would be willing to install a workaround plugin Jacques > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Thu, Oct 23, 2014 at 10:48 AM, Jacques Le Roux < > [hidden email]> wrote: > >> Le 23/10/2014 09:57, Pierre Smits a écrit : >> >>> Hi Pierre, All, >>> >>> Using an umbrella task in JIRA with for each app/component a sub task and >>> for each set of elements (menus, screens, forms, etc) a sub of sub task, >>> >> You can't have sub-sub-tasks in Jira, only sub-tasks >> >> Jacques >> |
Free forum by Nabble | Edit this page |