DOM implementation
Frank Bennett
the demo page at:
http://gsl-nagoya-u.net/http/pub/citeproc-demo/demo.html
It's based on the Firefox DOM implementation. I gather that browsers
vary in their deserialization methods, so this may not yet work in
Explorer, Safari, etc. If you get an error, send it along and I'll
try to adjust the page to work with additional browsers.
The DOM implementation is not quite complete yet; functions used for
localized dates are not yet in there; but the basics seem to be
working.
Frank
Frank Bennett
http://gsl-nagoya-u.net/http/pub/citeproc-demo/demo.html now renders
in Google Chrome and Safari in addition to Firefox. Some small
details still need to be attended to (the mapping of formatting
attributes for CSL 1.0 localized dates, support for Internet
Explorer), but the processor is confirmed to run cross-platform on
browsers that implement the DOM.
Needless to say, this opens up some interesting possibilities for
running the processor client-side in browser-based authoriing systems.
Frank
Christian Boulanger
Frank
--
Group home: http://groups.google.com/group/citeproc-js?hl=en
To post: citep...@googlegroups.com
To unsubscribe: citeproc-js...@googlegroups.com
Citeproc-js home: home: http://bitbucket.org/fbennett/citeproc-js/wiki/Home
To unsubscribe, reply using "remove me" as the subject.
Frank Bennett
> I'm pleased to announce that the processor demo page athttp://gsl-nagoya-u.net/http/pub/citeproc-demo/demo.htmlnow renders
> in Google Chrome and Safari in addition to Firefox. Some small
> details still need to be attended to (the mapping of formatting
> attributes for CSL 1.0 localized dates, support for Internet
> Explorer), but the processor is confirmed to run cross-platform on
> browsers that implement the DOM.
>
> Needless to say, this opens up some interesting possibilities for
> running the processor client-side in browser-based authoriing systems.
One item I should have mentioned in my previous note is that the
bundled processor code has now been split into three modules:
xmle4x.js, xmldom.js, and citeproc.js. This was necessary to get
things working in Google Chrome/v8. Because GC precompiles all JS,
code with incompatible syntax (i.e. everything that is specific to
E4X) causes the entire module to fail. The demo page has been
adjusted to load things in the correct order (xml modules first, then
the processor). To run the latest code (checked in today), you'll
need to do the same in your app.
Frank
>
> Frank
Frank Bennett
> On Apr 15, 12:03 am, Frank Bennett <biercena...@gmail.com> wrote:
>
> > I'm pleased to announce that the processor demo page athttp://gsl-nagoya-u.net/http/pub/citeproc-demo/demo.htmlnowrenders
> > in Google Chrome and Safari in addition to Firefox. Some small
> > details still need to be attended to (the mapping of formatting
> > attributes for CSL 1.0 localized dates, support for Internet
> > Explorer), but the processor is confirmed to run cross-platform on
> > browsers that implement the DOM.
>
> > Needless to say, this opens up some interesting possibilities for
> > running the processor client-side in browser-based authoriing systems.
Internet Explorer 6.0 @ Windows XP (confirmed by Bennett)
Internet Explorer 8.0 @ Windows (confirmed by Zelle)
Firefox 3.6.3 @ Linux (confirmed by Bennett)
Firefox 3.6.3 @ Windows (confirmed by Zelle)
Safari 4.0.5 for Windows (confirmed by Zelle)
Seamonkey 1.1.9 (Gecko) @ Windows (confirmed by Zelle)
Chrome 4.1.249.1045 @ Windows Vista (confirmed by user ahab on the
Google Docs help forum)
Chrome 5.0.342.9 beta @ Linux (confirmed by Bennett)
As ever, the demo page (now equipped with the latest processor
version) is here:
http://gsl-nagoya-u.net/http/pub/citeproc-demo/demo.html
Enjoy!
Frank Bennett
Nagoya
2010.04.18
>
> One item I should have mentioned in my previous note is that the
> bundled processor code has now been split into three modules:
> xmle4x.js, xmldom.js, and citeproc.js. This was necessary to get
> things working in Google Chrome/v8. Because GC precompiles all JS,
> code with incompatible syntax (i.e. everything that is specific to
> E4X) causes the entire module to fail. The demo page has been
> adjusted to load things in the correct order (xml modules first, then
> the processor). To run the latest code (checked in today), you'll
> need to do the same in your app.
>
> Frank
>
>
>
> > Frank