Thanks Thorsten, that fixed it. Didn't realize that memory equals heap
space.
Regards,
Ferdinand Soethe
Aggregating my project with wholesite.pdf in dynamic mode I'm getting a
error
HTTP ERROR: 500 Java+heap+space
which is probably due to limited heap space.
How/where can I add the 'xmx1024M' Parameter for Java to the Jetty
configuration to increases heap space?
Thanks,
Ferdinand
Hello Bryce,
Am 02.10.10 18:41, schrieb Bryce Alcock:
I am looking for a way to create page in forrest that
is NOT on any of the menus.
The basic requirements is that I want to create a page that you can
get to _ONLY_ from direct navigation.
There will be no links to it in any of the menus or
/stylesheets.
Yet I agree with Brian, these style sheets were designed to be used in a
pipeline, so you may have to make some major adjustments.
Regards,
Ferdinand Soethe
Am 06.07.10 06:27, schrieb Alan Wang:
Hi All,
I am writing a program similar to pdf output plugin to convert xdoc
pages in xml
Hi David,
David Poetzsch-Heffter schrieb:
> Hi.
>
> This was a good idea, it worked for me, thanks.
>
> david.
You could probably help others by posting the extra-css you added :-)
Regards,
Ferdinand Soethe
---
Fischerzug 3a
21522 Hohnstorf
Germany
ph +4139/696244
mob +17
Hi David,
afaik you can move the logo by adding some additional css in the
extra-css-section of the skinconfig.xml.
This is appended to the end of the Forrest CSS and will override any
settings uses by Forrest.
Regards,
Ferdinand
david schrieb:
> Hello all!
>
> I'm intending to use forrest to cr
As far as I remember it is important that your link points to the
odt-documentname but with the extension .html so that
Forrest will process it properly. That is a bit confusing but consistent
with the "you ask for what you want and not where it originates
from"-logic of Forrest Pipelines.
Cyriaqu
name="background-color"
> select="$config/colors/[EMAIL PROTECTED]'body']/@value" />
reference settings in skinconfig () and are used in one or
several of the helper stylesheets in the directory.
>
>
>
>
>
Reg
Am 14.03.2008 um 01:22 schrieb David Crossley:
I built our past releases (which contain sources
plus a pre-built binary) on Mac and no-one complained
during the pre-release testing phase about running
on Windows.
Oh great. I will try running my build under windows next week just to
be sure.
OK, problem solved with a fresh check out and building it.
Thanks everybody.
Regards,
Ferdinand Soethe
Am 13.03.2008 um 12:21 schrieb Ross Gardler:
Ferdinand Soethe wrote:
Am 12.03.2008 um 01:57 schrieb David Crossley:
Ferdinand, i remember that you used to run Windows.
If you just copied
OK, problem solved with a fresh check out and building it.
Thanks everybody.
Regards,
Ferdinand Soethe
Am 13.03.2008 um 12:21 schrieb Ross Gardler:
Ferdinand Soethe wrote:
Am 12.03.2008 um 01:57 schrieb David Crossley:
Ferdinand, i remember that you used to run Windows.
If you just copied
Am 12.03.2008 um 01:57 schrieb David Crossley:
Ferdinand, i remember that you used to run Windows.
If you just copied everything over to your new Mac then
there will be DOS line-endings issues (depending on how
you did the copy).
Try a fresh svn checkout of Forrest trunk.
Thanks David (an eve
Thorsten Scherler schrieb:
> shell is not installed in the location /bin/sh
> find sh and make a symlink to /bin/sh.
Strange. There is a file
named sh in /bin and when I execute it
I get a new sh-prompt.
To me that means that there is a shell in the right
directory, no?
Regards,
Fer
$ forrest run
bash: /Applications/forrest/head/bin/forrest: /bin/sh^M: bad
interpreter: No such file or directory
bash-3.2$
Any ideas what I'm doing wrong?
Regards,
Ferdinand Soethe
Does anyone have instuctions or tips for running Forrest under Leopard
on a MacBook.
I tried opening the terminal and running the forrest.sh but that
doesn't do the trick.
Regards,
Ferdinand Soethe
e menu-system so that context (where am I) is lost.
I agree with Gavin: It really depends on what you want and need.
The nice part of this discussion is that I finally understand why that
happens with mirrors.cgi :-)
Best regards,
Ferdinand Soethe
Ross Gardler wrote:
> Retrieve http://www.bildungsverein.de/linkmap.html and you will see
> another link to the "hidden" page. This page appears in all Forrest
> generated sites, it is what Forrest uses to as a list of pages that
> need to be generated according to site.xml.
That's what I meant
sts all pages I don't
see any references.
Best regards,
Ferdinand Soethe
show with context (with an entry on the menu)
in your site.
hth
Ferdinand Soethe
Actually the extra-css-section in skinconfig offers a whole range of
options tweaking or enhancing the css coming with your skin.
Since the content of this section is appended to the css provided by the
skin, you can override existing css-handles or add your own.
So all you'd really need to do is
that the commented meta-elements are used anywhere? I am
> not aware of such a thing, and if they are used I do not understand why
> they are commented out.
No, no problem with things commented out.
If that was a misunderstanding please ignore my comments.
Regards,
Ferdinand Soethe
Ross Gardler wrote:
> I'm not sure why the meta tags are left in the xdoc format. Perhaps a
> debugging remnant. I suspect it would be safe to remove the relevant XSL
> that produces these comments.
Please don't remove the meta-elements in these transformations as they
are needed for transporting
Thanks for the pointer, Ross.
Ross Gardler wrote:
> Ferdinand Soethe wrote:
>> I'd like to use DokuWiki as my CMS to generate content and Forrest to
>> render it. Since DokuWiki has a different syntax from MoinMoin and the
>> other wiki supported by our plugin I see two
I'd like to use DokuWiki as my CMS to generate content and Forrest to
render it. Since DokuWiki has a different syntax from MoinMoin and the
other wiki supported by our plugin I see two ways of rendering pages in
forrest:
1. Adapt the plugin to support DokuWiki-Syntax
I'll look into that tonite
I'd like to use DokuWiki as my CMS to generate content and Forrest to
render it. Since DokuWiki has a different syntax from MoinMoin and the
other wiki supported by our plugin I see two ways of rendering pages in
forrest:
1. Adapt the plugin to support DokuWiki-Syntax
I'll look into that tonite
Gav wrote:
> Not really, just popped in to see if html2document.xsl is the correct name
> For the version of forrest you are using with this, or if you should be
> Using html-to-document.xsl.
>
But I'm using .7 and for my project there is html2document.xsl in the
resources directory.
Thanks
I'd like to use DokuWiki as my CMS to generate content and Forrest to
render it. Since DokuWiki has a different syntax from MoinMoin and the
other wiki supported by our plugin I see two ways of rendering pages in
forrest:
1. Adapt the plugin to support DokuWiki-Syntax
I'll look into that tonite
ve wget) our own site after every
> reboot or install to warm up the caches. This definitly improves the
> user experience for the first user visiting ;)
I like that term "warm up the caches", a bit like building a fire in
the fireplace ...
--
Ferdinand Soethe
with it would be to raise this issue on the
developer list because this is really quite a common problem.
One solution that comes to mind is to implement the duplication of
multiply references content as an automated process.
hth
--
Ferdinand Soethe
--
Ferdinand Soethe
stability of
running Forrest dynamically?
Thanks,
--
Ferdinand Soethe
current scales
functionalities back into pelt in some not so distant future.
Regards,
Ferdinand Soethe
another template to number the items of the TOC.
--
Ferdinand Soethe
l items.
Comile the seed site with scales-skin to see the effect in the samples.
--
Ferdinand Soethe
for local menues since most of the goals can be achieved
in other, cleaner ways.
--
Ferdinand Soethe
page in
xsl-fo: *.fo
formatting objects source of current page (used to generate
pdf-document).
--
Ferdinand Soethe
Ferdinand Soethe wrote:
> Hallo Franz-Josef,
Sorry folks. My mailer was redirecting messages to the wrong folder.
--
Ferdinand Soethe
Ferdinand Soethe wrote:
> Hallo Franz-Josef,
Sorry folks. My mailer was redirecting messages to the wrong folder.
--
Ferdinand Soethe
könnte?
--
Ferdinand Soethe
PE aber nirgends gefunden.
Schönen Gruß
Ferdinand Soethe
[sorry, I was just gonna write a short answer and then I got carried
away ...]
Collapsed menus showing all of the menu items usually indicates an
error in site or tabs.xml.
1 Quite often a mismatch of directory names
that need to be exactly identical across both files.
[checking ...] Don't s
is anmeldunPHP.php? It appears to have nothing to do with your
> request for "abc.php", however, Cocoon is requesting it, any idea why?
I'm, sorry. In my mail I changed the original name of the files
from 'anmeldungPHP' to 'abc' to not confuse anybody.
So I was really requesting
'anmeldungPHP.php' in site and the file in xdocs is named 'anmeldungPHP.html'.
This the name in the error message.
--
Ferdinand Soethe
vailable.
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
Request URI
anmeldungPHP.php
cause
null
request-uri
/anmeldungPHP.php
Any ideas?
--
Ferdinand Soethe
ver
to process it correctly. And when I change the extension of the file
from html to php our pipelines don't want to skin it anymore. Too many
extension-based matchers along the route I suppose.
--
Ferdinand Soethe
peline as the
php-instructions pass untouched through my html-pipeline. I just don't
manage to get them skinned. And didn't want to re-create the whole
html-pipeline in my custom sitemap.
--
Ferdinand Soethe
d the unchanged within its body) so that I can
place this on a php-enabled server and use external scripts.
Note: I'm not expecting the php-function calls to be resolved by
Forrest, I merely want the document skinned and php-calls passed
intact.
Any suggestions?
--
Ferdinand Soethe
n my current project-site (Forrest 07x) linkmap gives me all
the links from site.xml in proper order including those in other tabs.
Not sure where that bug went?
Perhaps it only happens in improperly structures sites (remember out
struggle with the Forrest Website.)
--
Ferdinand Soethe
> - You can use p-Elements for the headings that you don't want to show,
>> add a class="whatYouLike" and format those with extra CSS to look
>> like a heading. Although, I must admit, this is rather a nasty hack!
> Even worse, now your document no longer has the defined structure it
> should have.
One of those rare occation where we actually agree on something :-)
--
Ferdinand Soethe
bulky documentation it would be useful to provide such an IOC.
> E.g.
Well, perhaps linkmap.html is a good start. It's generated
automatically in the root.
Hope that helps,
--
Ferdinand Soethe
Thanks David,
I'll see if I can find some documentation that way.
I just though it was weired that these settings are not mentioned in
any of the references that I checked.
--
Ferdinand Soethe
7;t find any that really explained it.
--
Ferdinand Soethe
nents anywhere.
Thanks,
--
Ferdinand Soethe
Miroslav Mocek wrote:
> strange. when I was first trying to do that (without configuration), it
> showed only empty page (menus and all, but no content). now it's working.
I've had that problem and the self-healing as well.
Anybody with ideas what is happening there.
--
Ferdinand Soethe
get a completely open
menu tree under each tab.
Going from there it might make sense to add a new skinconfig setting
that control the addition of the JavaScript code that collapses the
menues.
--
Ferdinand Soethe
m that I mentioned a
few days ago in the dev forum (Rev 226492).
Or wait until I come back in two weeks and will apply that patch
myself.
--
Ferdinand Soethe
and tabs.xml here so that we can all look
at a working solution.
--
Ferdinand Soethe
ocumentation/skins/$skin-name/
>> Javascript files would go in a "scripts" subdirectory.
>> CSS files would go in a "css" subdirectory.
>>
>> Then refer to those from your source documents with
>> URIs like /skin/blah.js and /skin/foo.css
>>
>> I am figuring this out by looking at the core sitemap
>> called forrest/main/webapp/resources.xmap
>> Search for "javascript" then follow to the
>> section.
>>
>> Hope that helps.
> yes a lot! it was easy to do.
> I thank anyone helped me.
--
Ferdinand Soethe
Helena Edelson wrote:
> I think Forrest is pretty sweet.
I think you have added quite a bit of sweetness to it. Seriously, I
think these sites look pretty cool and are an
excellent example of how much you can do with Forrest.
How much time did you spend on customizing the skins?
--
Ferdin
the
> ground up in a few weeks.
Afaik we will continue to support documentvxx so your work would
probably not be wasted.
Also: we already support xhtml as part of the html-processing. Check
out the e,bedded html-sample (bad naming) in the seed site to see that.
--
Ferdinand Soethe
David Crossley wrote:
> The question was do we need to add configuration notes
> to http://forrest.apache.org/docs/catalog.html to
> explain how to configure the editor in eclipse.
Sounds like a good idea. Unfortunately I don't have it installed right
now so I can't tes
). Will need to
> check this though.
Not sure what question is being answered here but:
Catalog support already worked flawlessly in M3 or M4. Better than
most commercial eclipse plugins. Tested it for use with Forrest and
found no problems.
--
Ferdinand Soethe
David Crossley wrote:
> Actually, this discussion would be useful as an FAQ,
> to explain the power of this source type match method.
Thanks for explaining.
Will try and find the bug in HTML-processing first though.
--
Ferdinand Soethe
et processed up to the http://localhost:/body-xhtml-test.html
step of the pipeline, after that the page content simply vanished.
--
Ferdinand Soethe
he pipeline
body-... will produce a clean looking document.
Do I need to add a new mapping to the source pipeline, what else would
I need to do.
Thanks
--
Ferdinand Soethe
Hi Thorsten,
I'm not sure who you are talking to. Me? Looks to me like I set reply
to properly. No?
Thorsten Scherler wrote:
> Please set "Reply to" to this list in the future (or unset it).
--
Ferdinand Soethe
Saxon in as default in all my my Forrest-transformations? Is it
that easy?
--
Ferdinand Soethe
> Ferdinand Soethe wrote:
>> Antonio Gallardo wrote:
>> Forrest is built on Apache Cocoon. Cocoon can use saxon as the XSLT
>> processor. Saxon supports xpath v2. That means is posible to use xpath v2
>> right now in forrest.
> Thanks. That is good to know. If
to offer a windows html-help
plugin as output as it is a reuirement for well integrated software
documentation on Windows.
Perhaps Johannes and I could work on making a finished plugin
together?
--
Ferdinand Soethe
g here?
--
Ferdinand Soethe
* [Icon: add] Added How to customize processing of html source [Link:
docs_0_70/howto/howto-custom-html-source.html] (DC) Thanks to Ferdinand
Soethe. Fixes FOR-446 [Link:
http://issues.apache.org/bugzilla/buglist.cgi?bug_id=FOR-446].
* [Icon: add] Added How-To Run Forrest f
ctions are expressed in the final output.
--
Ferdinand Soethe
float: left
> margin: 10px 10px 0 0 ;
> }
Which seems to be the problem here. The missing semicolon after
'float: left' is probably the culprit as far as I can tell.
> Does anyone have any idea what to do or where to add the code? Thanks
> so much. Dana
;
--
Ferdinand Soethe
Ross Gardler wrote:
> This is becoming an increasingly common request on this list. After the
> 0.7 release I will create a release for the plugin and make it available
> via the Eclipse upgrade mechanism.
Great idea.
--
Ferdinand Soethe
t one needs to be
careful as you might kill other java-based software nevertheless.
--
Ferdinand Soethe
tp://jetty.mortbay.org/jetty/faq?s=100-FAQ&t=Z2).
There is a port that you can call to stop the server.
--
Ferdinand Soethe
ted that way is much harder to comprehend (getting lost in the
web) and also a pain to maintain in the long run.
--
Ferdinand Soethe
The clear typographically structuring
of the menus, the use of color and the placement of logos and
background image would make it very useful for commercial and private
sites.
Would you consider donating it to our skin pool? Or short of that share
the code so that others can copy bits and pieces of it?
--
this to be so. After
all it does force you to duplicate each anchor in the page if your
want to address it. Or use the normal http-protocol which is not
really a solution either.
--
Ferdinand Soethe
orer
(I'm thinking about either send-tos) or associating a dummy file
in the project root with these commands.
Can anybody recommend an open source install software for windows?
--
Ferdinand Soethe
did not expect to have a
change in CSS change the number or names of files generated.
And even if it did, the new page should/would only load the
stylesheets that Forrest knew about when generating the new pages. So
what good would a clean do here?
Btw: While I was testing I was using jetty ...
--
Ferdinand Soethe
font-size : 80%;
}
to move the text to the side. Sort of counterintuitive that the last
figure is responsible for left padding but it works.
Thanks for all your suggestions,
--
Ferdinand Soethe
to move them to the right by the same amound that I widen
the menu.
Thanks,
--
Ferdinand Soethe
orners and I
haven't figured out how they are positioned yet.
I guess I'll have to put my nose in pelt to find out.
--
Ferdinand Soethe
I need to increase the width of the menu-page to fit longer labels
properly. Any ideas how best to do this?
--
Ferdinand Soethe
as startup like before and in any other directory.
Sounds to me like a very consistent approach. Is it difficult to
change that?
--
Ferdinand Soethe
it doesn't. In terms of the logic of site
it doesn't. I'll add a comment about this in site.xml
--
Ferdinand Soethe
: http://localhost:/index.html
So is this a problem of jetty rather than Forrest?
--
Ferdinand Soethe
I'd like to hide the 'build with forrest menu' that is displayed at
the bottom of each menu but I didn't find an option for that in
skinconf.xml. Is there another place to look or is placing
div#credit {visibility:hidden}
in the extra css currently the only option?
--
Ferdinand Soethe
gt;
and will disappear only when I place an index.xml in the xdocs
directory.
So why does Forrest want index.html. Is this a bug?
--
Ferdinand Soethe
le.
I agree. But increasing size is a major feature for visually impaired
people and they often need to increase the size quite a bit to read a
page.
So how to deal with that? For now having the menu area grow with the
font size might help.
--
Ferdinand Soethe
To reproduce:
Load any Forrest page (http://forrest.apache.org/index.html)
Click +a repeatedly
Watch menu item 'Documentation' grow into the page text area.
Is this a known problem, should I report this in Jira?
--
Ferdinand Soethe
Thanks, all of you. Now I understand where to look and how to read
that.
David Crossley wrote:
DC> We had a recent discussion that we need to have a document
DC> that describes all of this, but no-one has done it.
Have made a note to do that ...
--
Ferdinand
document-vxx before it gets skinned. And it is probably not a
plug-in (since I found none that looked like it) but a build-in
feature.
Only questions remaining is: Where is the grammar for this XHTML
subset defined. I saw only the general xhtml-dtds in
...\main\webapp\resources\schema.
Thanks,
Ferdinand Soethe
Thanks. Now I can safely train people to use document-v20 and wait
for xhtml to come along and turn into a stable implementation.
Ferdinand Soethe
ay to find out what modules are used
in any given Forrest release?
If not, wouldn't this be a useful thing
to report somewhere?
Thanks,
Ferdinand Soethe
-support become a plugin?
Thanks
Ferdinand Soethe
Juan Pablos wrote:
JJP> we are using xalan-2.6.1 and that support xpath v1
Thanks! Any idea when this will change to support xpath v2? There are
soo many useful functions in it.
--
Ferdinand Soethe
eally do test cases on your grammar.
Ferdinand Soethe
Ferdinand Soethe wrote:
FS> I have a real nasty problem with two validating Eclipse XML-plugins as
FS> soon as I add doctypes to my Forrest documents:
XMLBuddy's creator confirmed the problem and added that they are
working on catalog support and will speed it up because of this
pro
uld go wrong (and not be detected). So
somebody saying this way to do it is right would be much appreciated.
--
Ferdinand Soethe
seem to
get stuck trying to find the resource in the doctype only.
I don't really think that it has to do with the catalog not working
because both will work just finde and validate if I remove the
doctype.
Ferdinand Soethe
1 - 100 of 134 matches
Mail list logo
