dropping crumbs styling from brainfood/erik schuessler

[Adam Heath-2]

http://www.brainfood.com/ofbizbackend

[Adrian Crum]

It looks industrial. Nice!

-Adrian

Adam Heath wrote:
> http://www.brainfood.com/ofbizbackend
>

[Tim Ruppert]

Very, very nice - I see that Erik's still shooting for that ApacheERP  
setup that he did years ago.  Awesome!

Cheers,
Ruppert
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

On Nov 25, 2009, at 1:23 PM, Adam Heath wrote:

> http://www.brainfood.com/ofbizbackend

[Scott Gray-2]

INSERT INTO THEME_REVIEW
(THEME_REVIEW_ID, USER_LOGIN_ID, THEME_ID, THEME_RATING, THEME_REVIEW)
VALUES ('10000', 'lektran', 'BF_DROPCRMB', 5, 'Looks awesome, would  
view again. A++++');

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 26/11/2009, at 9:23 AM, Adam Heath wrote:

> http://www.brainfood.com/ofbizbackend

[Bruno Busco]

uhao!
That's great!

Now I see what you meant by "sleeping giant" !

-Bruno


2009/11/25 Adam Heath <[hidden email]>:
> http://www.brainfood.com/ofbizbackend
>

[Tim Ruppert]

Right now sleeping giant means not yet committed to the project :)  
Definitely looking for this look and feel to make it's way in there  
Erik - thanks so much!  I'm glad you've found the right avenue for  
that style.

Cheers,
Ruppert

On Nov 25, 2009, at 2:13 PM, Bruno Busco wrote:

> uhao!
> That's great!
>
> Now I see what you meant by "sleeping giant" !
>
> -Bruno
>
>
> 2009/11/25 Adam Heath <[hidden email]>:
>> http://www.brainfood.com/ofbizbackend
>>

[Bruno Busco]

Hi,
Any step from the "sleeping giant" ? ;-)

-Bruno

2009/11/25 Tim Ruppert <[hidden email]>:

> Right now sleeping giant means not yet committed to the project :)
>  Definitely looking for this look and feel to make it's way in there Erik -
> thanks so much!  I'm glad you've found the right avenue for that style.
>
> Cheers,
> Ruppert
>
> On Nov 25, 2009, at 2:13 PM, Bruno Busco wrote:
>
>> uhao!
>> That's great!
>>
>> Now I see what you meant by "sleeping giant" !
>>
>> -Bruno
>>
>>
>> 2009/11/25 Adam Heath <[hidden email]>:
>>>
>>> http://www.brainfood.com/ofbizbackend
>>>
>
>

[Jacques Le Roux]

I wonder if  the "sleeping giant" is not using Git and will flood us sooner or later.
That's one of the dark aspect of git usage. You are able to commit a lot in a single shoot, hard to review.
Nothing is perfect is this world

Jacques

From: "Bruno Busco" <[hidden email]>

> Hi,
> Any step from the "sleeping giant" ? ;-)
>
> -Bruno
>
> 2009/11/25 Tim Ruppert <[hidden email]>:
>> Right now sleeping giant means not yet committed to the project :)
>> Definitely looking for this look and feel to make it's way in there Erik -
>> thanks so much! I'm glad you've found the right avenue for that style.
>>
>> Cheers,
>> Ruppert
>>
>> On Nov 25, 2009, at 2:13 PM, Bruno Busco wrote:
>>
>>> uhao!
>>> That's great!
>>>
>>> Now I see what you meant by "sleeping giant" !
>>>
>>> -Bruno
>>>
>>>
>>> 2009/11/25 Adam Heath <[hidden email]>:
>>>>
>>>> http://www.brainfood.com/ofbizbackend
>>>>
>>
>>
>

[Scott Gray-2]

That's not how git is being used, it simply allows you to easily break  
up a single task into multiple more logically separated commits, which  
actually makes for easier reviews.

It is possible to do what you are suggesting but I don't think that is  
what is actually happening.

Regards
Scott

On 11/12/2009, at 11:24 PM, Jacques Le Roux wrote:

> I wonder if  the "sleeping giant" is not using Git and will flood us  
> sooner or later.
> That's one of the dark aspect of git usage. You are able to commit a  
> lot in a single shoot, hard to review.
> Nothing is perfect is this world
>
> Jacques
>
> From: "Bruno Busco" <[hidden email]>
>> Hi,
>> Any step from the "sleeping giant" ? ;-)
>> -Bruno
>> 2009/11/25 Tim Ruppert <[hidden email]>:
>>> Right now sleeping giant means not yet committed to the project :)
>>> Definitely looking for this look and feel to make it's way in  
>>> there Erik -
>>> thanks so much! I'm glad you've found the right avenue for that  
>>> style.
>>>
>>> Cheers,
>>> Ruppert
>>>
>>> On Nov 25, 2009, at 2:13 PM, Bruno Busco wrote:
>>>
>>>> uhao!
>>>> That's great!
>>>>
>>>> Now I see what you meant by "sleeping giant" !
>>>>
>>>> -Bruno
>>>>
>>>>
>>>> 2009/11/25 Adam Heath <[hidden email]>:
>>>>>
>>>>> http://www.brainfood.com/ofbizbackend
>>>>>
>>>
>>>
>>
>

[Jacques Le Roux]

First, I  must say that maybe my view is biased because I have no time to look at git and I'm a bit jealous :/
My point was that it allows you to work a long time alone on a (possibly large) task.
And even if you break it after in several svn commits it's still a lot of commit to review in a single shoot.
I agree it's easier than a large svn commit though.
I understand that having a big work to do it's certainly better to use git.
The only point which concern me is that needs, at least, some collaboration/exchanges before diving in lonesome work.
Maybe practice will show how to do it better.
But as I said I'm still far from being ready to switch from svn to git.

Hope I have passed my feeling

Cheers

Jacques

From: "Scott Gray" <[hidden email]>

> That's not how git is being used, it simply allows you to easily break  
> up a single task into multiple more logically separated commits, which  
> actually makes for easier reviews.
>
> It is possible to do what you are suggesting but I don't think that is  
> what is actually happening.
>
> Regards
> Scott
>
> On 11/12/2009, at 11:24 PM, Jacques Le Roux wrote:
>
>> I wonder if  the "sleeping giant" is not using Git and will flood us  
>> sooner or later.
>> That's one of the dark aspect of git usage. You are able to commit a  
>> lot in a single shoot, hard to review.
>> Nothing is perfect is this world
>>
>> Jacques
>>
>> From: "Bruno Busco" <[hidden email]>
>>> Hi,
>>> Any step from the "sleeping giant" ? ;-)
>>> -Bruno
>>> 2009/11/25 Tim Ruppert <[hidden email]>:
>>>> Right now sleeping giant means not yet committed to the project :)
>>>> Definitely looking for this look and feel to make it's way in  
>>>> there Erik -
>>>> thanks so much! I'm glad you've found the right avenue for that  
>>>> style.
>>>>
>>>> Cheers,
>>>> Ruppert
>>>>
>>>> On Nov 25, 2009, at 2:13 PM, Bruno Busco wrote:
>>>>
>>>>> uhao!
>>>>> That's great!
>>>>>
>>>>> Now I see what you meant by "sleeping giant" !
>>>>>
>>>>> -Bruno
>>>>>
>>>>>
>>>>> 2009/11/25 Adam Heath <[hidden email]>:
>>>>>>
>>>>>> http://www.brainfood.com/ofbizbackend
>>>>>>
>>>>
>>>>
>>>
>>
>
>

[Adam Heath-2]

Jacques Le Roux wrote:
> I wonder if  the "sleeping giant" is not using Git and will flood us
> sooner or later.
> That's one of the dark aspect of git usage. You are able to commit a lot
> in a single shoot, hard to review.
> Nothing is perfect is this world

He's a windows guy.  For all the website content and design work he
does, we do git for him on the server.

For code repositories, I tend to do small, incremental commits.  But
for customer content type sites, I do an everything commit, just get
it done, who cares style of work flow.

[Adam Heath-2]

Bruno Busco wrote:
> Hi,
> Any step from the "sleeping giant" ? ;-)

Erik is not subscribed to this list.  I'm forwarding this email to
him, please keep him and this list cc'd

[Adam Heath-2]

Jacques Le Roux wrote:

> First, I  must say that maybe my view is biased because I have no time
> to look at git and I'm a bit jealous :/
> My point was that it allows you to work a long time alone on a (possibly
> large) task.
> And even if you break it after in several svn commits it's still a lot
> of commit to review in a single shoot. I agree it's easier than a large
> svn commit though. I understand that having a big work to do it's
> certainly better to use git. The only point which concern me is that
> needs, at least, some collaboration/exchanges before diving in lonesome
> work.
> Maybe practice will show how to do it better. But as I said I'm still
> far from being ready to switch from svn to git.
> Hope I have passed my feeling

Git also allows you to publish your local cloned repository, *before*
you commit it back upstream into svn, so people can comment on it
earlier.  You can then rewrite your local history, taking into
consideration all suggestions, and when it's finally right, the final
commit to svn is clean and has no cruft.

Git has plugins to commit an entire new feature as a series of patches
in jira.  I haven't yet used this plugin tho.

[Jacques Le Roux]

Thanks Adam,

Yes, you already explained that and I have still to learn/practice.
I think I will not be able to before some time

Jacques

From: "Adam Heath" <[hidden email]>

> Jacques Le Roux wrote:
>> First, I  must say that maybe my view is biased because I have no time
>> to look at git and I'm a bit jealous :/
>> My point was that it allows you to work a long time alone on a (possibly
>> large) task.
>> And even if you break it after in several svn commits it's still a lot
>> of commit to review in a single shoot. I agree it's easier than a large
>> svn commit though. I understand that having a big work to do it's
>> certainly better to use git. The only point which concern me is that
>> needs, at least, some collaboration/exchanges before diving in lonesome
>> work.
>> Maybe practice will show how to do it better. But as I said I'm still
>> far from being ready to switch from svn to git.
>> Hope I have passed my feeling
>
> Git also allows you to publish your local cloned repository, *before*
> you commit it back upstream into svn, so people can comment on it
> earlier.  You can then rewrite your local history, taking into
> consideration all suggestions, and when it's finally right, the final
> commit to svn is clean and has no cruft.
>
> Git has plugins to commit an entire new feature as a series of patches
> in jira.  I haven't yet used this plugin tho.
>

[Bruno Busco]

Erik,
I am going to propose (again) on the ML to switch the default OFBiz
theme to the droppingcrumbs.
Of course your rich version would be much better.
Anything to be committed? ;-)

-Bruno

2009/12/11 Jacques Le Roux <[hidden email]>:

> Thanks Adam,
>
> Yes, you already explained that and I have still to learn/practice. I think
> I will not be able to before some time
>
> Jacques
>
> From: "Adam Heath" <[hidden email]>
>>
>> Jacques Le Roux wrote:
>>>
>>> First, I  must say that maybe my view is biased because I have no time
>>> to look at git and I'm a bit jealous :/
>>> My point was that it allows you to work a long time alone on a (possibly
>>> large) task.
>>> And even if you break it after in several svn commits it's still a lot
>>> of commit to review in a single shoot. I agree it's easier than a large
>>> svn commit though. I understand that having a big work to do it's
>>> certainly better to use git. The only point which concern me is that
>>> needs, at least, some collaboration/exchanges before diving in lonesome
>>> work.
>>> Maybe practice will show how to do it better. But as I said I'm still
>>> far from being ready to switch from svn to git.
>>> Hope I have passed my feeling
>>
>> Git also allows you to publish your local cloned repository, *before*
>> you commit it back upstream into svn, so people can comment on it
>> earlier.  You can then rewrite your local history, taking into
>> consideration all suggestions, and when it's finally right, the final
>> commit to svn is clean and has no cruft.
>>
>> Git has plugins to commit an entire new feature as a series of patches
>> in jira.  I haven't yet used this plugin tho.
>>
>
>