> From: Leo Simons [mailto:[EMAIL PROTECTED]] 
> 
> On Thu, 2002-07-18 at 10:56, Leo Sutic wrote:
> > > From: Peter Donald [mailto:[EMAIL PROTECTED]]
> >  + taking ages to build simple site (is it below 3 minutes yet?)
> > 
> > Cocoon is fast on my fast machine. But that's not really a 
> solution is 
> > it?
> 
> the new one is fast enough, if you ask me. It takes about 3 
> times longer than anakia.


the new one is about 1.5 to 2 minutes for every single subproject
in Excalibur.  My machine is fairly modest.


> >  + spammy output that makes it impossible to read build script
> > 
> > Yep. Can we limit the log level to WARN or ERROR? There are many
> > places in Cocoon where, for example, the lookup() method is used
> > instead of the hasComponent() method. Thus you get a WARN and a
> > huge stack trace even though nothing is wrong. But this is something
> > that can be fixed.
> 
> I suspect Berin will do so soon =)

No problem.


> >  + confusing setup (.uris vs sitebook vs xml pages vs xsl pages)
> > 
> > I'm sure we can do something about that.
> 
> I don't like the .uris. I think the setup should be


.uris isn't used, so you can safely remove them.


> - book.xml
> - documents using document-v10.dtd
> - non-documents inside same directory
> - optinal property file with a use.skin={bla} setup


The DTD docs are only required because of Xerces.  Xerces throws
an error if the DTD is not able to be read.  We can get rid of
the <!DOCTYPE > tags and the need for the DTD directories can go
away.

Book.xml vs. Project.xml--we can work with either.  I agree we
should use one of them.  We can make Project.xml work--so it really
isn't a problem.

Yesterday, I wanted to get this build to work so I could update the
site.


> > But, Peter, Berin, if this could be made to work, would it be 
> > acceptable for both of you?
> 
> the important part is not getting it to work but doing the 
> maintainance once it works, I think.


Like I said, I got the stuff working.  In another thread I said I
don't really care if we use Anakia or Cocoon to do the generation.
That really doesn't concern me one way or the other.  I am saying
that I don't want <div/> tags in my XML.  I want to use a DTD that
we #1 already agreed upon, and #2 represents the semantic intent
of the document better.

I *know* Anakia can work with the current DTD.  If it can't, then
we can supply a stylesheet to make the transformation at build time.
Either way I don't really care how it gets done.  I don't want an
unorganized and broken DTD.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to