unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil-0S17iFHR5lf2/9iHc7UuXF6hYfS7NtTn@public.gmane.org>
Cc: guile-user-mXXj517/zsQ@public.gmane.org,
	ssax-sxml-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ANN: SDOM project development release 0.4
Date: Sat, 31 Dec 2005 13:40:22 +0000	[thread overview]
Message-ID: <87lky1bd15.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <2bc5f8210512290724i505b05e3lae7b3eb75653a4d4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Julian Graham's message of "Thu, 29 Dec 2005 10:24:15 -0500")

Julian Graham <joolean-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Hi Neil,
>   Well, maybe I don't understand the question, but I'd say you could
> use SDOM pretty much anywhere you'd use, say, JDOM,

I'm afraid that doesn't help me much ... unless there are JDOM
applications that I could refer to as examples?

> but wanted to use
> Scheme instead of Java.  Granted, the most popular application of the
> DOM is in web browsers alongside (X)HTML, but I find it's quite handy
> for doing high-level manipulation of XML documents in general.

But isn't everything event-driven?  As in, execute so-and-so script on
so-and-so objects when I click on this link?  And in that case, don't
you need something that amounts to a web browser (or at least, an
HTML/XML page renderer) to exercise the DOM?

>  I know
> some people have strong feelings about the isomorphism between XML and
> S-expressions that SXML exploits and that SDOM kind of runs counter to
> that, but it also provides a few features that SSAX doesn't -- and
> that I needed for the projects I'm working on -- such as the event
> handling stuff and a stronger type system for XML nodes.

That's rather over my head, so definitely not a concern of mine :-)

Regards,
        Neil



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

  parent reply	other threads:[~2005-12-31 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04 19:12 ANN: SDOM project development release 0.4 Julian Graham
     [not found] ` <2bc5f8210512041112k5bf277e9vb9ebba673c14c9e8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-12-28 15:40   ` Neil Jerram
     [not found]     ` <874q4tmdq5.fsf-0S17iFHR5lf2/9iHc7UuXF6hYfS7NtTn@public.gmane.org>
2005-12-29 15:24       ` Julian Graham
     [not found]         ` <2bc5f8210512290724i505b05e3lae7b3eb75653a4d4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-12-29 16:08           ` klaus schilling
2005-12-30 20:46             ` Julian Graham
2005-12-31 13:40           ` Neil Jerram [this message]
     [not found]             ` <87lky1bd15.fsf-0S17iFHR5lf2/9iHc7UuXF6hYfS7NtTn@public.gmane.org>
2005-12-31 16:53               ` Julian Graham
2006-01-09 22:00                 ` Neil Jerram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lky1bd15.fsf@ossau.uklinux.net \
    --to=neil-0s17ifhr5lf2/9ihc7uuxf6hyfs7nttn@public.gmane.org \
    --cc=guile-user-mXXj517/zsQ@public.gmane.org \
    --cc=ssax-sxml-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).