Adam R. B. Jack wrote:
I'll certainly guilty of being away for a while, but
gump.document.forrest is not a small thing, and to my eyes, not entirely
obvious.
...
Also, if we want both xdoc and html output we'd need to set
of tempaltes (with code in) which isn't nice.
Maybe my comment got lost...
Nicola Ken Barozzi wrote:
Adam R. B. Jack wrote:
I'll certainly guilty of being away for a while, but
gump.document.forrest is not a small thing, and to my eyes, not entirely
obvious.
...
Also, if we want both xdoc and html output we'd need to set
of tempaltes (with code in) which isn't nice.
Also, if we want both xdoc and html output we'd need to set
of tempaltes (with code in) which isn't nice.
Maybe my comment got lost... generate html and Forrest can skin that too.
In other words, Forrest can skin an html site.
I heard it, but I think I mentally filtered it somewhat,
Now realize that I am *NOT* proposing Anakia. What I am proposing is
that the ability to view a site as it is being produced is a very
valuable thing to have, and an important consideration both for a
machine which is a shared resource and for any hope of there ever being
personal usage of
Sam Ruby wrote:
Nicola Ken Barozzi wrote:
...
Maybe my comment got lost... generate html and Forrest can skin that too.
In other words, Forrest can skin an html site.
So, if you make Cheetah output plain html you can see the site
natively, or decide to have Forrest skin over it and publish it
Sam Ruby wrote:
Beyond that, I would like to reiterate the point that there is value in
keeping true to the original design where Gump bootstraps its own
dependencies.
I agree with that.
--
Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
Nick Chalko wrote:
Stefano Mazzocchi wrote:
\
.
Ok, I think that reducing complexity is critical for wider adoption.
+1 in removal of forrest and go plain XHTML + CSS. But please, let's
use a velocity-like approach, not a DOM like approach!
I am not sure how removing forrest reduces
I'll certainly guilty of being away for a while, but
gump.document.forrest is not a small thing, and to my eyes, not entirely
obvious.
It is really just a lot of repetative simple code, building simple xdoc
pieces. It it's pretty, but it isn't that bad.
We have gump.document.text, and we
Adam R. B. Jack wrote:
BTW: I'm eager to see some graphics. If SVG can be written (in XML, viua
Python) can Forrest convert these to images (using Batik or somethough?)
I'll happily continue with Forrest if that is a good way to get images
rendered.
Yes
Just put foo.svg and then access it as
Adam Jack wrote:
Forrest uses cocoon (http://cocoon.apache.org/2.0/)
Which is a servlet that does xml pipelines
XML - transform - transform -- xml (or whatever) out.
Along with caching all kinds of other cool stuff.
That is what you get when you use the forrest run command
Because many, many of
Adam Jack wrote:
Whatever the cause, I am really starting to get 'done' with forrest. I
support it's use, I introduced it have dealt with the issues and built
workarounds from day one, but it is hard work w/ no fun.
I remember that feeling. I like the forrest project and I like the
forrest devs
I wonder if we ought consider replacing Forrest with a pure Python HTML
producer. As above, I can't prove that forrest is the problem, but a pure
Python solution might just halve the unknowns.
I've been using Python to generate HTML from XML via XSL for a few weeks
now using 4suite. I'm fairly
Adam Jack wrote:
I've been trying to run some quick jobs (a check.py not an integrate.py) to
try to get insight into this problem. I'm finding (at least on my machine)
that forrest is growing to huge size, and getting bogged down in swapping.
I can't say this with certainty, but I feel that both
Stefano Mazzocchi wrote:
Adam Jack wrote:
Two possible solutions here:
1) use forrest as a dynamic application
2) have HTML generate by python
I would go for 1) since it would keep us the ability to do dynamic
stuff like metadata manipulation.
I volunteer to setup 1)
+1 for dynamic
1) use forrest as a dynamic application
First, what do you mean by this, please? For those of us who don't know,
could somebody elaborate?
Second, I think it is forrest that is where we are getting stuck right now.
Now sure why, but it is locking up. So, if we want forest, we have to figure
Adam Jack wrote:
[snip]
I think it is forrest that is where we are getting stuck right now.
Now sure why, but it is locking up. So, if we want forest, we have to figure
out how to get inside that problem.
Which version are you using? Probably coincidence, but I recently
stopped using
CVS
Davey [EMAIL PROTECTED]
To: Gump code and data [EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 4:01 PM
Subject: Re: Gump Thrashing/Spinning...
Adam Jack wrote:
[snip]
I think it is forrest that is where we are getting stuck right now.
Now sure why, but it is locking up. So, if we want
17 matches
Mail list logo
