You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Linda Rose <li...@cox.net> on 2004/11/04 00:33:19 UTC
modifying the css for forrest
Hi,
I've been very impressed by the example sites that have been created using
Forrest. I want to customize the look of mine. Can I modify
my-project\build\site\skin\basic.css?
Thanks,
Linda
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Linda Rose
Webmaster, Alexandria Digital Library Project
http://www.alexandria.ucsb.edu
lrose@alexandria.ucsb.edu
805 893-8902
Re: modifying the css for forrest
Posted by Thorsten Scherler <th...@apache.org>.
Thorsten Scherler escribió:
> Linda Rose escribió:
>
>> ----- Original Message ----- snip
>>
>>>
>>> You have to change the padding attribute.
>>> http://www.w3schools.com/css/css_padding.asp can be a start.
>>>
>>> in skinconf.xml
>>> <extra-css>
>>> #menu .menuitem {
>>> padding: 0px 0px 2px 12px;
>>> background-image: url('images/page.gif');
>>> background-repeat: no-repeat;
>>> background-position: center left;
>>> font-weight : normal;
>>> margin-left: 10px;
>>> }
>>> </extra-css>
>>> --
>>> thorsten
>>
>>
>> --------------------------------------------------------------------------
>> Hi Thorsten,
>>
>> I added:
>> <extra-css>
>> #menu .menuitem {
>> padding: 0px 0px 10px 12px;
>> background-image: url('images/page.gif');
>> background-repeat: no-repeat;
>> background-position: center left;
>> font-weight : normal;
>> margin-left: 10px;
>> }
>>
>> and set the screen.css back to the original value but my spacing
>> disappeared. The extra-css doesn't seem to have an effect.
>>
>> Linda
>>
>>
>
> Hi Linda,
>
> I tried with
> #menu .menuitem {
> padding: 10px 0px 10px 12px;
> background-image: url('images/page.gif');
> background-repeat: no-repeat;
> background-position: center left;
> font-weight : normal;
> margin-left: 10px;
> }
> and for me that is doing the trip.
/trip/ /trick/
sorry!
--
thorsten
"Together we stand, divided we fall"
Hey you (Pink Floyd)
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
----- Original Message -----
snip
> Hi Linda,
>
> I tried with
> #menu .menuitem {
> padding: 10px 0px 10px 12px;
> background-image: url('images/page.gif');
> background-repeat: no-repeat;
> background-position: center left;
> font-weight : normal;
> margin-left: 10px;
> }
> and for me that is doing the trip.
>
> Did you tried with /forrest/ or with /forrest run/?
>
> --
> thorsten
>
I used forrest. Should I use forrest run?
Linda
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
Yes, I meant skinconf.xml, sorry.
----- Original Message -----
From: "Ross Gardler" <rg...@apache.org>
To: <us...@forrest.apache.org>
Sent: Friday, November 05, 2004 1:46 PM
Subject: Re: modifying the css for forrest
> Linda Rose wrote:
>> Any ideas on why this css is not applied for me when I put it in my
>> skin.xml file?
>
> Do you mean skinconf.xml (you should).
>
> Ross
>
Re: modifying the css for forrest
Posted by Ross Gardler <rg...@apache.org>.
Linda Rose wrote:
> Any ideas on why this css is not applied for me when I put it in my
> skin.xml file?
Do you mean skinconf.xml (you should).
Ross
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
Oh my Gosh, I had a typo! 10x instead of 10px. I'm so sorry. But thanks for
showing me how to troubleshoot.
Linda
----- Original Message -----
From: "Ross Gardler" <rg...@apache.org>
To: <us...@forrest.apache.org>
Sent: Friday, November 05, 2004 2:30 PM
Subject: Re: modifying the css for forrest
Linda Rose wrote:
> Any ideas on why this css is not applied for me when I put it in my
> skin.xml file?
For test purposes:
- do "forrest run"
- point your browser at http://localhost:8888
- does your CSS have any affect?
- point your browser at http://localhost:8888/skin/profile.css
- can you see your #menu .menuitem addition in that file?
Ross
>
> Thanks,
>
> Linda
>
>
> ----- Original Message ----- From: "Thorsten Scherler"
> <th...@apache.org>
> To: <us...@forrest.apache.org>
> Sent: Thursday, November 04, 2004 11:55 PM
> Subject: Re: modifying the css for forrest
>
>
>> Linda Rose escribió:
>>
>>> ----- Original Message ----- snip
>>>
>>>>
>>>> You have to change the padding attribute.
>>>> http://www.w3schools.com/css/css_padding.asp can be a start.
>>>>
>>>> in skinconf.xml
>>>> <extra-css>
>>>> #menu .menuitem {
>>>> padding: 0px 0px 2px 12px;
>>>> background-image: url('images/page.gif');
>>>> background-repeat: no-repeat;
>>>> background-position: center left;
>>>> font-weight : normal;
>>>> margin-left: 10px;
>>>> }
>>>> </extra-css>
>>>> --
>>>> thorsten
>>>
>>>
>>> --------------------------------------------------------------------------
>>>
>>> Hi Thorsten,
>>>
>>> I added:
>>> <extra-css>
>>> #menu .menuitem {
>>> padding: 0px 0px 10px 12px;
>>> background-image: url('images/page.gif');
>>> background-repeat: no-repeat;
>>> background-position: center left;
>>> font-weight : normal;
>>> margin-left: 10px;
>>> }
>>>
>>> and set the screen.css back to the original value but my spacing
>>> disappeared. The extra-css doesn't seem to have an effect.
>>>
>>> Linda
>>>
>>>
>>
>> Hi Linda,
>>
>> I tried with
>> #menu .menuitem {
>> padding: 10px 0px 10px 12px;
>> background-image: url('images/page.gif');
>> background-repeat: no-repeat;
>> background-position: center left;
>> font-weight : normal;
>> margin-left: 10px;
>> }
>> and for me that is doing the trip.
>>
>> Did you tried with /forrest/ or with /forrest run/?
>>
>> --
>> thorsten
>>
>> "Together we stand, divided we fall"
>> Hey you (Pink Floyd)
>>
>>
>
>
>
>
Re: modifying the css for forrest
Posted by Ross Gardler <rg...@apache.org>.
Linda Rose wrote:
> Any ideas on why this css is not applied for me when I put it in my
> skin.xml file?
For test purposes:
- do "forrest run"
- point your browser at http://localhost:8888
- does your CSS have any affect?
- point your browser at http://localhost:8888/skin/profile.css
- can you see your #menu .menuitem addition in that file?
Ross
>
> Thanks,
>
> Linda
>
>
> ----- Original Message ----- From: "Thorsten Scherler"
> <th...@apache.org>
> To: <us...@forrest.apache.org>
> Sent: Thursday, November 04, 2004 11:55 PM
> Subject: Re: modifying the css for forrest
>
>
>> Linda Rose escribió:
>>
>>> ----- Original Message ----- snip
>>>
>>>>
>>>> You have to change the padding attribute.
>>>> http://www.w3schools.com/css/css_padding.asp can be a start.
>>>>
>>>> in skinconf.xml
>>>> <extra-css>
>>>> #menu .menuitem {
>>>> padding: 0px 0px 2px 12px;
>>>> background-image: url('images/page.gif');
>>>> background-repeat: no-repeat;
>>>> background-position: center left;
>>>> font-weight : normal;
>>>> margin-left: 10px;
>>>> }
>>>> </extra-css>
>>>> --
>>>> thorsten
>>>
>>>
>>> --------------------------------------------------------------------------
>>>
>>> Hi Thorsten,
>>>
>>> I added:
>>> <extra-css>
>>> #menu .menuitem {
>>> padding: 0px 0px 10px 12px;
>>> background-image: url('images/page.gif');
>>> background-repeat: no-repeat;
>>> background-position: center left;
>>> font-weight : normal;
>>> margin-left: 10px;
>>> }
>>>
>>> and set the screen.css back to the original value but my spacing
>>> disappeared. The extra-css doesn't seem to have an effect.
>>>
>>> Linda
>>>
>>>
>>
>> Hi Linda,
>>
>> I tried with
>> #menu .menuitem {
>> padding: 10px 0px 10px 12px;
>> background-image: url('images/page.gif');
>> background-repeat: no-repeat;
>> background-position: center left;
>> font-weight : normal;
>> margin-left: 10px;
>> }
>> and for me that is doing the trip.
>>
>> Did you tried with /forrest/ or with /forrest run/?
>>
>> --
>> thorsten
>>
>> "Together we stand, divided we fall"
>> Hey you (Pink Floyd)
>>
>>
>
>
>
>
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
Any ideas on why this css is not applied for me when I put it in my skin.xml
file?
Thanks,
Linda
----- Original Message -----
From: "Thorsten Scherler" <th...@apache.org>
To: <us...@forrest.apache.org>
Sent: Thursday, November 04, 2004 11:55 PM
Subject: Re: modifying the css for forrest
> Linda Rose escribió:
>> ----- Original Message ----- snip
>>
>>>
>>> You have to change the padding attribute.
>>> http://www.w3schools.com/css/css_padding.asp can be a start.
>>>
>>> in skinconf.xml
>>> <extra-css>
>>> #menu .menuitem {
>>> padding: 0px 0px 2px 12px;
>>> background-image: url('images/page.gif');
>>> background-repeat: no-repeat;
>>> background-position: center left;
>>> font-weight : normal;
>>> margin-left: 10px;
>>> }
>>> </extra-css>
>>> --
>>> thorsten
>>
>> --------------------------------------------------------------------------
>> Hi Thorsten,
>>
>> I added:
>> <extra-css>
>> #menu .menuitem {
>> padding: 0px 0px 10px 12px;
>> background-image: url('images/page.gif');
>> background-repeat: no-repeat;
>> background-position: center left;
>> font-weight : normal;
>> margin-left: 10px;
>> }
>>
>> and set the screen.css back to the original value but my spacing
>> disappeared. The extra-css doesn't seem to have an effect.
>>
>> Linda
>>
>>
>
> Hi Linda,
>
> I tried with
> #menu .menuitem {
> padding: 10px 0px 10px 12px;
> background-image: url('images/page.gif');
> background-repeat: no-repeat;
> background-position: center left;
> font-weight : normal;
> margin-left: 10px;
> }
> and for me that is doing the trip.
>
> Did you tried with /forrest/ or with /forrest run/?
>
> --
> thorsten
>
> "Together we stand, divided we fall"
> Hey you (Pink Floyd)
>
>
Re: modifying the css for forrest
Posted by Thorsten Scherler <th...@apache.org>.
Linda Rose escribió:
> ----- Original Message ----- snip
>
>>
>> You have to change the padding attribute.
>> http://www.w3schools.com/css/css_padding.asp can be a start.
>>
>> in skinconf.xml
>> <extra-css>
>> #menu .menuitem {
>> padding: 0px 0px 2px 12px;
>> background-image: url('images/page.gif');
>> background-repeat: no-repeat;
>> background-position: center left;
>> font-weight : normal;
>> margin-left: 10px;
>> }
>> </extra-css>
>> --
>> thorsten
>
> --------------------------------------------------------------------------
> Hi Thorsten,
>
> I added:
> <extra-css>
> #menu .menuitem {
> padding: 0px 0px 10px 12px;
> background-image: url('images/page.gif');
> background-repeat: no-repeat;
> background-position: center left;
> font-weight : normal;
> margin-left: 10px;
> }
>
> and set the screen.css back to the original value but my spacing
> disappeared. The extra-css doesn't seem to have an effect.
>
> Linda
>
>
Hi Linda,
I tried with
#menu .menuitem {
padding: 10px 0px 10px 12px;
background-image: url('images/page.gif');
background-repeat: no-repeat;
background-position: center left;
font-weight : normal;
margin-left: 10px;
}
and for me that is doing the trip.
Did you tried with /forrest/ or with /forrest run/?
--
thorsten
"Together we stand, divided we fall"
Hey you (Pink Floyd)
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
----- Original Message -----
snip
>
> You have to change the padding attribute.
> http://www.w3schools.com/css/css_padding.asp can be a start.
>
> in skinconf.xml
> <extra-css>
> #menu .menuitem {
> padding: 0px 0px 2px 12px;
> background-image: url('images/page.gif');
> background-repeat: no-repeat;
> background-position: center left;
> font-weight : normal;
> margin-left: 10px;
> }
> </extra-css>
> --
> thorsten
--------------------------------------------------------------------------
Hi Thorsten,
I added:
<extra-css>
#menu .menuitem {
padding: 0px 0px 10px 12px;
background-image: url('images/page.gif');
background-repeat: no-repeat;
background-position: center left;
font-weight : normal;
margin-left: 10px;
}
and set the screen.css back to the original value but my spacing
disappeared. The extra-css doesn't seem to have an effect.
Linda
Re: modifying the css for forrest
Posted by Thorsten Scherler <th...@apache.org>.
Ross Gardler escribió:
>
>
> Linda Rose wrote:
>
>>
>> ----- Original Message -----
>>
>>> Yeah, but IMO Linda *should* firstly use <extra-css/> in the
>>> skinconf.xml.
>>>
>>> Linda, there you can place your personal css-elements.
>>> Just open a your page in a html-editor and look for the elements name
>>> of the things you want to change.
>>>
>>>> If you do find you want to do things that can't be done in
>>>> skinconf.xml please put a feature request on the issue tracker. Some
>>>> of our devs are designing an improvement to the skin system at the
>>>> moment and your input would be very helpful.
>>>>
>>>> >
>>>> Ross
>>>>
>>>
>>> Yeah, I will install all features of *pelt* into *leather*.
>>> If I have the files open I can implement new features (if easy to
>>> implement) on the fly. ;-)
>>>
>>> What do you actually want to change?
>>>
>>> --
>>> thorsten
>>
>>
>>
>> I want to add space below div.menuitem, see
>> http://www.alexandria.ucsb.edu/adl/docs_software/site/devguide/Intro.html
>> and look at the left-hand margin. I added space below. Can I place
>> that in skinconf.xml?
>
>
> Yep. this is purely a CSS change and therefore can be put into the
> <extra-css> tag of skinconf.xml - anything you put in here will override
> anything in the skins css.
>
> Ross
>
You have to change the padding attribute.
http://www.w3schools.com/css/css_padding.asp can be a start.
in skinconf.xml
<extra-css>
#menu .menuitem {
padding: 0px 0px 2px 12px;
background-image: url('images/page.gif');
background-repeat: no-repeat;
background-position: center left;
font-weight : normal;
margin-left: 10px;
}
</extra-css>
--
thorsten
"Together we stand, divided we fall"
Hey you (Pink Floyd)
Re: modifying the css for forrest
Posted by Ross Gardler <rg...@apache.org>.
Linda Rose wrote:
>
> ----- Original Message -----
>
>> Yeah, but IMO Linda *should* firstly use <extra-css/> in the
>> skinconf.xml.
>>
>> Linda, there you can place your personal css-elements.
>> Just open a your page in a html-editor and look for the elements name
>> of the things you want to change.
>>
>>> If you do find you want to do things that can't be done in
>>> skinconf.xml please put a feature request on the issue tracker. Some
>>> of our devs are designing an improvement to the skin system at the
>>> moment and your input would be very helpful.
>>>
>>> >
>>> Ross
>>>
>>
>> Yeah, I will install all features of *pelt* into *leather*.
>> If I have the files open I can implement new features (if easy to
>> implement) on the fly. ;-)
>>
>> What do you actually want to change?
>>
>> --
>> thorsten
>
>
> I want to add space below div.menuitem, see
> http://www.alexandria.ucsb.edu/adl/docs_software/site/devguide/Intro.html
> and look at the left-hand margin. I added space below. Can I place that
> in skinconf.xml?
Yep. this is purely a CSS change and therefore can be put into the
<extra-css> tag of skinconf.xml - anything you put in here will override
anything in the skins css.
Ross
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
----- Original Message -----
> Yeah, but IMO Linda *should* firstly use <extra-css/> in the skinconf.xml.
>
> Linda, there you can place your personal css-elements.
> Just open a your page in a html-editor and look for the elements name of
> the things you want to change.
>
>> If you do find you want to do things that can't be done in skinconf.xml
>> please put a feature request on the issue tracker. Some of our devs are
>> designing an improvement to the skin system at the moment and your input
>> would be very helpful.
>>
>> >
>> Ross
>>
>
> Yeah, I will install all features of *pelt* into *leather*.
> If I have the files open I can implement new features (if easy to
> implement) on the fly. ;-)
>
> What do you actually want to change?
>
> --
> thorsten
I want to add space below div.menuitem, see
http://www.alexandria.ucsb.edu/adl/docs_software/site/devguide/Intro.html
and look at the left-hand margin. I added space below. Can I place that in
skinconf.xml?
Linda
Re: modifying the css for forrest
Posted by Thorsten Scherler <th...@apache.org>.
Ross Gardler escribió:
> Linda Rose wrote:
>
>> ----- Original Message ----- From: "Ross Gardler" <rg...@apache.org>
>>
>>> You are /almost/ getting the hang of it. You found the right file,
>>> but you are editing the wrong copy - this one will get overwritten
>>> whenever you upgrade Forrest.
>>>
>>> See my other reply to Clays post with details of where you can safely
>>> configure your look and feel.
>>>
>>> Ross
>>>
>> Hi Ross,
>>
>> As per the instructions, I copied the pelt skins to
>> myproject/src/documentation/skins/mypelt and modified the line in
>> forrest.properties project.skin=src/documentation/skins/mypelt.
>
>
> That should be just "mypelt".
>
> Note, if you are only changing the CSS then you do not really need to do
> this, it is only if you wnat to do some configuration that cannot be
> done in skinconf.xml. If you do go this route you should also copy the
> common skin accross to your skins directory, this prevents version
> conflicts with later versions of Forrest.
>
Yeah, but IMO Linda *should* firstly use <extra-css/> in the skinconf.xml.
Linda, there you can place your personal css-elements.
Just open a your page in a html-editor and look for the elements name of
the things you want to change.
> If you do find you want to do things that can't be done in skinconf.xml
> please put a feature request on the issue tracker. Some of our devs are
> designing an improvement to the skin system at the moment and your input
> would be very helpful.
>
> >
> Ross
>
Yeah, I will install all features of *pelt* into *leather*.
If I have the files open I can implement new features (if easy to
implement) on the fly. ;-)
What do you actually want to change?
--
thorsten
"Together we stand, divided we fall"
Hey you (Pink Floyd)
Re: Improving documentation - you can help!
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> Ross Gardler said:
<snip/>
>>That being said, our docs *do* need improvement. The problem is that the
>>people working on the code are doing so on a voluntary basis, we don't
>>get paid (at least not directly) for this work, and we certainly don't
>>get paid to write documentation. It is a common problem for Open source
>>projects, but you, as users, can help (read on).
>
>
> And for that, I thank you. I apologize for the tone of my message (I guess
> it's never really a good idea to prefix something with <rant> ;-)). I
> guess I could just continue along <quietly/> contributing little PATCHes
> here and there (as I've started doing over the last few days...).
Yes, you have started contributing patches (actually you have been doing
for a long time, and you have also been active on the lists for a long
time - also a contribution to Forrest). I simply replied in order to say
that others can do it too.
Please *don't* continue quietly, by saying what needs to be done you
make us *all* aware. People often want to help but don't know how. Your
rant pointed out one way *everyone* can help.
Ross
Re: Improving documentation - you can help!
Posted by Clay Leeds <cl...@medata.com>.
Ross Gardler said:
> Hmmmm...
>
> I'm not sure you can call it a tiny assumption when the doc originally
> referenced says:
>
> "For example, copy forrest/src/core/context/skins/pelt to your project
> area at src/documentation/skins/my-fancy-skin and add
> project.skin=my-fancy-skin to forrest.properties"
>
> In this sentence, it clearly says what to put in the property (note the
> "project.skin=my-fancy-skin") on the last line.
D'oh! Thanks for pointing that out! Sorry for wasting more of your time.
> That being said, our docs *do* need improvement. The problem is that the
> people working on the code are doing so on a voluntary basis, we don't
> get paid (at least not directly) for this work, and we certainly don't
> get paid to write documentation. It is a common problem for Open source
> projects, but you, as users, can help (read on).
And for that, I thank you. I apologize for the tone of my message (I guess
it's never really a good idea to prefix something with <rant> ;-)). I
guess I could just continue along <quietly/> contributing little PATCHes
here and there (as I've started doing over the last few days...).
>> One of my goals is to improve FOPs documentation (and Forrest's as I
>> slog through the process of getting FOP's docs back online!) so that
>> newbies like myself don't have to deal with silly frustrations like
>> this. IMO, documentation should not skimp on examples. Rather, they
>> should almost go out of their way to be verbose.
>
> Speaking personally, I do not have the time to write extensive examples
> - my code *is* my example, unfortunatley this creates a particularly
> high barrier to entry, that's why I am spending the free time I have
> between contracts helping out here on the user list, as well as writing
> code improvements in the core of Forrest - work which I will eventually
> get paid for. So how can users, help?
>
> It would be really nice if people who get helped out on the user lists
> could help improve the project by clarifying things that confused them
> in the docs. As Clay says adding examples and notes from your experience
> can help a great deal.
>
> Contributing to a project like this one does not only mean writing code.
> Docs and assisting fellow users on this list are equally as valuable.
>
> To contribute your documentation enhancements edit the relevant files
> and commit a diff to the issue tracker (
> http://issues.cocoondev.org/secure/BrowseProject.jspa?id=10000 ). If you
> don't know how to create a diff see
> http://forrest.apache.org/contrib.html If you still can't prepare a diff
> (that document probably needs some improving too) then posting your
> notes/examples and an explanation of where they fit into the
> documentation to an issue is the next best thing.
>
> Every small contribution helps a great deal, please give back to the
> project when your personal schedule allows.
Thanks! I'll see what I can do to improve the docs where I find vagaries.
>> </rant>
>>
>> NOTE: The above rant wasn't directed 'at' Ross (or anyone in
>> particular). ;-)
>
> Neither was my response aimed at Clay (or anyone in particular) ;-)
>
> Ross
Again, I apologize for my tone and for wasting time.
--
Clay Leeds - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Improving documentation - you can help! (was Re: modifying the
css for forrest)
Posted by Ross Gardler <rg...@apache.org>.
Linda Rose wrote:
> I had tried it first as project.skin=mypelt and got an error message
> with that too. So I tried it with the path included. Sorry for any
> confusion.
No problem, we are here to help :-)
I'm not sure if you have got it working yet or not. If not then please
respond to the original mail as I changes the subject on this one to
reflect the fact it was dealing with Clay's comments on documentation.
Ross
Re: Improving documentation - you can help! (was Re: modifying the css for forrest)
Posted by Linda Rose <li...@cox.net>.
I had tried it first as project.skin=mypelt and got an error message with
that too. So I tried it with the path included. Sorry for any confusion.
----- Original Message -----
From: "Ross Gardler" <rg...@apache.org>
To: <us...@forrest.apache.org>
Sent: Thursday, November 04, 2004 1:50 PM
Subject: Improving documentation - you can help! (was Re: modifying the css
for forrest)
> Clay Leeds wrote:
>> On Nov 4, 2004, at 12:04 PM, Ross Gardler wrote:
>>
>>> Linda Rose wrote:
>
> <snip/>
>
> > > > As per the instructions, I copied the pelt skins to
> > > > myproject/src/documentation/skins/mypelt and modified the line in
> > > > forrest.properties project.skin=src/documentation/skins/mypelt.
> > >
> > > That should be just "mypelt".
> >
>> I'm pretty sure Ross meant that the line in forrest.properties should be
>> just:
>>
>> project.skin=mypelt
>
> Yes, that is what I meant
>
>>
>> <rant>
>> I get confused in the Forrest docs where assumptions are made by the
>> author, and I just don't get it. It's particularly frustrating, when I'm
>> close to a solution, but the amount of time to resolve a problem is
>> exacerbated by little assumptions like this
>
> Hmmmm...
>
> I'm not sure you can call it a tiny assumption when the doc originally
> referenced says:
>
> "For example, copy forrest/src/core/context/skins/pelt to your project
> area at src/documentation/skins/my-fancy-skin and add
> project.skin=my-fancy-skin to forrest.properties"
>
> In this sentence, it clearly says what to put in the property (note the
> "project.skin=my-fancy-skin") on the last line.
>
> That being said, our docs *do* need improvement. The problem is that the
> people working on the code are doing so on a voluntary basis, we don't get
> paid (at least not directly) for this work, and we certainly don't get
> paid to write documentation. It is a common problem for Open source
> projects, but you, as users, can help (read on).
>
>> One of my goals is to improve FOPs documentation (and Forrest's as I slog
>> through the process of getting FOP's docs back online!) so that newbies
>> like myself don't have to deal with silly frustrations like this. IMO,
>> documentation should not skimp on examples. Rather, they should almost go
>> out of their way to be verbose.
>
> Speaking personally, I do not have the time to write extensive examples -
> my code *is* my example, unfortunatley this creates a particularly high
> barrier to entry, that's why I am spending the free time I have between
> contracts helping out here on the user list, as well as writing code
> improvements in the core of Forrest - work which I will eventually get
> paid for. So how can users, help?
>
> It would be really nice if people who get helped out on the user lists
> could help improve the project by clarifying things that confused them in
> the docs. As Clay says adding examples and notes from your experience can
> help a great deal.
>
> Contributing to a project like this one does not only mean writing code.
> Docs and assisting fellow users on this list are equally as valuable.
>
> To contribute your documentation enhancements edit the relevant files and
> commit a diff to the issue tracker (
> http://issues.cocoondev.org/secure/BrowseProject.jspa?id=10000 ). If you
> don't know how to create a diff see http://forrest.apache.org/contrib.html
> If you still can't prepare a diff (that document probably needs some
> improving too) then posting your notes/examples and an explanation of
> where they fit into the documentation to an issue is the next best thing.
>
> Every small contribution helps a great deal, please give back to the
> project when your personal schedule allows.
>
>> </rant>
>>
>> NOTE: The above rant wasn't directed 'at' Ross (or anyone in particular).
>> ;-)
>
> Neither was my response aimed at Clay (or anyone in particular) ;-)
>
> Ross
>
Improving documentation - you can help! (was Re: modifying the css
for forrest)
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Nov 4, 2004, at 12:04 PM, Ross Gardler wrote:
>
>> Linda Rose wrote:
<snip/>
> > > As per the instructions, I copied the pelt skins to
> > > myproject/src/documentation/skins/mypelt and modified the line in
> > > forrest.properties project.skin=src/documentation/skins/mypelt.
> >
> > That should be just "mypelt".
>
> I'm pretty sure Ross meant that the line in forrest.properties should be
> just:
>
> project.skin=mypelt
Yes, that is what I meant
>
> <rant>
> I get confused in the Forrest docs where assumptions are made by the
> author, and I just don't get it. It's particularly frustrating, when I'm
> close to a solution, but the amount of time to resolve a problem is
> exacerbated by little assumptions like this
Hmmmm...
I'm not sure you can call it a tiny assumption when the doc originally
referenced says:
"For example, copy forrest/src/core/context/skins/pelt to your project
area at src/documentation/skins/my-fancy-skin and add
project.skin=my-fancy-skin to forrest.properties"
In this sentence, it clearly says what to put in the property (note the
"project.skin=my-fancy-skin") on the last line.
That being said, our docs *do* need improvement. The problem is that the
people working on the code are doing so on a voluntary basis, we don't
get paid (at least not directly) for this work, and we certainly don't
get paid to write documentation. It is a common problem for Open source
projects, but you, as users, can help (read on).
> One of my goals is to improve FOPs documentation (and Forrest's as I
> slog through the process of getting FOP's docs back online!) so that
> newbies like myself don't have to deal with silly frustrations like
> this. IMO, documentation should not skimp on examples. Rather, they
> should almost go out of their way to be verbose.
Speaking personally, I do not have the time to write extensive examples
- my code *is* my example, unfortunatley this creates a particularly
high barrier to entry, that's why I am spending the free time I have
between contracts helping out here on the user list, as well as writing
code improvements in the core of Forrest - work which I will eventually
get paid for. So how can users, help?
It would be really nice if people who get helped out on the user lists
could help improve the project by clarifying things that confused them
in the docs. As Clay says adding examples and notes from your experience
can help a great deal.
Contributing to a project like this one does not only mean writing code.
Docs and assisting fellow users on this list are equally as valuable.
To contribute your documentation enhancements edit the relevant files
and commit a diff to the issue tracker (
http://issues.cocoondev.org/secure/BrowseProject.jspa?id=10000 ). If you
don't know how to create a diff see
http://forrest.apache.org/contrib.html If you still can't prepare a diff
(that document probably needs some improving too) then posting your
notes/examples and an explanation of where they fit into the
documentation to an issue is the next best thing.
Every small contribution helps a great deal, please give back to the
project when your personal schedule allows.
> </rant>
>
> NOTE: The above rant wasn't directed 'at' Ross (or anyone in
> particular). ;-)
Neither was my response aimed at Clay (or anyone in particular) ;-)
Ross
Patches always welcome ;-) (was Re: modifying the css for forrest)
Posted by Thorsten Scherler <th...@apache.org>.
Clay Leeds escribió:
> <rant>
> I get confused in the Forrest docs where assumptions are made by the
> author, and I just don't get it. It's particularly frustrating, when I'm
> close to a solution, but the amount of time to resolve a problem is
> exacerbated by little assumptions like this, coupled with work weeks and
> time zones.
>
> One of my goals is to improve FOPs documentation (and Forrest's as I
> slog through the process of getting FOP's docs back online!) so that
> newbies like myself don't have to deal with silly frustrations like
> this. IMO, documentation should not skimp on examples. Rather, they
> should almost go out of their way to be verbose.
> </rant>
>
> NOTE: The above rant wasn't directed 'at' Ross (or anyone in
> particular). ;-)
>
> Web Maestro Clay
>
Just change the docs and add it to jira with a patch. ;-)
--
thorsten
"Together we stand, divided we fall"
Hey you (Pink Floyd)
Re: modifying the css for forrest
Posted by Clay Leeds <cl...@medata.com>.
On Nov 4, 2004, at 12:04 PM, Ross Gardler wrote:
> Linda Rose wrote:
>> ----- Original Message ----- From: "Ross Gardler"
>> <rg...@apache.org>
>>> You are /almost/ getting the hang of it. You found the right file,
>>> but you are editing the wrong copy - this one will get overwritten
>>> whenever you upgrade Forrest.
>>>
>>> See my other reply to Clays post with details of where you can
>>> safely configure your look and feel.
>>>
>>> Ross
>> Hi Ross,
>> As per the instructions, I copied the pelt skins to
>> myproject/src/documentation/skins/mypelt and modified the line in
>> forrest.properties project.skin=src/documentation/skins/mypelt.
>
> That should be just "mypelt".
I'm pretty sure Ross meant that the line in forrest.properties should
be just:
project.skin=mypelt
<rant>
I get confused in the Forrest docs where assumptions are made by the
author, and I just don't get it. It's particularly frustrating, when
I'm close to a solution, but the amount of time to resolve a problem is
exacerbated by little assumptions like this, coupled with work weeks
and time zones.
One of my goals is to improve FOPs documentation (and Forrest's as I
slog through the process of getting FOP's docs back online!) so that
newbies like myself don't have to deal with silly frustrations like
this. IMO, documentation should not skimp on examples. Rather, they
should almost go out of their way to be verbose.
</rant>
NOTE: The above rant wasn't directed 'at' Ross (or anyone in
particular). ;-)
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: modifying the css for forrest
Posted by Ross Gardler <rg...@apache.org>.
Linda Rose wrote:
> ----- Original Message ----- From: "Ross Gardler" <rg...@apache.org>
>
>> You are /almost/ getting the hang of it. You found the right file, but
>> you are editing the wrong copy - this one will get overwritten
>> whenever you upgrade Forrest.
>>
>> See my other reply to Clays post with details of where you can safely
>> configure your look and feel.
>>
>> Ross
>>
> Hi Ross,
>
> As per the instructions, I copied the pelt skins to
> myproject/src/documentation/skins/mypelt and modified the line in
> forrest.properties project.skin=src/documentation/skins/mypelt.
That should be just "mypelt".
Note, if you are only changing the CSS then you do not really need to do
this, it is only if you wnat to do some configuration that cannot be
done in skinconf.xml. If you do go this route you should also copy the
common skin accross to your skins directory, this prevents version
conflicts with later versions of Forrest.
If you do find you want to do things that can't be done in skinconf.xml
please put a feature request on the issue tracker. Some of our devs are
designing an improvement to the skin system at the moment and your input
would be very helpful.
Ross
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
----- Original Message -----
From: "Ross Gardler" <rg...@apache.org>
> You are /almost/ getting the hang of it. You found the right file, but you
> are editing the wrong copy - this one will get overwritten whenever you
> upgrade Forrest.
>
> See my other reply to Clays post with details of where you can safely
> configure your look and feel.
>
> Ross
>
Hi Ross,
As per the instructions, I copied the pelt skins to
myproject/src/documentation/skins/mypelt and modified the line in
forrest.properties project.skin=src/documentation/skins/mypelt.
Now I get the following error:
--------error message--------------------
fetch-versioned-skin:
Trying to get "src/documentation/skins/mypelt" skin version
0.6...
BUILD FAILED
C:\Forrest\apache-forrest-0.6\src\core\targets\skins.xml:107: The following
error occurred while executing this line:
C:\Forrest\apache-forrest-0.6\src\core\targets\skins.xml:119: The following
error occurred while executing this line:
C:\Forrest\ADLDocs\build\tmp\skinlist2fetchbuild.xml:7:
java.net.MalformedURLException: no protocol: src/documentation/skins/myp
elt-0.6.zip
----------------------------------------------------------
Am I supposed to change something else as well?
Thanks,
Linda
Re: modifying the css for forrest
Posted by Ross Gardler <rg...@apache.org>.
Linda Rose wrote:
> I found it in
> apache-forrest-0.6\src\core\context\skins\pelt\css\screen.css. When I
> modify that and do a build, my changes aren't clobbered. Yay! I'm
> starting to get the hang of this.
You are /almost/ getting the hang of it. You found the right file, but
you are editing the wrong copy - this one will get overwritten whenever
you upgrade Forrest.
See my other reply to Clays post with details of where you can safely
configure your look and feel.
Ross
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
I found it in apache-forrest-0.6\src\core\context\skins\pelt\css\screen.css.
When I modify that and do a build, my changes aren't clobbered. Yay! I'm
starting to get the hang of this.
Linda
----- Original Message -----
From: "Linda Rose" <li...@cox.net>
To: <us...@forrest.apache.org>
Sent: Wednesday, November 03, 2004 3:56 PM
Subject: Re: modifying the css for forrest
> Yes, I tried it and my changes to my-project\build\site\skin\basic.css got
> clobbered when I did a build. Where does the source basic.css live?
>
> Thanks, Linda
>
> ----- Original Message -----
> From: "Clay Leeds" <cl...@medata.com>
> To: <us...@forrest.apache.org>
> Sent: Wednesday, November 03, 2004 3:42 PM
> Subject: Re: modifying the css for forrest
>
>
>> On Nov 3, 2004, at 3:33 PM, Linda Rose wrote:
>>> Hi,
>>>
>>> I've been very impressed by the example sites that have been created
>>> using Forrest. I want to customize the look of mine. Can I modify
>>> my-project\build\site\skin\basic.css?
>>>
>>> Thanks,
>>>
>>> Linda
>>
>> IIUC, anything in build/site (or build\site\ on Windows) is fair game to
>> get clobbered when you do a /forrest/. For this reason, I tend to want to
>> make changes in src/* somewhere (can a member of the Forrest Team confirm
>> this?).
>
>
>>
>> Is it possible for you to make the necessary changes in the <extra-css/>
>> portion of src/documentation/skinconf.xml? I would assume not. Perhaps
>> the scale-dev/leather-dev skin may be along the lines of what you're
>> looking for (search the dev@forrest.apache.org lists for more info and to
>> 'watch' or 'contribute' to the progress)?
>>
>> If not, you could also modify the .css files in the forrest/*/skin/. Of
>> course, if you're using forrest-0.7-dev, those changes might get affected
>> (or get in the way of) svn updates. If you're using forrest-0.6, you
>> should be pretty safe, although you'll want to back up any of those files
>> before you make changes.
>>
>> HTH!
>>
>> Web Maestro Clay
>> --
>> Clay Leeds - <cl...@medata.com>
>> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
>> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>>
>>
>
>
>
Re: modifying the css for forrest
Posted by Linda Rose <li...@cox.net>.
Yes, I tried it and my changes to my-project\build\site\skin\basic.css got
clobbered when I did a build. Where does the source basic.css live?
Thanks, Linda
----- Original Message -----
From: "Clay Leeds" <cl...@medata.com>
To: <us...@forrest.apache.org>
Sent: Wednesday, November 03, 2004 3:42 PM
Subject: Re: modifying the css for forrest
> On Nov 3, 2004, at 3:33 PM, Linda Rose wrote:
>> Hi,
>>
>> I've been very impressed by the example sites that have been created
>> using Forrest. I want to customize the look of mine. Can I modify
>> my-project\build\site\skin\basic.css?
>>
>> Thanks,
>>
>> Linda
>
> IIUC, anything in build/site (or build\site\ on Windows) is fair game to
> get clobbered when you do a /forrest/. For this reason, I tend to want to
> make changes in src/* somewhere (can a member of the Forrest Team confirm
> this?).
>
> Is it possible for you to make the necessary changes in the <extra-css/>
> portion of src/documentation/skinconf.xml? I would assume not. Perhaps the
> scale-dev/leather-dev skin may be along the lines of what you're looking
> for (search the dev@forrest.apache.org lists for more info and to 'watch'
> or 'contribute' to the progress)?
>
> If not, you could also modify the .css files in the forrest/*/skin/. Of
> course, if you're using forrest-0.7-dev, those changes might get affected
> (or get in the way of) svn updates. If you're using forrest-0.6, you
> should be pretty safe, although you'll want to back up any of those files
> before you make changes.
>
> HTH!
>
> Web Maestro Clay
> --
> Clay Leeds - <cl...@medata.com>
> Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
> PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
>
>
Re: modifying the css for forrest
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Nov 3, 2004, at 3:33 PM, Linda Rose wrote:
>
>> I've been very impressed by the example sites that have been created
>> using Forrest. I want to customize the look of mine. Can I modify
>> my-project\build\site\skin\basic.css?
>>
>> Thanks,
>>
>> Linda
>
>
> IIUC, anything in build/site (or build\site\ on Windows) is fair game to
> get clobbered when you do a /forrest/. For this reason, I tend to want
> to make changes in src/* somewhere (can a member of the Forrest Team
> confirm this?).
You are correct. You should *only* edit things in your src directory.
> Is it possible for you to make the necessary changes in the <extra-css/>
> portion of src/documentation/skinconf.xml?
In the skinconf.xml file it is possible to change most of the colours
used, there are quite a few examples coulour schemes in that file. If
you want to do more you can override classes, or even add new ones by
placing them in the <extra-css> tags in that same file (again there are
examples in the file).
You can also configure a fair bit of the layout of the site in the
skinconf.xml file. Read the comments in that file and play around.
> If not, you could also modify the .css files in the forrest/*/skin/.
No, you should not be editing the files in forrest/*/skin/ as these
changes will get overwritten whenver you upgrade to a newer version of
Forrest. Only ever edit things in your projects src directory.
You can, however, create your own skin in your src directory and edit
that one. See http://forrest.apache.org/docs/your-project.html#skins for
more info.
Ross
Re: modifying the css for forrest
Posted by Clay Leeds <cl...@medata.com>.
On Nov 3, 2004, at 3:33 PM, Linda Rose wrote:
> Hi,
>
> I've been very impressed by the example sites that have been created
> using Forrest. I want to customize the look of mine. Can I modify
> my-project\build\site\skin\basic.css?
>
> Thanks,
>
> Linda
IIUC, anything in build/site (or build\site\ on Windows) is fair game
to get clobbered when you do a /forrest/. For this reason, I tend to
want to make changes in src/* somewhere (can a member of the Forrest
Team confirm this?).
Is it possible for you to make the necessary changes in the
<extra-css/> portion of src/documentation/skinconf.xml? I would assume
not. Perhaps the scale-dev/leather-dev skin may be along the lines of
what you're looking for (search the dev@forrest.apache.org lists for
more info and to 'watch' or 'contribute' to the progress)?
If not, you could also modify the .css files in the forrest/*/skin/. Of
course, if you're using forrest-0.7-dev, those changes might get
affected (or get in the way of) svn updates. If you're using
forrest-0.6, you should be pretty safe, although you'll want to back up
any of those files before you make changes.
HTH!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>