You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Clay Leeds <cl...@medata.com> on 2004/08/12 06:10:29 UTC
Forrest available-skins only lists test* skins
I was looking again for skins (seems to be a recurring theme[1] :-)),
and couldn't find them when I ran the /forrest available-skins/
command. It lists testskin & testskin2, but doesn't list the other
skins which I believe should be 'available':
# Specifies name of Forrest skin to use
#project.skin=forrest-site
#project.skin=pelt-dev
#project.skin=crust
project.skin=tigris
There's probably a reason it doesn't list these others, but I don't
know what it is. I can understand why pelt-dev isn't listed, but don't
understand why the others aren't listed with a brief description.
Web Maestro Clay
[1]
http://marc.theaimsgroup.com/?l=forrest-dev&m=108867525625688&w=2
Re: strange looping behaviour with pelt skin
Posted by David Crossley <cr...@apache.org>.
(Bringing this thread over form user list.)
David Crossley wrote:
> Philippe Vanpeperstraete wrote to user@f.a.o:
> > When generating the forrest website using the pelt skin, forrest
> > generates a seemingly infinite series of docs subdirectories, actually
> > crashing my computer. ...
Crashes Java with java.lang.OutOfMemoryError
> Yes i am seeing the issue too. ...
It only happens with the pelt skin.
When generating the core forrest documentation
it descends into docs/docs/docs chaos...
...
* [32/73] [2/50] 2.679s 18.4Kb docs/upgrading_05.html
X [0] docs/docs/upgrading_05.html
BROKEN:
/usr/local/svn/forrest/src/documentation/content/xdocs/docs/docs/upgrading_05.xml
(No such file or directory)
...
...
* [101/45] [2/56] 4.34s 89.6Kb
docs/docs/docs/docs/document-v13.dtdx.html
... and worse.
--
David Crossley
Re: strange looping behaviour with pelt skin
Posted by "Scherler, Thorsten" <th...@apache.org>.
Any ideas what could cause that?
Ever seen this behaviour before?
Any input welcome.
King regards
thorsten
Thorsten Scherler wrote:
> I will have a look on that tonight to!
>
> King regards
> thorsten
>
> David Crossley wrote:
>
>> Philippe Vanpeperstraete wrote:
>>
>>> When generating the forrest website using the pelt skin, forrest
>>> generates a seemingly infinite series of docs subdirectories, actually
>>> crashing my computer. Manually stopping the generation illustrates the
>>> issue. This seems to affect only the howto and faq pages. Did anyone
>>> else encounter this behaviour? Im using a freshly updated copy (revision
>>> 36319), followed by:
>>>
>>> build clean
>>> build
>>> edit forrest.properties to change skin
>>> forrest clean
>>> forrest
>>
>>
>>
>> Yes i am seeing the issue too. Also it happens with more
>> than just howto and faq, e.g. also with upgrading_06.html
>>
>> However, i don't see it in the 'forrest seed site'.
>>
>> Switching the core XSLT processor to use Saxon instead,
>> then there is no problem.
>>
>
>
Re: strange looping behaviour with pelt skin
Posted by Thorsten Scherler <th...@apache.org>.
I will have a look on that tonight to!
King regards
thorsten
David Crossley wrote:
> Philippe Vanpeperstraete wrote:
>
>>When generating the forrest website using the pelt skin, forrest
>>generates a seemingly infinite series of docs subdirectories, actually
>>crashing my computer. Manually stopping the generation illustrates the
>>issue. This seems to affect only the howto and faq pages. Did anyone
>>else encounter this behaviour? Im using a freshly updated copy (revision
>>36319), followed by:
>>
>>build clean
>>build
>>edit forrest.properties to change skin
>>forrest clean
>>forrest
>
>
> Yes i am seeing the issue too. Also it happens with more
> than just howto and faq, e.g. also with upgrading_06.html
>
> However, i don't see it in the 'forrest seed site'.
>
> Switching the core XSLT processor to use Saxon instead,
> then there is no problem.
>
Re: strange looping behaviour with pelt skin
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Switching the core XSLT processor to use Saxon instead,
> then there is no problem.
Woops, retract that statement about Saxon. It happens there too.
I mistakenly still had the default skin "crust" enabled
where the issue does not occur ... only happens with "pelt".
--
David Crossley
Re: strange looping behaviour with pelt skin
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Philippe Vanpeperstraete wrote:
> > When generating the forrest website using the pelt skin, forrest
> > generates a seemingly infinite series of docs subdirectories, actually
> > crashing my computer. ...
Crashes Java with out of memory error.
> Yes i am seeing the issue too. ...
We are taking this discussion over to the dev list.
--
David Crossley
Re: strange looping behaviour with pelt skin
Posted by David Crossley <cr...@apache.org>.
Philippe Vanpeperstraete wrote:
> When generating the forrest website using the pelt skin, forrest
> generates a seemingly infinite series of docs subdirectories, actually
> crashing my computer. Manually stopping the generation illustrates the
> issue. This seems to affect only the howto and faq pages. Did anyone
> else encounter this behaviour? Im using a freshly updated copy (revision
> 36319), followed by:
>
> build clean
> build
> edit forrest.properties to change skin
> forrest clean
> forrest
Yes i am seeing the issue too. Also it happens with more
than just howto and faq, e.g. also with upgrading_06.html
However, i don't see it in the 'forrest seed site'.
Switching the core XSLT processor to use Saxon instead,
then there is no problem.
--
David Crossley
strange looping behaviour with pelt skin
Posted by Philippe Vanpeperstraete <ph...@skynet.be>.
When generating the forrest website using the pelt skin, forrest
generates a seemingly infinite series of docs subdirectories, actually
crashing my computer. Manually stopping the generation illustrates the
issue. This seems to affect only the howto and faq pages. Did anyone
else encounter this behaviour? Im using a freshly updated copy (revision
36319), followed by:
build clean
build
edit forrest.properties to change skin
forrest clean
forrest
* [116/29] [0/0] 5.031s 281.5Kb docs/howto-v13.dtdx.pdf
* [117/30] [2/56] 3.141s 123.0Kb docs/docs/howto-v13.dtdx.html
* [118/31] [2/56] 3.094s 123.3Kb
docs/docs/docs/docs/howto-v13.dtdx.html
* [119/30] [0/0] 4.781s 281.5Kb
docs/docs/docs/docs/howto-v13.dtdx.pdf
* [120/29] [0/0] 4.547s 281.5Kb docs/docs/howto-v13.dtdx.pdf
* [121/30] [2/56] 3.391s 124.0Kb
docs/docs/docs/docs/docs/docs/docs/docs/how
to-v13.dtdx.html
* [122/29] [0/0] 4.453s 281.5Kb
docs/docs/docs/docs/docs/docs/docs/docs/how
to-v13.dtdx.pdf
* [123/28] [0/0] 0.109s 2.5Kb skin/basic.css
* [124/29] [2/22] 0.5s 15.3Kb howto/howto-pdf-tab.html
X [0] howto/howto/howto-pdf-tab.html
BROKEN:
C:\forrest\src\documentation\content\xdocs\howto\howto\howto-pdf-tab.xml
(Het systeem kan het opgegeven pad niet vinden)
* [126/27] [0/0] 0.313s 17.8Kb howto/howto-pdf-tab.pdf
* [127/26] [0/0] 0.343s 19.7Kb docs/document-v13.pdf
* [128/26] [1/33] 0.953s 37.4Kb faq.html
* [129/25] [0/0] 0.891s 55.1Kb faq.pdf
* [130/27] [3/46] 0.812s 41.9Kb docs/primer.html
* [131/26] [0/0] 1.0s 43.4Kb docs/primer.pdf
X [0] docs/docs/primer.html BROKEN:
C:\forre
st\src\documentation\content\xdocs\docs\docs\primer.xml (Het systeem kan
het opg
egeven pad niet vinden)
* [133/26] [2/56] 2.328s 101.4Kb
docs/docs/docs/docs/docs/docs/docs/docs/faq
-v13.dtdx.html
* [134/25] [0/0] 3.735s 217.5Kb
docs/docs/docs/docs/docs/docs/docs/docs/faq
-v13.dtdx.pdf
Re: Forrest available-skins only lists test* skins
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> I was looking for a way to determine which skins are available to
> /forrest/ users. I wanted to change from forrest-site to something
> else. I'd seen discussion of new skins in the list (tigris, crust,
> pelt-dev) and wanted to 'see' what choices were available. ...
If you were using the name "forrest-site" in your
forrest.properties configuration, then that is being
automatically renamed to "crust" (as our backward
compatibility). So just use the name "crust" directly.
Thanks for your idea about explaining default skins
in the 'forrest available-skins' ... good catch.
--
David Crossley
Re: Forrest available-skins only lists test* skins
Posted by Clay Leeds <cl...@medata.com>.
On Aug 12, 2004, at 5:33 PM, David Crossley wrote:
> Clay Leeds wrote:
>> I was looking again for skins (seems to be a recurring theme[1] :-)),
>
> Why are you looking for additional skins? Those concepts
> from those old experimental skins are being added to the
> current default skins, mainly "pelt-dev" but also "crust".
I was looking for a way to determine which skins are available to
/forrest/ users. I wanted to change from forrest-site to something
else. I'd seen discussion of new skins in the list (tigris, crust,
pelt-dev) and wanted to 'see' what choices were available. So I figured
/forrest available-skins/ would get me the answer. Unfortunately, it
didn't. I found the other skin names by doing a /find . -iname *skin*/
from my forrest/ dir (using 'svn update -r 36024').
>> and couldn't find them when I ran the /forrest available-skins/
>> command. It lists testskin & testskin2, but doesn't list the other
>> skins which I believe should be 'available':
>
> I just added a comment to 'forrest available-skins' to provide
> some guidance.
Sounds good!
>> # Specifies name of Forrest skin to use
>> #project.skin=forrest-site
>> #project.skin=pelt-dev
>> #project.skin=crust
>> project.skin=tigris
>>
>> There's probably a reason it doesn't list these others, but I don't
>> know what it is.
>
> Only that no-one has found time to add that capability.
>
>> I can understand why pelt-dev isn't listed, but don't
>> understand why the others aren't listed with a brief description.
>
> Later we will add an automated description. For the moment
> see http://forrest.apache.org/docs/skins.html
Looks good! I hadn't noticed the update. Thanks for the pointer!
Web Maestro Clay
Re: Forrest available-skins only lists test* skins
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> I was looking again for skins (seems to be a recurring theme[1] :-)),
Why are you looking for additional skins? Those concepts
from those old experimental skins are being added to the
current default skins, mainly "pelt-dev" but also "crust".
> and couldn't find them when I ran the /forrest available-skins/
> command. It lists testskin & testskin2, but doesn't list the other
> skins which I believe should be 'available':
I just added a comment to 'forrest available-skins' to provide
some guidance.
> # Specifies name of Forrest skin to use
> #project.skin=forrest-site
> #project.skin=pelt-dev
> #project.skin=crust
> project.skin=tigris
>
> There's probably a reason it doesn't list these others, but I don't
> know what it is.
Only that no-one has found time to add that capability.
> I can understand why pelt-dev isn't listed, but don't
> understand why the others aren't listed with a brief description.
Later we will add an automated description. For the moment
see http://forrest.apache.org/docs/skins.html
--
David Crossley
Re: Forrest available-skins only lists test* skins
Posted by David Crossley <cr...@apache.org>.
Charles Palmer wrote:
> Is there any guidance or advice on producing skins?
The first bit of guidance is to ask why do you need to?
Our plan is to make the default Forrest skins to be
highly configurable, so that with minimal skills
people can change the layout and appearance.
> The comment in site2xhtml.xsl says this:
>
> site2xhtml.xsl is the final stage in HTML page production. It merges HTML
> from
> document2html.xsl, tab2menu.xsl and book2menu.xsl, and adds the site header,
> footer, searchbar, css etc. As input, it takes XML of the form:
>
> <site>
> <div class="menu">
> ...
> </div>
> <div class="tab">
> ...
> </div>
> <div class="content">
> ...
> </div>
> </site>
>
> It looks to me that the .xsl file then proceeds to grab content and generate
> HTML - but it looks like other .xsl files also generate HTML and so are
> therefore involved in the look and feel.
Various XML aggregations and XSL transformations are pipelined
together. The site2xhtml.xsl is usually the final stage.
> Is there any automated or documented way of creating the .xsl files from an
> existing HTML website, or is it all hand-crafted? That is, can arbitrary
> HTML design tools be used to produce good-looking site templates, which can
> then transformed into .xsl files? Or do you have to be both an HTML guru and
> XSL guru to make a new skin?
Making a new skin is not a trivial exercise. Yes one would
need specialised skills. That is why we need the default
skins to be highly configurable.
--
David Crossley
Re: creating skins (was: Forrest available-skins only lists test*
skins)
Posted by Dave Brondsema <da...@brondsema.net>.
Charles Palmer wrote:
> Team
>
> Is there any guidance or advice on producing skins?
>
> Is there any automated or documented way of creating the .xsl files from an
> existing HTML website, or is it all hand-crafted? That is, can arbitrary
> HTML design tools be used to produce good-looking site templates, which can
> then transformed into .xsl files? Or do you have to be both an HTML guru and
> XSL guru to make a new skin?
>
> Charles
>
Yes, you need to know XML, HTML and CSS. The best way to create a new
skin is to copy an existing one and modify it.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: Forrest available-skins only lists test* skins
Posted by Charles Palmer <ch...@dspdesign.com>.
Team
Is there any guidance or advice on producing skins?
The comment in site2xhtml.xsl says this:
site2xhtml.xsl is the final stage in HTML page production. It merges HTML
from
document2html.xsl, tab2menu.xsl and book2menu.xsl, and adds the site header,
footer, searchbar, css etc. As input, it takes XML of the form:
<site>
<div class="menu">
...
</div>
<div class="tab">
...
</div>
<div class="content">
...
</div>
</site>
It looks to me that the .xsl file then proceeds to grab content and generate
HTML - but it looks like other .xsl files also generate HTML and so are
therefore involved in the look and feel.
Is there any automated or documented way of creating the .xsl files from an
existing HTML website, or is it all hand-crafted? That is, can arbitrary
HTML design tools be used to produce good-looking site templates, which can
then transformed into .xsl files? Or do you have to be both an HTML guru and
XSL guru to make a new skin?
Charles
----- Original Message -----
From: "Clay Leeds" <cl...@medata.com>
To: <us...@forrest.apache.org>
Sent: Thursday, August 12, 2004 5:10 AM
Subject: Forrest available-skins only lists test* skins
> I was looking again for skins (seems to be a recurring theme[1] :-)),
> and couldn't find them when I ran the /forrest available-skins/
> command. It lists testskin & testskin2, but doesn't list the other
> skins which I believe should be 'available':
>
> # Specifies name of Forrest skin to use
> #project.skin=forrest-site
> #project.skin=pelt-dev
> #project.skin=crust
> project.skin=tigris
>
> There's probably a reason it doesn't list these others, but I don't
> know what it is. I can understand why pelt-dev isn't listed, but don't
> understand why the others aren't listed with a brief description.
>
> Web Maestro Clay
>
> [1]
> http://marc.theaimsgroup.com/?l=forrest-dev&m=108867525625688&w=2
>