Обсуждение: jade X openjade
In my Athon 1.7 512 MB RAM computer with Debian it takes 2m6s to generate de PostgreSQL 7.4.1 HTML documentation using JADE and 4m7s using OPENJADE (almost 2X). So why use OPENJADE ? Halley ______________________________________________________________________ Yahoo! Mail - O melhor e-mail do Brasil! Abra sua conta agora: http://br.yahoo.com/info/mail.html
Halley Pacheco de Oliveira wrote: > In my Athon 1.7 512 MB RAM computer with Debian it > takes 2m6s to generate de PostgreSQL 7.4.1 HTML > documentation using JADE and 4m7s using OPENJADE > (almost 2X). So why use OPENJADE ? I would have to double check, but I think OPENJADE offers better backend support. Personally I think the real question should be, Why *JADE*? We should be doing whatever it takes to move to XML/XSLT. Using Apache xerces I can transform a 1000 page document in less than a minute. J > > Halley > > ______________________________________________________________________ > > Yahoo! Mail - O melhor e-mail do Brasil! Abra sua conta agora: > http://br.yahoo.com/info/mail.html > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Вложения
Joshua D. Drake wrote: > Halley Pacheco de Oliveira wrote: > >> In my Athon 1.7 512 MB RAM computer with Debian it >> takes 2m6s to generate de PostgreSQL 7.4.1 HTML >> documentation using JADE and 4m7s using OPENJADE >> (almost 2X). So why use OPENJADE ? > > > I would have to double check, but I think OPENJADE offers better backend > support. > > Personally I think the real question should be, Why *JADE*? We should be > doing whatever it takes to move to XML/XSLT. > > Using Apache xerces I can transform a 1000 page document in less than a > minute. I have used xercess-C++ in my current project and I can tell you one thing. It's object model is broken. It is a fine API in general but the way it's object model is broken, makes me hate it.. really.. Given a better choice I wouldn't use it. But I haven't used any other XML toolkits either. My XML experience is pretty limited.. Shridhar
> I have used xercess-C++ in my current project and I can tell you one thing. It's > object model is broken. Well what I believe we are really after is Xalan which Xerces is required to run. I believe it is Xalan that actually does the XSLT transformations. > > It is a fine API in general but the way it's object model is broken, makes me > hate it.. really.. > > Given a better choice I wouldn't use it. But I haven't used any other XML > toolkits either. My XML experience is pretty limited.. > > Shridhar > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > -- Co-Founder Command Prompt, Inc. The wheel's spinning but the hamster's dead
-On [20040221 21:52], Joshua D. Drake (jd@commandprompt.com) wrote: >Well what I believe we are really after is Xalan which Xerces is required >to run. I believe it is Xalan that actually does the XSLT transformations. Correct. Xerces is the parser (both DOM and SAX). I have found Xerces+Xalan to find issues in my XML/XSLT 'code' which xsltproc didn't clearly label as wrong, whereas xsltproc understands EXSLT natively. -- Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono PGP fingerprint: 2D92 980E 45FE 2C28 9DB7 9D88 97E6 839B 2EAC 625B http://www.tendra.org/ | http://diary.in-nomine.org/ My name is Legion: for we are many...