RE: [Fwd: Xmlc: [Ann] Jivan 1.0 RC 1]
"Christian Cryder" <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
Ooh...very interesting! Looks like the main developer is Arno Schatz (who worked at Lutris about the same time I did). I will subscribe to their mailing list and take a closer look...it seems like we ought to be ably to integrate with this fairly easily (since it just supplies/renders the DOM)...one of the concerns I have is that its GPL, so I'm not sure exactly how that would integrate with Barracuda's EPL. But I will talk to Arno and find out... Thanks for bringing this to our attention, Denny (I never did see it on the XMLC list...hmmm?) Christian ---------------------------------------------- Christian Cryder Internet Architect, ATMReports.com Project Chair, BarracudaMVC - http://barracudamvc.org ---------------------------------------------- "Coffee? I could quit anytime, just not today" > -----Original Message----- > From: [email protected] > [mailto:[email protected]]On Behalf Of Denny Chambers > Sent: Tuesday, September 16, 2003 9:45 AM > To: Barracuda > Subject: [Barracuda] [Fwd: Xmlc: [Ann] Jivan 1.0 RC 1] > > > This looks pretty interesting, so I thought I would forward it over from > the XMLC list. > > -------- Original Message -------- > Subject: Xmlc: [Ann] Jivan 1.0 RC 1 > Date: Tue, 16 Sep 2003 13:08:34 +0200 > From: Arno Schatz <[email protected]> > Reply-To: [email protected] > To: [email protected], [email protected] > > > > Hi, > > I have been working on the Jivan Project (www.jivan.org) for a > while, It is an open > source project. Similar to XMLC it can parse HTML, lets you > manipulate the HTML DOM and > can seialize the result. It is optimized for use in web applications. > > There were 3 reasons to write Jivan and not use xmlc for HTML pages: > - performance: Jivan is more than 3 times faster in table > replication (see > www.jivan.org for performance result) > - ease of use: Jivan doesn't compile anything and does not need > to be included in the > build process (hence no ant taskdef neccessary) > - dealing with invalid HTML: Jivan leaves the HTML page as it > is, except those places > you dynamically change. Jivan parses almost any HTML without > fixing (unlike xmlc). While > serialisation, for all nodes (and subtrees) which are not touched > by the programmer, > Jivan will copy the coresponding HTML string from the supplied > template directly to the > output. > > > Jivan uses the latest form Apache.org: Xerces-2 and nekoHTML. > > Similar to xmlc, you manipulate the web-page through the standard > interfaces from W3C DOM > for HTML. > > check it out at www.jivan.org and give me some feedback, > Arno > > > _______________________________________________ > XMLC mailing list > [email protected] > http://www.enhydra.org/mailman/listinfo.cgi/xmlc > > > >