apply changes in XSLs after revision update (was: How to create a patch for forrest)

[Johannes Schaefer <jo...@uidesign.de>]

Hi!

We are using the forrest development version
and getting it via svn. To stay up-to-date
we get a new copy now and then. After that
we copy our "documentation" tree into the
forrest-dir for the new revision. So far so
good.

We changed some forrest-core styleguides to
our needs (and tastes). Now, after each
update we have to apply these changes to the
new revision.

Is there an easier way to do this?

Cheers
Johannes


Johannes Schaefer wrote:

 >> Hi!
 >> I was talking "user", i.e. as user
 >> we modified some xsl-files. I want to
 >> step to the next revision (sic! 30994)
 >> and apply our changes there.
 >>
 >> I can't do an update, since I'm working
 >> on my xdocs:
 >>    D:\forrest>svn update
 >>    svn: Working copy 'src/documentation/content/xdocs' not locked
 >>
 >> So, we get a fresh revision and want
 >> our changes applied there.


Well i am really not sure what you are talking about.
Please provide more information. The first thing that
we need to know is how did you obtain your copy of Forrest?

-- David Crossley


-- 
User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg
Fon +49 (0)7141 377 000 * Fax  +49 (0)7141 377 00-99
Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * 
D-81825 München
www.uidesign.de

Re: apply changes in XSLs after revision update (was: How to create a patch for forrest)

[Johannes Schaefer <jo...@uidesign.de>]

David Crossley wrote:
> Johannes Schaefer wrote:
> 
>>We are using the forrest development version
>>and getting it via svn. To stay up-to-date
>>we get a new copy now and then.
> 
> 
> Good. However you should do that as often as possible.
> 
> 
>>After that
>>we copy our "documentation" tree into the
>>forrest-dir for the new revision. So far so
>>good.
> 
> 
> No, not good. I do not understand what you are doing.
> Why are you copying stuff into the Forrest source tree?


Sorry to you all ... stupid me.
I'm quite sure that these problems will
go away now that I've started my project
with 'forrest seed' and NOT using the
forrest source tree. Entschuldigung.
Excuse me. Desculpem. Scusi. Isvenite.
Perdon. Excuse moi.

Johannes



> 
> If you are building your own documentation then it
> should be completely outside of Forrest, e.g. over
> in /home/you/my-docs/ do a 'forrest seed' and add your
> new documentation in there.
> 
> 
>>We changed some forrest-core styleguides to
>>our needs (and tastes). Now, after each
>>update we have to apply these changes to the
>>new revision.
> 
> 
> Why can't you do it how i described in the last thread?
> When you do 'svn update', if there were any source changes
> to the files that you have modified, then those changes
> will get safely merged with yours. If there are conflicts
> because someone changed the exact same portion of the file
> that you changed, then you will be warned and you will
> need to fix them.
> 



-- 
User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg
Fon +49 (0)7141 377 000 * Fax  +49 (0)7141 377 00-99
Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * 
D-81825 München
www.uidesign.de

Buch "User Interface Tuning" von Joachim Machate & Michael Burmester
www.user-interface-tuning.de

Attraktivität von interaktiven Produkten messen mit
www.attrakdiff.de

Re: apply changes in XSLs after revision update (was: How to create a patch for forrest)

[David Crossley <cr...@apache.org>]

Johannes Schaefer wrote:
> We are using the forrest development version
> and getting it via svn. To stay up-to-date
> we get a new copy now and then.

Good. However you should do that as often as possible.

> After that
> we copy our "documentation" tree into the
> forrest-dir for the new revision. So far so
> good.

No, not good. I do not understand what you are doing.
Why are you copying stuff into the Forrest source tree?

If you are building your own documentation then it
should be completely outside of Forrest, e.g. over
in /home/you/my-docs/ do a 'forrest seed' and add your
new documentation in there.

> We changed some forrest-core styleguides to
> our needs (and tastes). Now, after each
> update we have to apply these changes to the
> new revision.

Why can't you do it how i described in the last thread?
When you do 'svn update', if there were any source changes
to the files that you have modified, then those changes
will get safely merged with yours. If there are conflicts
because someone changed the exact same portion of the file
that you changed, then you will be warned and you will
need to fix them.

-- 
David Crossley

Re: apply changes in XSLs after revision update (was: How to create a patch for forrest)

[Thorsten Scherler <th...@apache.org>]

Hi Johannes,

woh, I may missunderstood you but ...

Johannes Schaefer wrote:
> Hi!
> 
> We are using the forrest development version
> and getting it via svn. To stay up-to-date
> we get a new copy now and then.

I hope you are just using /svn update/.

  After that
> we copy our "documentation" tree into the
> forrest-dir for the new revision. So far so
> good.

Why are you doing that?
Didn't you have your own seed?
I mean there is no need to copy your documentation into forrest if you 
start with a /forrest seed/!

> 
> We changed some forrest-core styleguides to
> our needs (and tastes). Now, after each
> update we have to apply these changes to the
> new revision.
> 

What files are they? If you just change some skin files e.g. book-tab 
then just copy the book-tab skin and rename it! In your 
forrest.properties just change project.skin to the new name. This way 
you do not have to aplly your changes.

HTH
thorsten

> Is there an easier way to do this?
> 
> Cheers
> Johannes
> 
> 
> Johannes Schaefer wrote:
> 
>  >> Hi!
>  >> I was talking "user", i.e. as user
>  >> we modified some xsl-files. I want to
>  >> step to the next revision (sic! 30994)
>  >> and apply our changes there.
>  >>
>  >> I can't do an update, since I'm working
>  >> on my xdocs:
>  >>    D:\forrest>svn update
>  >>    svn: Working copy 'src/documentation/content/xdocs' not locked
>  >>
>  >> So, we get a fresh revision and want
>  >> our changes applied there.
> 
> 
> Well i am really not sure what you are talking about.
> Please provide more information. The first thing that
> we need to know is how did you obtain your copy of Forrest?
> 
> -- David Crossley
> 
> 

RE: unsubscribing from forrest-user

[Nat Guy <na...@bigcode.com>]

Thank you David.

Yes I tried every method presented to me - all unsubscribing from this same
account - and always telling me that the account doesn't exist even though I
continue to receive the forrest user messages. I also sent an unsub. message
to what looked to be described as a human manning this list but no changes
have occurred.

Seems there is a hiccup in this automated de-lister...? Certainly not a
seemless experience.

Thank you for any help,
Nat

-----Original Message-----
From: David Crossley [mailto:crossley@apache.org]
Sent: Wednesday, August 04, 2004 6:23 PM
To: user@forrest.apache.org
Cc: Nat Guy
Subject: unsubscribing from forrest-user


Nat Guy wrote:
> Is anyone at the helm of this email list? Is it truly impossible to get
off?
> I have tried every automated and non-automated solution and I can't get
off
> this ride. I am now forced to email the group?

Are you sending the unsubscribe email from the same email address
as that from which you originally subscribed. If that doesn't work
then email the list again and we will try other methods.

--
David Crossley

unsubscribing from forrest-user

[David Crossley <cr...@apache.org>]

Nat Guy wrote:
> Is anyone at the helm of this email list? Is it truly impossible to get off?
> I have tried every automated and non-automated solution and I can't get off
> this ride. I am now forced to email the group?

Are you sending the unsubscribe email from the same email address
as that from which you originally subscribed. If that doesn't work
then email the list again and we will try other methods.

-- 
David Crossley

RE: apply changes in XSLs after revision update (was: How to create a patch for forrest)

[Nat Guy <na...@bigcode.com>]

Is anyone at the helm of this email list? Is it truly impossible to get off?
I have tried every automated and non-automated solution and I can't get off
this ride. I am now forced to email the group?

Thanks,
Nat