You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Rodent of Unusual Size <Ke...@Golux.Com> on 2003/09/22 15:07:28 UTC
css again
argh. i'm starting to get torqued at forrest for being such a maze
of twisty little passages..
i want to make some changes to the page.css for a site, but nothing i
change in the skins/css/page.css file gets propagated to the
build/site/skin/page.css file. in fact, i can't figure out how
that gets created; it has stuff in it that only appears in a
generated file in the tmp/ tree, with which it's identical -- but
how the tmp/ file gets created i have no clew.
--
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
"Millennium hand and shrimp!"
Re: css again
Posted by Jeff Turner <je...@apache.org>.
On Mon, Sep 22, 2003 at 09:07:28AM -0400, Rodent of Unusual Size wrote:
> argh. i'm starting to get torqued at forrest for being such a maze
> of twisty little passages..
>
> i want to make some changes to the page.css for a site, but nothing i
> change in the skins/css/page.css file gets propagated to the
> build/site/skin/page.css file. in fact, i can't figure out how
> that gets created; it has stuff in it that only appears in a
> generated file in the tmp/ tree, with which it's identical -- but
> how the tmp/ file gets created i have no clew.
Which skin is your site using (specified in forrest.properties)? Each
skin has a separate .css file.
Is the .css the only thing you want to modify, or do you need to tinker
with the HTML (adding class nodes or whatever)?
You can override the .css from your chosen skin quite easily. Say you're
using the forrest-site skin. The default .css is located in
src/resources/skins/forrest-site/css/page.css. To override that, copy it
to $PROJECT/src/documentation/skins/forrest-site/css/page.css and make
your changes there. Any files from the skin can be overridden in this
way.
If you want to make larger HTML modifications, then defining a completely
new skin may be easier:
http://xml.apache.org/forrest/your-project.html#new_skin
The build/tmp/context/ directory is generated at runtime, and contains
the site's contents reorganized in a standard format expected by the
servlet 2.x spec (WEB-INF/* directory) and Forrest's sitemap (skin in
skins/...).
--Jeff
> --
> #ken P-)}
>
> Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
> Author, developer, opinionist http://Apache-Server.Com/
>
> "Millennium hand and shrimp!"
>
>
Re: css again
Posted by David Crossley <cr...@indexgeo.com.au>.
Rodent of Unusual Size wrote:
> Antonio Gallardo wrote:
> >
> > I noted this bug before. For a workaround, remove all the
> > build directory and generate again.
>
> um, which parts of the build tree? some of the source files are
> under build/, so i can't just get rid of that. build/tmp/ and
> build/site/ maybe?
Er, i am not sure what you mean by "source files". Unless, you
have manually added stuff to ./build for some reason, then
you will be safe to do 'forrest clean' (or just 'rm -rf ./build')
and start again with 'forrest'.
Sure forrest does copy some source files into the build space
and i know that some projects add extra stuff in there via their
build.xml (e.g. xml-commons, cocoon) so that forrest can process it.
The only situation where you would need to worry about ./build/*
is if you use 'forrest run' and edit stuff in build/webapps then you
will need to copy the modified source back as Antonio described.
--David
Re: css again
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Rodent of Unusual Size dijo:
> Antonio Gallardo wrote:
>>
>> Before removing the build directory, type:
>>
>> "forrest backcopy"
>>
>> Then try to generate} again
>
> /me swears violently
lol :-D
>
> i'm getting ready to ditch forrest altogether because it is
> (imho) such a spaghetti directory of poorly-documented
> interdependencies.. }-(
Don't be cruel. We are trying to do our most effort here. :)
>
> doing that resulted in some errors about 'cacheable' and
> 'pipeline' now being illegal in a couple of places.
Seriously, If this did not work. You can still take your backup copy
(still don't remove it!) and try to copy just the changed files from
build/webapp to src.
I thought the backcopy option still works well. I used it before.
BTW, are you using the CVS version?
Best Regards,
Antonio Gallardo
Re: css again
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Antonio Gallardo wrote:
>
> Before removing the build directory, type:
>
> "forrest backcopy"
>
> Then try to generate} again
/me swears violently
i'm getting ready to ditch forrest altogether because it is
(imho) such a spaghetti directory of poorly-documented
interdependencies.. }-(
doing that resulted in some errors about 'cacheable' and
'pipeline' now being illegal in a couple of places.
--
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
"Millennium hand and shrimp!"
Re: css again
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Rodent of Unusual Size dijo:
> Antonio Gallardo wrote:
>>
>> I noted this bug before. For a workaround, remove all the build
>> directory and generate again.
>
> um, which parts of the build tree? some of the source files are
> under build/, so i can't just get rid of that. build/tmp/ and
> build/site/ maybe?
Forrest has an option:
backcopy -> If anything has been edited in build/webapps, copies them back
to src/documentation
But I recommend to make a backup if things does wrong. Just to have a
second option. I used this option before and worked well.
Before removing the build directory, type:
"forrest backcopy"
Then try to generate} again
Best Regards,
Antonio Gallardo.
Re: css again
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Antonio Gallardo wrote:
>
> I noted this bug before. For a workaround, remove all the build directory
> and generate again.
um, which parts of the build tree? some of the source files are
under build/, so i can't just get rid of that. build/tmp/ and
build/site/ maybe?
--
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
"Millennium hand and shrimp!"
Re: css again
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Rodent of Unusual Size dijo:
> argh. i'm starting to get torqued at forrest for being such a maze of
> twisty little passages..
>
> i want to make some changes to the page.css for a site, but nothing i
> change in the skins/css/page.css file gets propagated to the
> build/site/skin/page.css file. in fact, i can't figure out how
> that gets created; it has stuff in it that only appears in a
> generated file in the tmp/ tree, with which it's identical -- but
> how the tmp/ file gets created i have no clew.
Hi:
I noted this bug before. For a workaround, remove all the build directory
and generate again.
Antonio Gallardo.