Converting frontend themes to Twitter Bootstrap

[jonatan soto]

Hi,

Would be anyone interested in convert the existing frontend themes into
Bootstrap http://twitter.github.io/bootstrap/?

The idea is to create a theme from scratch that will replace the current
default and multiplex themes. In order to do that I would propose to create
a new branch and start over with the creation of the new theme modifying
the markup and screen definitions for the ecommerce and ecomclone
applications. Another option would be to leave intact the ecommerce and
apply the changes to the ecomclone only but looks like a bit messy to me. I
also think that the ecomclone doesn't include all the ftl so that will
require to copy the missing ones from the ecommerce app.

Paul opened a Jira ticket for that so I think we could use it for this:
https://issues.apache.org/jira/browse/OFBIZ-5040

Cheers,
--
-----

Jonatan Soto

[hans_bakker]

Another option you could consider is replacing backend and frontend
themes by a single theme.....

On 05/06/2013 05:31 PM, Jonatan Soto wrote:

> Hi,
>
> Would be anyone interested in convert the existing frontend themes into
> Bootstrap http://twitter.github.io/bootstrap/?
>
> The idea is to create a theme from scratch that will replace the current
> default and multiplex themes. In order to do that I would propose to create
> a new branch and start over with the creation of the new theme modifying
> the markup and screen definitions for the ecommerce and ecomclone
> applications. Another option would be to leave intact the ecommerce and
> apply the changes to the ecomclone only but looks like a bit messy to me. I
> also think that the ecomclone doesn't include all the ftl so that will
> require to copy the missing ones from the ecommerce app.
>
> Paul opened a Jira ticket for that so I think we could use it for this:
> https://issues.apache.org/jira/browse/OFBIZ-5040
>
> Cheers,

[jonatan soto]

Personally I like the idea of keeping the backend and frontend themes
separated. Also dealing with the backend markup and screens definitions
will be an enormous effort imo. I will prefer to start with something
doable for now.


On Mon, May 6, 2013 at 12:40 PM, Hans Bakker
<[hidden email]>wrote:

> Another option you could consider is replacing backend and frontend themes
> by a single theme.....
>
>
> On 05/06/2013 05:31 PM, Jonatan Soto wrote:
>
>> Hi,
>>
>> Would be anyone interested in convert the existing frontend themes into
>> Bootstrap http://twitter.github.io/**bootstrap/<http://twitter.github.io/bootstrap/>
>> ?
>>
>> The idea is to create a theme from scratch that will replace the current
>> default and multiplex themes. In order to do that I would propose to
>> create
>> a new branch and start over with the creation of the new theme modifying
>> the markup and screen definitions for the ecommerce and ecomclone
>> applications. Another option would be to leave intact the ecommerce and
>> apply the changes to the ecomclone only but looks like a bit messy to me.
>> I
>> also think that the ecomclone doesn't include all the ftl so that will
>> require to copy the missing ones from the ecommerce app.
>>
>> Paul opened a Jira ticket for that so I think we could use it for this:
>> https://issues.apache.org/**jira/browse/OFBIZ-5040<https://issues.apache.org/jira/browse/OFBIZ-5040>
>>
>> Cheers,
>>
>
>

--
-----

Jonatan Soto

[Jacques Le Roux]

Yes, but that would be much much more work ;)

Jacques

From: "Hans Bakker" <[hidden email]>

> Another option you could consider is replacing backend and frontend
> themes by a single theme.....
>
> On 05/06/2013 05:31 PM, Jonatan Soto wrote:
>> Hi,
>>
>> Would be anyone interested in convert the existing frontend themes into
>> Bootstrap http://twitter.github.io/bootstrap/?
>>
>> The idea is to create a theme from scratch that will replace the current
>> default and multiplex themes. In order to do that I would propose to create
>> a new branch and start over with the creation of the new theme modifying
>> the markup and screen definitions for the ecommerce and ecomclone
>> applications. Another option would be to leave intact the ecommerce and
>> apply the changes to the ecomclone only but looks like a bit messy to me. I
>> also think that the ecomclone doesn't include all the ftl so that will
>> require to copy the missing ones from the ecommerce app.
>>
>> Paul opened a Jira ticket for that so I think we could use it for this:
>> https://issues.apache.org/jira/browse/OFBIZ-5040
>>
>> Cheers,
>

[hans_bakker]

for GrowERP we are looking into the possibility to use the backend theme
for the frontend....

more and more we would like to make backend applications available to
frontend customers...
and re-implement them using e-commerce ftl screens is really a big task....

Regards,
Hans

On 05/06/2013 05:59 PM, Jacques Le Roux wrote:

> Yes, but that would be much much more work ;)
>
> Jacques
>
> From: "Hans Bakker" <[hidden email]>
>> Another option you could consider is replacing backend and frontend
>> themes by a single theme.....
>>
>> On 05/06/2013 05:31 PM, Jonatan Soto wrote:
>>> Hi,
>>>
>>> Would be anyone interested in convert the existing frontend themes into
>>> Bootstrap http://twitter.github.io/bootstrap/?
>>>
>>> The idea is to create a theme from scratch that will replace the current
>>> default and multiplex themes. In order to do that I would propose to create
>>> a new branch and start over with the creation of the new theme modifying
>>> the markup and screen definitions for the ecommerce and ecomclone
>>> applications. Another option would be to leave intact the ecommerce and
>>> apply the changes to the ecomclone only but looks like a bit messy to me. I
>>> also think that the ecomclone doesn't include all the ftl so that will
>>> require to copy the missing ones from the ecommerce app.
>>>
>>> Paul opened a Jira ticket for that so I think we could use it for this:
>>> https://issues.apache.org/jira/browse/OFBIZ-5040
>>>
>>> Cheers,

[Heidi Dehaes - Olagos]

Hello,
I am very interested-

Eric

Www.olagos.eu
Op 6 mei 2013 12:32 schreef "Jonatan Soto" <[hidden email]> het
volgende:

> Hi,
>
> Would be anyone interested in convert the existing frontend themes into
> Bootstrap http://twitter.github.io/bootstrap/?
>
> The idea is to create a theme from scratch that will replace the current
> default and multiplex themes. In order to do that I would propose to create
> a new branch and start over with the creation of the new theme modifying
> the markup and screen definitions for the ecommerce and ecomclone
> applications. Another option would be to leave intact the ecommerce and
> apply the changes to the ecomclone only but looks like a bit messy to me. I
> also think that the ecomclone doesn't include all the ftl so that will
> require to copy the missing ones from the ecommerce app.
>
> Paul opened a Jira ticket for that so I think we could use it for this:
> https://issues.apache.org/jira/browse/OFBIZ-5040
>
> Cheers,
> --
> -----
>
> Jonatan Soto
>

[Heidi Dehaes - Olagos]

Hello,

It is not useful to create the same layout and theme for frontend and backend.
The ecommerce frontend needs to be more and more adapted to the
"social ecommerce" functionalities.
This is not the case at all for the backend.

The top of ecommerce websites uses today "social ecommerce" with
Twitter, Facebook , Linkedin , Pinterest, etc. social engine
functionalities integrated in the ecommerce frontend. This is really
needed for marketing someones e-shop today.

I think integration into ofbiz of Bootstrap is a good base and
necessity to bring ofbiz ecommerce again to the top of e-shop layouts.

Regards,
Eric

2013/5/6 Heidi Dehaes <[hidden email]>:

> Hello,
> I am very interested-
>
> Eric
>
> Www.olagos.eu
>
> Op 6 mei 2013 12:32 schreef "Jonatan Soto" <[hidden email]> het
> volgende:
>
>> Hi,
>>
>> Would be anyone interested in convert the existing frontend themes into
>> Bootstrap http://twitter.github.io/bootstrap/?
>>
>> The idea is to create a theme from scratch that will replace the current
>> default and multiplex themes. In order to do that I would propose to
>> create
>> a new branch and start over with the creation of the new theme modifying
>> the markup and screen definitions for the ecommerce and ecomclone
>> applications. Another option would be to leave intact the ecommerce and
>> apply the changes to the ecomclone only but looks like a bit messy to me.
>> I
>> also think that the ecomclone doesn't include all the ftl so that will
>> require to copy the missing ones from the ecommerce app.
>>
>> Paul opened a Jira ticket for that so I think we could use it for this:
>> https://issues.apache.org/jira/browse/OFBIZ-5040
>>
>> Cheers,
>> --
>> -----
>>
>> Jonatan Soto

--
Olagos bvba
http://www.olagos.eu
http://www.olagos.com
http://www.olagos.be
http://www.olagos.nl
Olagos team
Kerkstraat 34
2570 Duffel
Belgium

[Jacques Le Roux]

Agreed, when you think about it having the same theme for frontend (eCommerce) and backend is actually not a necessity.
And frontend (eCommerce) must obviously done before anyway.

To make it more clear Paul, Jonatan and I are working together in ilscipio http://www.ilscipio.com/en/
And we would appreciate if other companies could join in a common theme overhaul effort.

We could synchronize the work effort creating sub-tasks from  https://issues.apache.org/jira/browse/OFBIZ-5040 as suggested Jonatan.

Jacques

From: "Heidi Dehaes" <[hidden email]>

> Hello,
>
> It is not useful to create the same layout and theme for frontend and backend.
> The ecommerce frontend needs to be more and more adapted to the
> "social ecommerce" functionalities.
> This is not the case at all for the backend.
>
> The top of ecommerce websites uses today "social ecommerce" with
> Twitter, Facebook , Linkedin , Pinterest, etc. social engine
> functionalities integrated in the ecommerce frontend. This is really
> needed for marketing someones e-shop today.
>
> I think integration into ofbiz of Bootstrap is a good base and
> necessity to bring ofbiz ecommerce again to the top of e-shop layouts.
>
> Regards,
> Eric
>
> 2013/5/6 Heidi Dehaes <[hidden email]>:
>> Hello,
>> I am very interested-
>>
>> Eric
>>
>> Www.olagos.eu
>>
>> Op 6 mei 2013 12:32 schreef "Jonatan Soto" <[hidden email]> het
>> volgende:
>>
>>> Hi,
>>>
>>> Would be anyone interested in convert the existing frontend themes into
>>> Bootstrap http://twitter.github.io/bootstrap/?
>>>
>>> The idea is to create a theme from scratch that will replace the current
>>> default and multiplex themes. In order to do that I would propose to
>>> create
>>> a new branch and start over with the creation of the new theme modifying
>>> the markup and screen definitions for the ecommerce and ecomclone
>>> applications. Another option would be to leave intact the ecommerce and
>>> apply the changes to the ecomclone only but looks like a bit messy to me.
>>> I
>>> also think that the ecomclone doesn't include all the ftl so that will
>>> require to copy the missing ones from the ecommerce app.
>>>
>>> Paul opened a Jira ticket for that so I think we could use it for this:
>>> https://issues.apache.org/jira/browse/OFBIZ-5040
>>>
>>> Cheers,
>>> --
>>> -----
>>>
>>> Jonatan Soto
>
>
>
> --
> Olagos bvba
> http://www.olagos.eu
> http://www.olagos.com
> http://www.olagos.be
> http://www.olagos.nl
> Olagos team
> Kerkstraat 34
> 2570 Duffel
> Belgium

[Heidi Dehaes - Olagos]

hello,

If we can take part in the effort, we would like to do so.




2013/5/6 Jacques Le Roux <[hidden email]>:

> Agreed, when you think about it having the same theme for frontend (eCommerce) and backend is actually not a necessity.
> And frontend (eCommerce) must obviously done before anyway.
>
> To make it more clear Paul, Jonatan and I are working together in ilscipio http://www.ilscipio.com/en/
> And we would appreciate if other companies could join in a common theme overhaul effort.
>
> We could synchronize the work effort creating sub-tasks from  https://issues.apache.org/jira/browse/OFBIZ-5040 as suggested Jonatan.
>
> Jacques
>
> From: "Heidi Dehaes" <[hidden email]>
>> Hello,
>>
>> It is not useful to create the same layout and theme for frontend and backend.
>> The ecommerce frontend needs to be more and more adapted to the
>> "social ecommerce" functionalities.
>> This is not the case at all for the backend.
>>
>> The top of ecommerce websites uses today "social ecommerce" with
>> Twitter, Facebook , Linkedin , Pinterest, etc. social engine
>> functionalities integrated in the ecommerce frontend. This is really
>> needed for marketing someones e-shop today.
>>
>> I think integration into ofbiz of Bootstrap is a good base and
>> necessity to bring ofbiz ecommerce again to the top of e-shop layouts.
>>
>> Regards,
>> Eric
>>
>> 2013/5/6 Heidi Dehaes <[hidden email]>:
>>> Hello,
>>> I am very interested-
>>>
>>> Eric
>>>
>>> Www.olagos.eu
>>>
>>> Op 6 mei 2013 12:32 schreef "Jonatan Soto" <[hidden email]> het
>>> volgende:
>>>
>>>> Hi,
>>>>
>>>> Would be anyone interested in convert the existing frontend themes into
>>>> Bootstrap http://twitter.github.io/bootstrap/?
>>>>
>>>> The idea is to create a theme from scratch that will replace the current
>>>> default and multiplex themes. In order to do that I would propose to
>>>> create
>>>> a new branch and start over with the creation of the new theme modifying
>>>> the markup and screen definitions for the ecommerce and ecomclone
>>>> applications. Another option would be to leave intact the ecommerce and
>>>> apply the changes to the ecomclone only but looks like a bit messy to me.
>>>> I
>>>> also think that the ecomclone doesn't include all the ftl so that will
>>>> require to copy the missing ones from the ecommerce app.
>>>>
>>>> Paul opened a Jira ticket for that so I think we could use it for this:
>>>> https://issues.apache.org/jira/browse/OFBIZ-5040
>>>>
>>>> Cheers,
>>>> --
>>>> -----
>>>>
>>>> Jonatan Soto
>>
>>
>>
>> --
>> Olagos bvba
>> http://www.olagos.eu
>> http://www.olagos.com
>> http://www.olagos.be
>> http://www.olagos.nl
>> Olagos team
>> Kerkstraat 34
>> 2570 Duffel
>> Belgium

--
Olagos bvba
http://www.olagos.eu
http://www.olagos.com
http://www.olagos.be
http://www.olagos.nl
Olagos team
Kerkstraat 34
2570 Duffel
Belgium

[Heidi Dehaes - Olagos]

still any news?

Eric

2013/5/6 Heidi Dehaes <[hidden email]>:

> hello,
>
> If we can take part in the effort, we would like to do so.
>
>
>
>
> 2013/5/6 Jacques Le Roux <[hidden email]>:
>> Agreed, when you think about it having the same theme for frontend (eCommerce) and backend is actually not a necessity.
>> And frontend (eCommerce) must obviously done before anyway.
>>
>> To make it more clear Paul, Jonatan and I are working together in ilscipio http://www.ilscipio.com/en/
>> And we would appreciate if other companies could join in a common theme overhaul effort.
>>
>> We could synchronize the work effort creating sub-tasks from  https://issues.apache.org/jira/browse/OFBIZ-5040 as suggested Jonatan.
>>
>> Jacques
>>
>> From: "Heidi Dehaes" <[hidden email]>
>>> Hello,
>>>
>>> It is not useful to create the same layout and theme for frontend and backend.
>>> The ecommerce frontend needs to be more and more adapted to the
>>> "social ecommerce" functionalities.
>>> This is not the case at all for the backend.
>>>
>>> The top of ecommerce websites uses today "social ecommerce" with
>>> Twitter, Facebook , Linkedin , Pinterest, etc. social engine
>>> functionalities integrated in the ecommerce frontend. This is really
>>> needed for marketing someones e-shop today.
>>>
>>> I think integration into ofbiz of Bootstrap is a good base and
>>> necessity to bring ofbiz ecommerce again to the top of e-shop layouts.
>>>
>>> Regards,
>>> Eric
>>>
>>> 2013/5/6 Heidi Dehaes <[hidden email]>:
>>>> Hello,
>>>> I am very interested-
>>>>
>>>> Eric
>>>>
>>>> Www.olagos.eu
>>>>
>>>> Op 6 mei 2013 12:32 schreef "Jonatan Soto" <[hidden email]> het
>>>> volgende:
>>>>
>>>>> Hi,
>>>>>
>>>>> Would be anyone interested in convert the existing frontend themes into
>>>>> Bootstrap http://twitter.github.io/bootstrap/?
>>>>>
>>>>> The idea is to create a theme from scratch that will replace the current
>>>>> default and multiplex themes. In order to do that I would propose to
>>>>> create
>>>>> a new branch and start over with the creation of the new theme modifying
>>>>> the markup and screen definitions for the ecommerce and ecomclone
>>>>> applications. Another option would be to leave intact the ecommerce and
>>>>> apply the changes to the ecomclone only but looks like a bit messy to me.
>>>>> I
>>>>> also think that the ecomclone doesn't include all the ftl so that will
>>>>> require to copy the missing ones from the ecommerce app.
>>>>>
>>>>> Paul opened a Jira ticket for that so I think we could use it for this:
>>>>> https://issues.apache.org/jira/browse/OFBIZ-5040
>>>>>
>>>>> Cheers,
>>>>> --
>>>>> -----
>>>>>
>>>>> Jonatan Soto
>>>
>>>
>>>
>>> --
>>> Olagos bvba
>>> http://www.olagos.eu
>>> http://www.olagos.com
>>> http://www.olagos.be
>>> http://www.olagos.nl
>>> Olagos team
>>> Kerkstraat 34
>>> 2570 Duffel
>>> Belgium
>
>
>
> --
> Olagos bvba
> http://www.olagos.eu
> http://www.olagos.com
> http://www.olagos.be
> http://www.olagos.nl
> Olagos team
> Kerkstraat 34
> 2570 Duffel
> Belgium

--
Olagos bvba
http://www.olagos.eu
http://www.olagos.com
http://www.olagos.be
http://www.olagos.nl
Olagos team
Kerkstraat 34
2570 Duffel
Belgium

[jonatan soto]

I'd wait a bit longer to see if somebody else is interested. Also since the
intention is to do donate it to the community I'd like to know other
opinions about it. More concretely I'd like to know PMC & committers
opinions and suggestions (if any).

Basically the idea is to drop the existing frontend themes and replace them
by one theme based on Bootstrap. Depending on how we do it, probably we can
create a new set of frontend themes based on Bootstrap.

Well, at some point we will need to define what exactly are we going to do
and then how it will be handled.



On Tue, May 7, 2013 at 2:58 PM, Heidi Dehaes <[hidden email]> wrote:

> still any news?
>
> Eric
>
> 2013/5/6 Heidi Dehaes <[hidden email]>:
> > hello,
> >
> > If we can take part in the effort, we would like to do so.
> >
> >
> >
> >
> > 2013/5/6 Jacques Le Roux <[hidden email]>:
> >> Agreed, when you think about it having the same theme for frontend
> (eCommerce) and backend is actually not a necessity.
> >> And frontend (eCommerce) must obviously done before anyway.
> >>
> >> To make it more clear Paul, Jonatan and I are working together in
> ilscipio http://www.ilscipio.com/en/
> >> And we would appreciate if other companies could join in a common theme
> overhaul effort.
> >>
> >> We could synchronize the work effort creating sub-tasks from
> https://issues.apache.org/jira/browse/OFBIZ-5040 as suggested Jonatan.
> >>
> >> Jacques
> >>
> >> From: "Heidi Dehaes" <[hidden email]>
> >>> Hello,
> >>>
> >>> It is not useful to create the same layout and theme for frontend and
> backend.
> >>> The ecommerce frontend needs to be more and more adapted to the
> >>> "social ecommerce" functionalities.
> >>> This is not the case at all for the backend.
> >>>
> >>> The top of ecommerce websites uses today "social ecommerce" with
> >>> Twitter, Facebook , Linkedin , Pinterest, etc. social engine
> >>> functionalities integrated in the ecommerce frontend. This is really
> >>> needed for marketing someones e-shop today.
> >>>
> >>> I think integration into ofbiz of Bootstrap is a good base and
> >>> necessity to bring ofbiz ecommerce again to the top of e-shop layouts.
> >>>
> >>> Regards,
> >>> Eric
> >>>
> >>> 2013/5/6 Heidi Dehaes <[hidden email]>:
> >>>> Hello,
> >>>> I am very interested-
> >>>>
> >>>> Eric
> >>>>
> >>>> Www.olagos.eu
> >>>>
> >>>> Op 6 mei 2013 12:32 schreef "Jonatan Soto" <[hidden email]>
> het
> >>>> volgende:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> Would be anyone interested in convert the existing frontend themes
> into
> >>>>> Bootstrap http://twitter.github.io/bootstrap/?
> >>>>>
> >>>>> The idea is to create a theme from scratch that will replace the
> current
> >>>>> default and multiplex themes. In order to do that I would propose to
> >>>>> create
> >>>>> a new branch and start over with the creation of the new theme
> modifying
> >>>>> the markup and screen definitions for the ecommerce and ecomclone
> >>>>> applications. Another option would be to leave intact the ecommerce
> and
> >>>>> apply the changes to the ecomclone only but looks like a bit messy
> to me.
> >>>>> I
> >>>>> also think that the ecomclone doesn't include all the ftl so that
> will
> >>>>> require to copy the missing ones from the ecommerce app.
> >>>>>
> >>>>> Paul opened a Jira ticket for that so I think we could use it for
> this:
> >>>>> https://issues.apache.org/jira/browse/OFBIZ-5040
> >>>>>
> >>>>> Cheers,
> >>>>> --
> >>>>> -----
> >>>>>
> >>>>> Jonatan Soto
> >>>
> >>>
> >>>
> >>> --
> >>> Olagos bvba
> >>> http://www.olagos.eu
> >>> http://www.olagos.com
> >>> http://www.olagos.be
> >>> http://www.olagos.nl
> >>> Olagos team
> >>> Kerkstraat 34
> >>> 2570 Duffel
> >>> Belgium
> >
> >
> >
> > --
> > Olagos bvba
> > http://www.olagos.eu
> > http://www.olagos.com
> > http://www.olagos.be
> > http://www.olagos.nl
> > Olagos team
> > Kerkstraat 34
> > 2570 Duffel
> > Belgium
>
>
>
> --
> Olagos bvba
> http://www.olagos.eu
> http://www.olagos.com
> http://www.olagos.be
> http://www.olagos.nl
> Olagos team
> Kerkstraat 34
> 2570 Duffel
> Belgium
>

--
-----

Jonatan Soto

[Heidi Dehaes - Olagos]

ok


2013/5/7 Jonatan Soto <[hidden email]>:

> I'd wait a bit longer to see if somebody else is interested. Also since the
> intention is to do donate it to the community I'd like to know other
> opinions about it. More concretely I'd like to know PMC & committers
> opinions and suggestions (if any).
>
> Basically the idea is to drop the existing frontend themes and replace them
> by one theme based on Bootstrap. Depending on how we do it, probably we can
> create a new set of frontend themes based on Bootstrap.
>
> Well, at some point we will need to define what exactly are we going to do
> and then how it will be handled.
>
>
>
> On Tue, May 7, 2013 at 2:58 PM, Heidi Dehaes <[hidden email]> wrote:
>
>> still any news?
>>
>> Eric
>>
>> 2013/5/6 Heidi Dehaes <[hidden email]>:
>> > hello,
>> >
>> > If we can take part in the effort, we would like to do so.
>> >
>> >
>> >
>> >
>> > 2013/5/6 Jacques Le Roux <[hidden email]>:
>> >> Agreed, when you think about it having the same theme for frontend
>> (eCommerce) and backend is actually not a necessity.
>> >> And frontend (eCommerce) must obviously done before anyway.
>> >>
>> >> To make it more clear Paul, Jonatan and I are working together in
>> ilscipio http://www.ilscipio.com/en/
>> >> And we would appreciate if other companies could join in a common theme
>> overhaul effort.
>> >>
>> >> We could synchronize the work effort creating sub-tasks from
>> https://issues.apache.org/jira/browse/OFBIZ-5040 as suggested Jonatan.
>> >>
>> >> Jacques
>> >>
>> >> From: "Heidi Dehaes" <[hidden email]>
>> >>> Hello,
>> >>>
>> >>> It is not useful to create the same layout and theme for frontend and
>> backend.
>> >>> The ecommerce frontend needs to be more and more adapted to the
>> >>> "social ecommerce" functionalities.
>> >>> This is not the case at all for the backend.
>> >>>
>> >>> The top of ecommerce websites uses today "social ecommerce" with
>> >>> Twitter, Facebook , Linkedin , Pinterest, etc. social engine
>> >>> functionalities integrated in the ecommerce frontend. This is really
>> >>> needed for marketing someones e-shop today.
>> >>>
>> >>> I think integration into ofbiz of Bootstrap is a good base and
>> >>> necessity to bring ofbiz ecommerce again to the top of e-shop layouts.
>> >>>
>> >>> Regards,
>> >>> Eric
>> >>>
>> >>> 2013/5/6 Heidi Dehaes <[hidden email]>:
>> >>>> Hello,
>> >>>> I am very interested-
>> >>>>
>> >>>> Eric
>> >>>>
>> >>>> Www.olagos.eu
>> >>>>
>> >>>> Op 6 mei 2013 12:32 schreef "Jonatan Soto" <[hidden email]>
>> het
>> >>>> volgende:
>> >>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> Would be anyone interested in convert the existing frontend themes
>> into
>> >>>>> Bootstrap http://twitter.github.io/bootstrap/?
>> >>>>>
>> >>>>> The idea is to create a theme from scratch that will replace the
>> current
>> >>>>> default and multiplex themes. In order to do that I would propose to
>> >>>>> create
>> >>>>> a new branch and start over with the creation of the new theme
>> modifying
>> >>>>> the markup and screen definitions for the ecommerce and ecomclone
>> >>>>> applications. Another option would be to leave intact the ecommerce
>> and
>> >>>>> apply the changes to the ecomclone only but looks like a bit messy
>> to me.
>> >>>>> I
>> >>>>> also think that the ecomclone doesn't include all the ftl so that
>> will
>> >>>>> require to copy the missing ones from the ecommerce app.
>> >>>>>
>> >>>>> Paul opened a Jira ticket for that so I think we could use it for
>> this:
>> >>>>> https://issues.apache.org/jira/browse/OFBIZ-5040
>> >>>>>
>> >>>>> Cheers,
>> >>>>> --
>> >>>>> -----
>> >>>>>
>> >>>>> Jonatan Soto
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Olagos bvba
>> >>> http://www.olagos.eu
>> >>> http://www.olagos.com
>> >>> http://www.olagos.be
>> >>> http://www.olagos.nl
>> >>> Olagos team
>> >>> Kerkstraat 34
>> >>> 2570 Duffel
>> >>> Belgium
>> >
>> >
>> >
>> > --
>> > Olagos bvba
>> > http://www.olagos.eu
>> > http://www.olagos.com
>> > http://www.olagos.be
>> > http://www.olagos.nl
>> > Olagos team
>> > Kerkstraat 34
>> > 2570 Duffel
>> > Belgium
>>
>>
>>
>> --
>> Olagos bvba
>> http://www.olagos.eu
>> http://www.olagos.com
>> http://www.olagos.be
>> http://www.olagos.nl
>> Olagos team
>> Kerkstraat 34
>> 2570 Duffel
>> Belgium
>>
>
>
>
> --
> -----
>
> Jonatan Soto

--
Olagos bvba
http://www.olagos.eu
http://www.olagos.com
http://www.olagos.be
http://www.olagos.nl
Olagos team
Kerkstraat 34
2570 Duffel
Belgium

[Richard Siddall]

Jonatan Soto wrote:
> Would be anyone interested in convert the existing frontend themes into
> Bootstrap http://twitter.github.io/bootstrap/?
>
> The idea is to create a theme from scratch that will replace the current
> default and multiplex themes.
[snip]

While I think having more modern front-end themes would be great, let me
play devil's advocate...

Why Bootstrap?

Why not Zurb Foundation (http://foundation.zurb.com/), HTML5 Boilerplate
(http://html5boilerplate.com/) or some other starting point?  Or as
Scott Kellum argued on the Compass list (on January 8), use a
combination of components such as Susy, Sassy-buttons, Color-Schemer,
and Modular-Scale.

Bootstrap is an easy way of getting a lot of functionality, but it's
arguable overused.  It's fast becoming to HTML5 frameworks what Times
Roman is to web fonts.  If you want your web shop to look like everyone
else's web shop, it's a great choice.  If you want to differentiate
yourself in the market, use something else.

Plus, many Bootstrap-based themes just throw the whole bloated framework
at the browser, regardless of which pieces they use, slowing page loads
and wasting mobile bandwidth allocations.  But Bootstrap is built on
LESS, so you can choose which chunks of CSS and JavaScript should be
included in your site's copy of Bootstrap, as well as using variables
and mixins to get more consistent CSS styling.

LESS is based on JavaScript, which practically requires you to install
Node.js to use it.  Zurb Foundation is based on SASS, which is written
in Ruby.  It looks like SASS will run on JRuby on the JVM.

To summarize:
- Bootstrap is just one of several great HTML5 frameworks
- You can get the same effects using straight CSS3 and JavaScript, or
smaller projects for areas like responsive design, button styling, text
spacing, etc.
- Bootstrap is overused
- Bootstrap is frequently ineptly used, penalizing the end user
- A major reason to use Bootstrap is to use LESS and other languages
that abstract CSS and JavaScript
- Bootstrap may not be the best framework for a Java-based project

I hope this helps.

Regards,

        Richard Siddall

[Heidi Dehaes - Olagos]

Zurb seems to be extremely nice and modern.

Eric

2013/5/7 Richard Siddall <[hidden email]>:

> Jonatan Soto wrote:
>>
>> Would be anyone interested in convert the existing frontend themes into
>> Bootstrap http://twitter.github.io/bootstrap/?
>>
>> The idea is to create a theme from scratch that will replace the current
>> default and multiplex themes.
>
> [snip]
>
> While I think having more modern front-end themes would be great, let me
> play devil's advocate...
>
> Why Bootstrap?
>
> Why not Zurb Foundation (http://foundation.zurb.com/), HTML5 Boilerplate
> (http://html5boilerplate.com/) or some other starting point?  Or as Scott
> Kellum argued on the Compass list (on January 8), use a combination of
> components such as Susy, Sassy-buttons, Color-Schemer, and Modular-Scale.
>
> Bootstrap is an easy way of getting a lot of functionality, but it's
> arguable overused.  It's fast becoming to HTML5 frameworks what Times Roman
> is to web fonts.  If you want your web shop to look like everyone else's web
> shop, it's a great choice.  If you want to differentiate yourself in the
> market, use something else.
>
> Plus, many Bootstrap-based themes just throw the whole bloated framework at
> the browser, regardless of which pieces they use, slowing page loads and
> wasting mobile bandwidth allocations.  But Bootstrap is built on LESS, so
> you can choose which chunks of CSS and JavaScript should be included in your
> site's copy of Bootstrap, as well as using variables and mixins to get more
> consistent CSS styling.
>
> LESS is based on JavaScript, which practically requires you to install
> Node.js to use it.  Zurb Foundation is based on SASS, which is written in
> Ruby.  It looks like SASS will run on JRuby on the JVM.
>
> To summarize:
> - Bootstrap is just one of several great HTML5 frameworks
> - You can get the same effects using straight CSS3 and JavaScript, or
> smaller projects for areas like responsive design, button styling, text
> spacing, etc.
> - Bootstrap is overused
> - Bootstrap is frequently ineptly used, penalizing the end user
> - A major reason to use Bootstrap is to use LESS and other languages that
> abstract CSS and JavaScript
> - Bootstrap may not be the best framework for a Java-based project
>
> I hope this helps.
>
> Regards,
>
>         Richard Siddall

--
Olagos bvba
http://www.olagos.eu
http://www.olagos.com
http://www.olagos.be
http://www.olagos.nl
Olagos team
Kerkstraat 34
2570 Duffel
Belgium

[Adrian Crum-3]

I agree in principle with this reply. Very few shops use the OFBiz
eCommerce front-end - it wasn't intended to be used as-is, instead its
there for demonstration purposes.

Each business will have a preference for styling their site, so choosing
one theme over all others seems presumptuous.

As I mentioned in the Jira issue, HTML cleanups are always welcome.
Consistent and concise markup makes it easier to design themes - and
from my perspective that provides the most benefit to OFBiz developers.

-Adrian

On 5/7/2013 2:49 PM, Richard Siddall wrote:

> Jonatan Soto wrote:
>> Would be anyone interested in convert the existing frontend themes into
>> Bootstrap http://twitter.github.io/bootstrap/?
>>
>> The idea is to create a theme from scratch that will replace the current
>> default and multiplex themes.
> [snip]
>
> While I think having more modern front-end themes would be great, let
> me play devil's advocate...
>
> Why Bootstrap?
>
> Why not Zurb Foundation (http://foundation.zurb.com/), HTML5
> Boilerplate (http://html5boilerplate.com/) or some other starting
> point?  Or as Scott Kellum argued on the Compass list (on January 8),
> use a combination of components such as Susy, Sassy-buttons,
> Color-Schemer, and Modular-Scale.
>
> Bootstrap is an easy way of getting a lot of functionality, but it's
> arguable overused.  It's fast becoming to HTML5 frameworks what Times
> Roman is to web fonts.  If you want your web shop to look like
> everyone else's web shop, it's a great choice.  If you want to
> differentiate yourself in the market, use something else.
>
> Plus, many Bootstrap-based themes just throw the whole bloated
> framework at the browser, regardless of which pieces they use, slowing
> page loads and wasting mobile bandwidth allocations.  But Bootstrap is
> built on LESS, so you can choose which chunks of CSS and JavaScript
> should be included in your site's copy of Bootstrap, as well as using
> variables and mixins to get more consistent CSS styling.
>
> LESS is based on JavaScript, which practically requires you to install
> Node.js to use it.  Zurb Foundation is based on SASS, which is written
> in Ruby.  It looks like SASS will run on JRuby on the JVM.
>
> To summarize:
> - Bootstrap is just one of several great HTML5 frameworks
> - You can get the same effects using straight CSS3 and JavaScript, or
> smaller projects for areas like responsive design, button styling,
> text spacing, etc.
> - Bootstrap is overused
> - Bootstrap is frequently ineptly used, penalizing the end user
> - A major reason to use Bootstrap is to use LESS and other languages
> that abstract CSS and JavaScript
> - Bootstrap may not be the best framework for a Java-based project
>
> I hope this helps.
>
> Regards,
>
>     Richard Siddall

[Jacques Le Roux]

Thanks Richard,

Would you be interested in such an effort?

For those interested by this discussion and, like me, not aware of those frameworks, I found those 2 Quoras links
http://www.quora.com/Front-End-Web-Development/Which-should-I-use-Foundation-Bootstrap-or-HTML5-Boilerplate
http://www.quora.com/Is-Bootstrap-a-complement-OR-an-alternative-to-HTML5-Boilerplate-or-viceversa

Jacques

From: "Richard Siddall" <[hidden email]>

> Jonatan Soto wrote:
>> Would be anyone interested in convert the existing frontend themes into
>> Bootstrap http://twitter.github.io/bootstrap/?
>>
>> The idea is to create a theme from scratch that will replace the current
>> default and multiplex themes.
> [snip]
>
> While I think having more modern front-end themes would be great, let me
> play devil's advocate...
>
> Why Bootstrap?
>
> Why not Zurb Foundation (http://foundation.zurb.com/), HTML5 Boilerplate
> (http://html5boilerplate.com/) or some other starting point?  Or as
> Scott Kellum argued on the Compass list (on January 8), use a
> combination of components such as Susy, Sassy-buttons, Color-Schemer,
> and Modular-Scale.
>
> Bootstrap is an easy way of getting a lot of functionality, but it's
> arguable overused.  It's fast becoming to HTML5 frameworks what Times
> Roman is to web fonts.  If you want your web shop to look like everyone
> else's web shop, it's a great choice.  If you want to differentiate
> yourself in the market, use something else.
>
> Plus, many Bootstrap-based themes just throw the whole bloated framework
> at the browser, regardless of which pieces they use, slowing page loads
> and wasting mobile bandwidth allocations.  But Bootstrap is built on
> LESS, so you can choose which chunks of CSS and JavaScript should be
> included in your site's copy of Bootstrap, as well as using variables
> and mixins to get more consistent CSS styling.
>
> LESS is based on JavaScript, which practically requires you to install
> Node.js to use it.  Zurb Foundation is based on SASS, which is written
> in Ruby.  It looks like SASS will run on JRuby on the JVM.
>
> To summarize:
> - Bootstrap is just one of several great HTML5 frameworks
> - You can get the same effects using straight CSS3 and JavaScript, or
> smaller projects for areas like responsive design, button styling, text
> spacing, etc.
> - Bootstrap is overused
> - Bootstrap is frequently ineptly used, penalizing the end user
> - A major reason to use Bootstrap is to use LESS and other languages
> that abstract CSS and JavaScript
> - Bootstrap may not be the best framework for a Java-based project
>
> I hope this helps.
>
> Regards,
>
> Richard Siddall

[jonatan soto]

Hi Richard,

First of all, thanks a lot for you input.

In response to your question about why Bootstrap, I just suggested it
because that's the one I already used in a couple of OFBiz projects.
Actually the designer who introduced Bootstrap for one of those projects
also suggested Zurb, but since I already had a bit of Bootstrap knowledge I
decided to use it as well for the other project.
Well, that doesn't change the fact that you are right. There is no reason
to do it with Bootstrap exclusively so I think we could rename this thread
to just 'Converting frontend themes to a HTML5 framework' until we decide
which framework (if any) we should use.
As a side note, I must say that I am not a web designer.

From my understanding your idea is to let users to compile a customized
framework based on Bootstrap, HTML5Boilerplate or Zurb within OFBiz,
correct? If so, my initial idea was a bit different, I just wanted to use a
customized version of Bootstrap compiled directly from their site:
http://twitter.github.io/bootstrap/customize.html




On Tue, May 7, 2013 at 3:49 PM, Richard Siddall <[hidden email]
> wrote:

> Jonatan Soto wrote:
>
>> Would be anyone interested in convert the existing frontend themes into
>> Bootstrap http://twitter.github.io/**bootstrap/<http://twitter.github.io/bootstrap/>
>> ?
>>
>> The idea is to create a theme from scratch that will replace the current
>> default and multiplex themes.
>>
> [snip]
>
> While I think having more modern front-end themes would be great, let me
> play devil's advocate...
>
> Why Bootstrap?
>
> Why not Zurb Foundation (http://foundation.zurb.com/), HTML5 Boilerplate (
> http://html5boilerplate.com/) or some other starting point?  Or as Scott
> Kellum argued on the Compass list (on January 8), use a combination of
> components such as Susy, Sassy-buttons, Color-Schemer, and Modular-Scale.
>
> Bootstrap is an easy way of getting a lot of functionality, but it's
> arguable overused.  It's fast becoming to HTML5 frameworks what Times Roman
> is to web fonts.  If you want your web shop to look like everyone else's
> web shop, it's a great choice.  If you want to differentiate yourself in
> the market, use something else.
>
> Plus, many Bootstrap-based themes just throw the whole bloated framework
> at the browser, regardless of which pieces they use, slowing page loads and
> wasting mobile bandwidth allocations.  But Bootstrap is built on LESS, so
> you can choose which chunks of CSS and JavaScript should be included in
> your site's copy of Bootstrap, as well as using variables and mixins to get
> more consistent CSS styling.
>
> LESS is based on JavaScript, which practically requires you to install
> Node.js to use it.  Zurb Foundation is based on SASS, which is written in
> Ruby.  It looks like SASS will run on JRuby on the JVM.
>
> To summarize:
> - Bootstrap is just one of several great HTML5 frameworks
> - You can get the same effects using straight CSS3 and JavaScript, or
> smaller projects for areas like responsive design, button styling, text
> spacing, etc.
> - Bootstrap is overused
> - Bootstrap is frequently ineptly used, penalizing the end user
> - A major reason to use Bootstrap is to use LESS and other languages that
> abstract CSS and JavaScript
> - Bootstrap may not be the best framework for a Java-based project
>
> I hope this helps.
>
> Regards,
>
>         Richard Siddall
>

--
-----

Jonatan Soto

[Christian Geisert]

Am 07.05.2013 16:29, schrieb Adrian Crum:
> I agree in principle with this reply. Very few shops use the OFBiz
> eCommerce front-end - it wasn't intended to be used as-is, instead its
> there for demonstration purposes.
>
> Each business will have a preference for styling their site, so choosing
> one theme over all others seems presumptuous.

But I think it's important to have a good looking Out of the Box
Ecommerce front-end to attract new users.

Christian

[jonatan soto]

Hi Adrian,

Thanks a lot for your input.

I agree with you that OFBiz is not an eCommerce platform and also that the
current themes are there for demonstration but that doesn't change the fact
that it needs a complete rework. So what I'm referring to is more about to
adapt all of the ftls and screen definitions using one of the fancy HTML5
frameworks available rather a cleanup.



On Tue, May 7, 2013 at 4:29 PM, Adrian Crum <
[hidden email]> wrote:

> I agree in principle with this reply. Very few shops use the OFBiz
> eCommerce front-end - it wasn't intended to be used as-is, instead its
> there for demonstration purposes.
>
> Each business will have a preference for styling their site, so choosing
> one theme over all others seems presumptuous.
>
> As I mentioned in the Jira issue, HTML cleanups are always welcome.
> Consistent and concise markup makes it easier to design themes - and from
> my perspective that provides the most benefit to OFBiz developers.
>
> -Adrian
>
>
> On 5/7/2013 2:49 PM, Richard Siddall wrote:
>
>> Jonatan Soto wrote:
>>
>>> Would be anyone interested in convert the existing frontend themes into
>>> Bootstrap http://twitter.github.io/**bootstrap/<http://twitter.github.io/bootstrap/>
>>> ?
>>>
>>> The idea is to create a theme from scratch that will replace the current
>>> default and multiplex themes.
>>>
>> [snip]
>>
>> While I think having more modern front-end themes would be great, let me
>> play devil's advocate...
>>
>> Why Bootstrap?
>>
>> Why not Zurb Foundation (http://foundation.zurb.com/), HTML5 Boilerplate
>> (http://html5boilerplate.com/) or some other starting point?  Or as
>> Scott Kellum argued on the Compass list (on January 8), use a combination
>> of components such as Susy, Sassy-buttons, Color-Schemer, and Modular-Scale.
>>
>> Bootstrap is an easy way of getting a lot of functionality, but it's
>> arguable overused.  It's fast becoming to HTML5 frameworks what Times Roman
>> is to web fonts.  If you want your web shop to look like everyone else's
>> web shop, it's a great choice.  If you want to differentiate yourself in
>> the market, use something else.
>>
>> Plus, many Bootstrap-based themes just throw the whole bloated framework
>> at the browser, regardless of which pieces they use, slowing page loads and
>> wasting mobile bandwidth allocations.  But Bootstrap is built on LESS, so
>> you can choose which chunks of CSS and JavaScript should be included in
>> your site's copy of Bootstrap, as well as using variables and mixins to get
>> more consistent CSS styling.
>>
>> LESS is based on JavaScript, which practically requires you to install
>> Node.js to use it.  Zurb Foundation is based on SASS, which is written in
>> Ruby.  It looks like SASS will run on JRuby on the JVM.
>>
>> To summarize:
>> - Bootstrap is just one of several great HTML5 frameworks
>> - You can get the same effects using straight CSS3 and JavaScript, or
>> smaller projects for areas like responsive design, button styling, text
>> spacing, etc.
>> - Bootstrap is overused
>> - Bootstrap is frequently ineptly used, penalizing the end user
>> - A major reason to use Bootstrap is to use LESS and other languages that
>> abstract CSS and JavaScript
>> - Bootstrap may not be the best framework for a Java-based project
>>
>> I hope this helps.
>>
>> Regards,
>>
>>     Richard Siddall
>>
>
>

--
-----

Jonatan Soto

[Adrian Crum-3]

I understand what you are proposing. So, let me try this again...

HTML cleanups are fine. Updating the markup to HTML 5 is fine. That sort
of overhaul has been done before and it is always welcome.

What we are discussing here is introducing an outside styling framework
for the eCommerce application. I question the need for the framework
because most businesses don't use the eCommerce application out of the
box. In other words, we would be investing a lot of time and effort into
something that a lot of businesses will just throw away.

As Christian pointed out, it would be nice to have a better looking
eCommerce demonstration, and I agree. But again, I think that can be
done with consistent and concise markup - coupled with some good styling.

I'm not opposed to the external framework idea, I just question the need
for it.

-Adrian

On 5/7/2013 4:21 PM, Jonatan Soto wrote:

> Hi Adrian,
>
> Thanks a lot for your input.
>
> I agree with you that OFBiz is not an eCommerce platform and also that the
> current themes are there for demonstration but that doesn't change the fact
> that it needs a complete rework. So what I'm referring to is more about to
> adapt all of the ftls and screen definitions using one of the fancy HTML5
> frameworks available rather a cleanup.
>
>
>
> On Tue, May 7, 2013 at 4:29 PM, Adrian Crum <
> [hidden email]> wrote:
>
>> I agree in principle with this reply. Very few shops use the OFBiz
>> eCommerce front-end - it wasn't intended to be used as-is, instead its
>> there for demonstration purposes.
>>
>> Each business will have a preference for styling their site, so choosing
>> one theme over all others seems presumptuous.
>>
>> As I mentioned in the Jira issue, HTML cleanups are always welcome.
>> Consistent and concise markup makes it easier to design themes - and from
>> my perspective that provides the most benefit to OFBiz developers.
>>
>> -Adrian
>>
>>
>> On 5/7/2013 2:49 PM, Richard Siddall wrote:
>>
>>> Jonatan Soto wrote:
>>>
>>>> Would be anyone interested in convert the existing frontend themes into
>>>> Bootstrap http://twitter.github.io/**bootstrap/<http://twitter.github.io/bootstrap/>
>>>> ?
>>>>
>>>> The idea is to create a theme from scratch that will replace the current
>>>> default and multiplex themes.
>>>>
>>> [snip]
>>>
>>> While I think having more modern front-end themes would be great, let me
>>> play devil's advocate...
>>>
>>> Why Bootstrap?
>>>
>>> Why not Zurb Foundation (http://foundation.zurb.com/), HTML5 Boilerplate
>>> (http://html5boilerplate.com/) or some other starting point?  Or as
>>> Scott Kellum argued on the Compass list (on January 8), use a combination
>>> of components such as Susy, Sassy-buttons, Color-Schemer, and Modular-Scale.
>>>
>>> Bootstrap is an easy way of getting a lot of functionality, but it's
>>> arguable overused.  It's fast becoming to HTML5 frameworks what Times Roman
>>> is to web fonts.  If you want your web shop to look like everyone else's
>>> web shop, it's a great choice.  If you want to differentiate yourself in
>>> the market, use something else.
>>>
>>> Plus, many Bootstrap-based themes just throw the whole bloated framework
>>> at the browser, regardless of which pieces they use, slowing page loads and
>>> wasting mobile bandwidth allocations.  But Bootstrap is built on LESS, so
>>> you can choose which chunks of CSS and JavaScript should be included in
>>> your site's copy of Bootstrap, as well as using variables and mixins to get
>>> more consistent CSS styling.
>>>
>>> LESS is based on JavaScript, which practically requires you to install
>>> Node.js to use it.  Zurb Foundation is based on SASS, which is written in
>>> Ruby.  It looks like SASS will run on JRuby on the JVM.
>>>
>>> To summarize:
>>> - Bootstrap is just one of several great HTML5 frameworks
>>> - You can get the same effects using straight CSS3 and JavaScript, or
>>> smaller projects for areas like responsive design, button styling, text
>>> spacing, etc.
>>> - Bootstrap is overused
>>> - Bootstrap is frequently ineptly used, penalizing the end user
>>> - A major reason to use Bootstrap is to use LESS and other languages that
>>> abstract CSS and JavaScript
>>> - Bootstrap may not be the best framework for a Java-based project
>>>
>>> I hope this helps.
>>>
>>> Regards,
>>>
>>>      Richard Siddall
>>>
>>
>