tclxml-users — Discussion on using the TclXML package

[Tclxml-users] Re: MetaKit+BLT+Expat+...

[Steve B. <Ste...@zv...>]

Shawn Freeman wrote:
> 
> Has anyone ever built a wish that had BLT+MetaKit+Expat all statically
> linked in? I know that TclKit is out there, but would also like the
> plotting and XML capabilities.

From the XML pov, it sounds good!  Of course, at the moment I
simply use the pure-Tcl XML parser in TclKit.  Of course, it
would be nice to have the faster expat available.  Ditto for
TclDOM.

Unfortunately, the C version of TclXML v2.0 still hasn't had the
panic-dump bugs fixed.  If anyone is able to lend a hand here,
please contact Peter Farmer (Pet...@zv...).

Cheers,
Steve Ball

-- 
Steve Ball            | waX Me Lyrical XML Editor | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |      XML XSL
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

[Tclxml-users] Re: [tclxml] dtd's

[Steve B. <Ste...@zv...>]

Steve Szabo wrote:
> 
> can tclxml parse dtd's and generate the xml?
>

TclXML can indeed parse DTDs - see the -elementdeclcommand,
-attlistdeclcommand, -entitydeclcommand and -notationdeclcommand
options.

However, TclXML cannot "generate" the XML.  My TODO list has an
item to create a Tcl package which reads the DTD and creates
Tcl commands corresponding to each element type, but alas I
have not yet got around to working on that.

HTHs,
Steve Ball

-- 
Steve Ball            | waX Me Lyrical XML Editor | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |      XML XSL
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

Re: [Tclxml-users] tcldompro.c

[Steve B. <Ste...@zv...>]

Joe English wrote:
> 
> > > You need to create a root element node before serializing the
> > > document; things should work properly then.
> >
> > So how do I create a "root element"?
> 
> Ah, now I see the problem: one of the main differences between
> dom::tcl and dom::c is that, in dom::tcl,
> 
>     dom::document createXXX $parent ...
> 
> adds the new node as a child of $parent, whereas
> dom::c creates it as an unattached, parentless node.
> You have to add the new node "by hand", e.g.,:
> 
>     dom::node appendChild $parent [dom::document createXXX $parent ...]
> 
> The dom::tcl behaviour is more intuitive and useful,
> but the dom::c behaviour matches the W3C DOM specification
> more closely.  When I last asked Steve about this he
> indicated that it would be best to follow the W3C spec.
> 
> Steve - is this still your take on things, or would
> it be better to change dom::c to match the documentation
> and dom::tcl?

After some time for reflection, I think we'll stick with the
non-standard feature.  If users want to, they can use TclDOM
in such a manner that it is standard (ie. create node using
factory method, then insert).

My plan for TclDOM is to make a 'theta' release like I did
for TclXML.  That work will involve bringing the C and Tcl
implementations into sync, as well as perhaps adding support
for tDOM-style features, like more OO style node commands.
Of course, we'll throw in DOM Level 2 and 3 support for 
good measure ;-)

Now I just have to find the time...

Cheers,
Steve Ball

-- 
Steve Ball            | waX Me Lyrical XML Editor | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |      XML XSL
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

Re: [Tclxml-users] why won't TclXML parse this?

[Steve B. <Ste...@zv...>]

Todd Bradley wrote:
> 
> I'm by no means an XML expert, so this may be a stupid
> question, but I was wondering why the TclXML parser
> chokes on something like this:
> 
> <foo bar='Black &amp; White'/>

Yes, that is well-formed XML.  To answer other responders who
said 'just avoid entity references in attribute values' you can't:
if you want both a single and double quote in the value, or a 
'<' character, then you must be able to use entity references.

> The &amp; is giving ParseCommand fits.  If I take out
> the &amp; then things work fine.
[...snip...]
> Possibly relevant version numbers from xml.tcl:
> 
> package provide xml 1.9
> 
> package require sgml 1.7

The behaviour you are observing is a bug that has been fixed.
Get the latest code, TclXML v2.0theta, and try it again.

However, that's not the whole story.  The current version of
TclXML can handle the predefined entities, lt, gt, quot, apos, amp,
as well as character entities (&#60;), but it cannot handle
general entities.  Unfortunately, this makes the parser 
non-conformant :-(  One could argue that it is a non-validating
parser and therefore is not obliged to read DTDs, but that argument
fails since a non-validating parser is expected to read the
internal DTD.

Thus the following should parse correctly:

<!DOCTYPE Sample [
  <!ENTITY example "excellent">
]>
<Sample>
  <Example value="an &example; value"/>
</Sample>

The 'value' attribute of the 'Example' element should have the
value 'an excellent value', but doesn't.  Someone should submit
a bug report on this (hint...).

HTHs,
Steve Ball

-- 
Steve Ball            | waX Me Lyrical XML Editor | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |      XML XSL
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

Re: [Tclxml-users] tcldompro.c

[Lee T. <lee...@pl...>]

you, my friend, kick ass.

thank you.
----- In reply to "Re: [Tclxml-users] tcldompro.c" from Joe English <jen...@fl...> -----
> 
> 
> I've just updated the dom::c package to make it compatible
> with dom::tcl and the TclDOM documentation:
> [dom::document createXXX $node1 ...] now creates the new node
> as a child of $node1.
> 
> This is largely compatible with the old dom::c behavior --
> typical usage is to insert nodes at the right point in the tree
> immediately after creating them, and scripts that do so will
> still work the same since the implementation automatically unlinks and
> reparents the new node.  The test suite still passes, so I'm
> fairly confident that this change won't break anything.
> 
> There's also a compile-time option (-DW3C_CONSTRUCTOR_BEHAVIOR)
> to get the old behaviour back.
> 
> Lee -- can you get a fresh copy from Sourceforge CVS and
> see if that works now?
> 
> 
> --Joe English
> 
>   jen...@fl...
> 

-- 
Lee Teague
Placemark Investments
972.404.8100x31  |  lee...@pl...

Re: [Tclxml-users] tcldompro.c

[Joe E. <jen...@fl...>]

I've just updated the dom::c package to make it compatible
with dom::tcl and the TclDOM documentation:
[dom::document createXXX $node1 ...] now creates the new node
as a child of $node1.

This is largely compatible with the old dom::c behavior --
typical usage is to insert nodes at the right point in the tree
immediately after creating them, and scripts that do so will
still work the same since the implementation automatically unlinks and
reparents the new node.  The test suite still passes, so I'm
fairly confident that this change won't break anything.

There's also a compile-time option (-DW3C_CONSTRUCTOR_BEHAVIOR)
to get the old behaviour back.

Lee -- can you get a fresh copy from Sourceforge CVS and
see if that works now?


--Joe English

  jen...@fl...

[Tclxml-users] do not subscribe

[<hy...@sa...>]

ZG8gbm90IHN1YnNjcmliZQ0K

Re: [Tclxml-users] tcldompro.c

[Lee T. <lee...@pl...>]

here's the source:

http://www.placemark.com/~lee/ns_tcldom.tar.gz

just untar it into your aolserver source tree, or set NS_HOME in the Makefile to
the location of your source tree.


here's what we had to change:

of course the Makefile to work with aolserver modules, etc. (didn't have to, but
it made it so much nicer...)


the following lines in tcldompro.c were added/replaced:

---------------------------------------------
#include "ns.h"
...



int Ns_ModuleInit(char *hServer, char *hModule)
{
   /* AOLserver doesn't deal well with namespaces in C modules
    * so we need to reinitialize this module everytime a new
    * interp thread is created by AOLserver.
    */
   Ns_TclRegisterAtCreate ( tcldominit, NULL);

   return (Ns_TclInitInterps(hServer, tcldominit, NULL));
}  



///// in tcldominit:

static int tcldominit( Tcl_Interp *interp, void *context )
....

    //return Tcl_PkgProvide(interp, PACKAGE_NAME, VERSION);
      return NS_OK;


---------------------------------------------

If you run through the code, you may notice a few other small differences, but
the big one was "Ns_ModuleInit".  The pain in the neck was figuring out that we
had to use "Ns_TclRegisterAtCreate" to make it reload the commands with every
thread.  This isn't loading the file, it's just calling "Tcl_CreateObjCommand" a
few times with every thread.


Note:  this isn't done, I'm writing this mailing list because we're having
problems with it.  Hopefully this will be of some use to someone, or maybe it'll
help someone help us with this problem.

BIG thanks to Jeremy Collins for making this work.

- Lee Teague


----- In reply to "Re: [Tclxml-users] tcldompro.c" from Dave Bauer <da...@ki...> -----
> Wow,
> 
> I am very interested in an AOLserver module with TclDOM. Do you mind sharing
> the code or how you accomplished this feat?
> 
> Right now we are using ns_xml with is a AOLserver module using libxml2 for
> OpenACS, but the interface is very basic. TclDOM has a really nice interface
> on the other hand, but the TCL version is slow.
> Thanks
> 
> Dave Bauer
> da...@th...
> 
> ----- Original Message -----
> From: "Lee Teague" <lee...@pl...>
> To: <tcl...@li...>
> Sent: Tuesday, May 08, 2001 3:50 PM
> Subject: [Tclxml-users] tcldompro.c
> 
> 
> > Hi -
> >
> > I've been working with your tcldom package, and I'm impressed!  The tcl
> xml
> > parser seemed a little slow with large arrays (85 elements) so I've been
> looking
> > into the C version (tcldompro.c).  I've got it compiled as an AOLServer
> module,
> > and it seemed to be working fine (we had a little trouble getting it to
> compile
> > with namespaces, but we figured it out.  I'll send you a patch if you
> want), but
> > I do have a question:  Does dom::DOMImplementation behave differently with
> the C
> > version?  Here's what I'm trying to do:
> >
> >
> > with the tcl version:
> >
> > %set doc [dom::DOMImplementation create]
> > ::dom::document1(node1)
> >
> > the C version:
> >
> > %set doc [dom::DOMImplementation create]
> > node9
> >
> >
> > with the tcl version, I can then take $doc and run "dom::DOMImplementation
> > serialize" on it to create the xml.  But, with the C version, it says,
> "document
> > has no document element"
> >
> > Also, with the TCL version, doing a "namespace eval ::dom { info vars }"
> gives
> > me "document1" (the array in the above case) and "document1var1", etc.
> The C
> > version does not.
> >
> > Thanks for *any* light you can shed on this.
> >
> >
> >
> > Lee Teague
> >
> >
> > --
> > Lee Teague
> > Placemark Investments
> > lee...@pl...
> >
> > _______________________________________________
> > Tclxml-users mailing list
> > Tcl...@li...
> > http://lists.sourceforge.net/lists/listinfo/tclxml-users
> >
> 
> 

-- 
Lee Teague
Placemark Investments
972.404.8100x31  |  lee...@pl...

Re: [Tclxml-users] tcldompro.c

[Joe E. <jen...@fl...>]

> > You need to create a root element node before serializing the
> > document; things should work properly then.
>
> So how do I create a "root element"?

Ah, now I see the problem: one of the main differences between
dom::tcl and dom::c is that, in dom::tcl,

    dom::document createXXX $parent ...

adds the new node as a child of $parent, whereas
dom::c creates it as an unattached, parentless node.
You have to add the new node "by hand", e.g.,:

    dom::node appendChild $parent [dom::document createXXX $parent ...]

The dom::tcl behaviour is more intuitive and useful,
but the dom::c behaviour matches the W3C DOM specification
more closely.  When I last asked Steve about this he
indicated that it would be best to follow the W3C spec.

Steve - is this still your take on things, or would
it be better to change dom::c to match the documentation
and dom::tcl?



--Joe English

  jen...@fl...

Re: [Tclxml-users] tcldompro.c

[Lee T. <lee...@pl...>]

I actually am using some of that package.  It requires tclxml.  What i'm trying
to do is a little more specialized than what that package does, so I'm having to
write some of the DOM stuff directly.  


----- In reply to "Re: [Tclxml-users] tcldompro.c" from Daniel <da...@co...> -----
> Hi,
> 
> Since you are using soap, you may be interested in:
> http://www.zsplat.freeserve.co.uk/soap/doc/TclSOAP.html
> 
> > 
> > ---------  CODE THAT WORKS WITH THE TCL VERSION -------------------
> > 
> >         set methodName "get_state"
> > 
> >    set doc [dom::DOMImplementation create]
> > 
> >    set env [dom::document createElement $doc "SOAP-ENV:Envelope"]
> 
> -- 
> da...@co...    "Fortuna audaces juvat"
> 
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> http://lists.sourceforge.net/lists/listinfo/tclxml-users
> 

-- 
Lee Teague
Placemark Investments
972.404.8100x31  |  lee...@pl...

Re: [Tclxml-users] tcldompro.c

[Daniel <da...@co...>]

Hi,

Since you are using soap, you may be interested in:
http://www.zsplat.freeserve.co.uk/soap/doc/TclSOAP.html

> 
> ---------  CODE THAT WORKS WITH THE TCL VERSION -------------------
> 
>         set methodName "get_state"
> 
>    set doc [dom::DOMImplementation create]
> 
>    set env [dom::document createElement $doc "SOAP-ENV:Envelope"]

-- 
da...@co...    "Fortuna audaces juvat"

Re: [Tclxml-users] tcldompro.c

[Lee T. <lee...@pl...>]

----- In reply to "Re: [Tclxml-users] tcldompro.c" from Joe English <jen...@fl...> -----
> 
> Lee Teague <lee...@pl...> wrote:
> 
> > Here's what I'm trying to do:
> > with the tcl version:
> > %set doc [dom::DOMImplementation create]
> > ::dom::document1(node1)
> >
> > the C version:
> > %set doc [dom::DOMImplementation create]
> > node9
> >
> > with the tcl version, I can then take $doc and run "dom::DOMImplementation
> > serialize" on it to create the xml.  But, with the C version, it says, "document
> > has no document element"
> 
> That's odd; the Tcl version gives me the same error as the C version
> ("document has no document element").  What version of dom::tcl do you
> have installed?
> 
> You need to create a root element node before serializing the
> document; things should work properly then.
> 


So how do I create a "root element"?  With the TCL version, all my code works
fine, but with this C version, it complains about "no document element".  I'll
include a code snippet at the bottom of this msg to show you exactly what's
happening.  Again, the TCL version creates the XML just fine like this.


Thanks for your help!



---------  CODE THAT WORKS WITH THE TCL VERSION -------------------


	set methodName "get_state"

   set doc [dom::DOMImplementation create]
   
   set env [dom::document createElement $doc "SOAP-ENV:Envelope"]

   dom::element setAttribute $env "xmlns:SOAP-ENV" "http://schemas.xmlsoap.org/soap/envelope/"
   dom::element setAttribute $env "xmlns:xsi" "http://www.w3.org/1999/XMLSchema-instance"
   dom::element setAttribute $env "xmlns:xsd" "http://www.w3.org/1999/XMLSchema"

   set bod [dom::document createElement $env "SOAP-ENV:Body"]
   
   set cmd [dom::document createElement $bod $methodName]
   
   dom::element setAttribute $cmd "SOAP-ENV:encodingStyle" "http://schemas.xmlsoap.org/soap/encoding/"


   set par [dom::document createElement $cmd state]
   dom::element setAttribute $par "xsi:type" "xsd:string"
   dom::document createTextNode $par Texas

   regsub {<!DOCTYPE[^>]*>\n} [dom::DOMImplementation serialize $doc] {} result
   dom::DOMImplementation destroy $doc

	return $result

---------  CODE THAT WORKS WITH THE TCL VERSION  ------------------

--------------  XML RESULT FROM TCL VERSION  ----------------------

<?xml version='1.0'?>

<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
	<SOAP-ENV:Body>
		<get_state SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
			<state xsi:type="xsd:string">
				Texas
			</state>
		</get_state>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

--------------  XML RESULT FROM TCL VERSION  ----------------------



--
Lee Teague
Placemark Investments
lee...@pl...

Re: [Tclxml-users] tcldompro.c

[Joe E. <jen...@fl...>]

Lee Teague <lee...@pl...> wrote:

> I've got [dom::c] compiled as an AOLServer module,
> and it seemed to be working fine (we had a little trouble getting it to compile
> with namespaces, but we figured it out.  I'll send you a patch if you want)

Do you mean Tcl namespaces, XML namespaces, or C++ namespaces?
Or something else?  At any rate, yes, please send a patch and I'll
get it integrated.  What problems did you run into?


> I do have a question:  Does dom::DOMImplementation behave differently with the C
> version?

Probably.  Any differences in documented functionality should be considered
a bug though.  (There are many differences in implementation details - like
the representation of nodes - but those are inconsequential).


> Here's what I'm trying to do:
> with the tcl version:
> %set doc [dom::DOMImplementation create]
> ::dom::document1(node1)
>
> the C version:
> %set doc [dom::DOMImplementation create]
> node9
>
> with the tcl version, I can then take $doc and run "dom::DOMImplementation
> serialize" on it to create the xml.  But, with the C version, it says, "document
> has no document element"

That's odd; the Tcl version gives me the same error as the C version
("document has no document element").  What version of dom::tcl do you
have installed?

You need to create a root element node before serializing the
document; things should work properly then.

I think that raising an error is the correct behaviour in this case. 
The documentation for [dom::DOMImplementation serialize] 
says that "the text is guaranteed to be a well-formed XML document",
and there's no way to meet that guarantee unless there's exactly one 
document element.


> Also, with the TCL version, doing a "namespace eval ::dom { info vars }" gives
> me "document1" (the array in the above case) and "document1var1", etc.  The C
> version does not.

That's one of the inconsequential implementation details mentioned above :-)
The C version stores the tree in an internal data structure,
where the Tcl version uses Tcl variables in the ::dom namespace.


--Joe English

  jen...@fl...

[Tclxml-users] tcldompro.c

[Lee T. <lee...@pl...>]

Hi -

I've been working with your tcldom package, and I'm impressed!  The tcl xml
parser seemed a little slow with large arrays (85 elements) so I've been looking
into the C version (tcldompro.c).  I've got it compiled as an AOLServer module,
and it seemed to be working fine (we had a little trouble getting it to compile
with namespaces, but we figured it out.  I'll send you a patch if you want), but
I do have a question:  Does dom::DOMImplementation behave differently with the C
version?  Here's what I'm trying to do:


with the tcl version:

%set doc [dom::DOMImplementation create]
::dom::document1(node1)

the C version:

%set doc [dom::DOMImplementation create]
node9


with the tcl version, I can then take $doc and run "dom::DOMImplementation
serialize" on it to create the xml.  But, with the C version, it says, "document
has no document element"

Also, with the TCL version, doing a "namespace eval ::dom { info vars }" gives
me "document1" (the array in the above case) and "document1var1", etc.  The C
version does not.

Thanks for *any* light you can shed on this.



Lee Teague


-- 
Lee Teague
Placemark Investments
lee...@pl...

Re: [Tclxml-users] why won't TclXML parse this?

[Peter F. <pet...@zv...>]

Mats Bengtsson wrote:
> 
> Peter Farmer wrote
> > And the tclxml list has been awfully quite , it seems there's not much
> > interest . It would be nice to know if anyone's using it seriously  - it
> > cant be that good that no-one finds fault or lack with it 8-).
> 
> Just to tell you that there is interest in TclXML. Using it to learn
> my whiteboard ("http://hem.fyristorg.com/matben") to talk XML to the
> jabber IM server system (jabber.org). So, keep up the good work!

Thanks. We will try to 8-)
Jabber again. I'm amazed how keen are to talk to each other 8-). I must
say  I'm looking forward to realtime s/w dvelopment collaboration on SF
projects with jabber whiteboards and the like 8-)

> The sad(?) thing is that if things are working well, you never hear
> from anyone; it's first when there are problems people take contact.
> This thread is an example of that.
>

Well I know a few things that need work. And I guess I've got enough w/o
asking for more 8-)



-- 
Peter Farmer            |  Custom XML software   | Internet Engineering 
Zveno Pty Ltd           | Website XML Solutions  | Training & Seminars
http://www.zveno.com/   |   Open Source Tools    |   - XML XSL Tcl
Pet...@zv...  +------------------------+---------------------
Ph. +61 8 92434146      | Mobile +61 417 906 851 | Fax +61 2 6242 4099

Re: [Tclxml-users] why won't TclXML parse this?

[Peter F. <pet...@zv...>]

Todd,

I have tried to write this three time and lost it when almost finished,
when Netscrape crashed. urk. So my tries at reply have been getting
briefer .. 

> 
> > One of the reasons I do (apart from never having needed to use them  )
> > is that TclXML doesnt support them yet 8-). Its not a bug, its a
> > _missing_ feature ....  At the moment I dont know when it
> > will added. It
> > depends on how much demand for it there is and how much time
> > we can make
> > to work on it. Some paying clients have our almost undivided attention
> > at the moment 8-).
> 
> Fair enough, I suppose.

No, its not really. Its not good having to admit that a basic compliance
feature is missing . But we seem to be short handed at the moment.

 .. Todd's nicely done briefing on Jabber and its workings omitted here
...

> 
> So, given this Resource field to play with,
> some users inevitably decide to put funky
> things like ampersands in there, such as
> 
> "bu...@ja.../Black & White"
> 

doh! users! $@&%$!#@!

> The ampersand gets converted to "&" in
> the XML data stream, and then that has to
> be parsed correctly by the client program
> on the receiving end.
> 
> See here for more:
> http://docs.jabber.org/jpg/html/main.html#CH-ENTITY-TIER-RESOURCE
> 
> Right now, any user who tries to get update
> information from our Jabber server or who
> tries to chat with Jabberbot and has a re-
> source with an ampersand generates XML which
> cannot be parsed by the TclXML parser.
> 
> I've gotten around the problem by just ignoring
> those users for now, which isn't very polite,
> but at least my Expect script doesn't crash.
> I could do something hokey like scan the XML
> for something that looks like a resource, chop
> it off, pass the XML to the parser, and then
> re-insert the resource afterwards.  But I'm
> sure you'll agree that isn't a very elegant
> solution.
> 

agreed ;-)

> So, there you go.  That's what I use TclXML
> for.
> 
> Todd.

Thanks for the feedback Todd. Jabber is cool, and for some of our
favourite reasons (OS, XML, TCL). I hope we'll be able to get this fixed
for you as soon as we can.
Its interesting how Tcl does seem to have found a real niche in the
IRC/Chat/Instant Messaging world.
 

-- 
Peter Farmer            |  Custom XML software   | Internet Engineering 
Zveno Pty Ltd           | Website XML Solutions  | Training & Seminars
http://www.zveno.com/   |   Open Source Tools    |   - XML XSL Tcl
Pet...@zv...  +------------------------+---------------------
Ph. +61 8 92434146      | Mobile +61 417 906 851 | Fax +61 2 6242 4099

Re: [Tclxml-users] why won't TclXML parse this?

[Mats B. <ma...@pr...>]

Peter Farmer wrote
> And the tclxml list has been awfully quite , it seems there's not much
> interest . It would be nice to know if anyone's using it seriously  - it
> cant be that good that no-one finds fault or lack with it 8-).

Just to tell you that there is interest in TclXML. Using it to learn
my whiteboard ("http://hem.fyristorg.com/matben") to talk XML to the
jabber IM server system (jabber.org). So, keep up the good work!
The sad(?) thing is that if things are working well, you never hear
from anyone; it's first when there are problems people take contact.
This thread is an example of that.

Mats Bengtsson

RE: [Tclxml-users] why won't TclXML parse this?

[Todd B. <TBr...@ja...>]

Peter Farmer wrote:
> Your correct that it is valid XML . Entities are allowed in 
> attributes,
> though I'd personally steer clear of them. 

Unfortunately, I have no control over that, as 
I'll explain below.

> One of the reasons I do (apart from never having needed to use them  )
> is that TclXML doesnt support them yet 8-). Its not a bug, its a
> _missing_ feature ....  At the moment I dont know when it 
> will added. It
> depends on how much demand for it there is and how much time 
> we can make
> to work on it. Some paying clients have our almost undivided attention
> at the moment 8-).

Fair enough, I suppose.

> And the tclxml list has been awfully quite , it seems there's not much
> interest . It would be nice to know if anyone's using it 
> seriously  - it
> cant be that good that no-one finds fault or lack with it 8-).

I'm using it fairly seriously.  Here's what 
I do with TclXML.

First, some background.  In case you have
never heard of it, there's an open source
instant messaging system called Jabber
(www.jabber.org).  The Jabber movement has
been gaining a great deal of momentum over
the past few months and there are now some-
thing like 50,000 independent Jabber servers
around the world.  I work at Jabber.com,
which exists to provide commercial software
and services to add to the Jabber network.

Other than the facts that Jabber is open
source, is instant messaging independent
of Microsoft, Yahoo!, and AOL, the coolest
thing about Jabber is that the protocol is
all XML.

Before I got involved in Jabber, someone wrote
a Tcl/Tk Jabber client called zABBER, which I
have since taken over maintenance of (what
little maintenance there is--the client is
best described as "alpha" quality and hardly
anybody uses it, so I haven't been adding new
features or fixing bugs).  Recently, though, I 
have written several utilities in Tcl (using 
Expect) to act as specialized Jabber client 
programs and server side components.  

Two of the most used Tcl programs I've written
are called "Jabberbot" and "updateagent".  The
first is a chat bot for use at Jabber.com's
public Jabber server.  It receives and automat-
ically responds to instant messages from users, 
including handling some very basic tech support 
issues on its very own!  The second is a service 
that also runs on Jabber.com's public Jabber 
server and tells Jabber clients when there is a 
new version of themselves available for download.

Both of these programs are Expect scripts and
both use TclXML to parse the XML data stream
coming from Jabber clients and server compon-
ents.  The Jabber protocol says that each user
in the Jabber network will have a unique Jabber
ID.  This ID looks a lot like an email address.
For instance, my Jabber ID right now is:

"tbr...@ja.../WorkJIM"

As with email, the tbr...@ja... means
that my username is tbradley and I use the
jabber.com Jabber server.  The stuff after
the slash ("/WorkJIM") is called a "resource"
and is user configurable to give a unique
description of where you're connecting from.
So, unlike ICQ and other IM systems, you can
actually be connected to the Jabber network
multiple times.  For instance, I might be con-
nected on my work PC and on my cell phone and
on my home PC all at the same time.  So, I
might be simultaneously using JIDs of:

"tbr...@ja.../Work PC"
"tbr...@ja.../Nokia 5900"
"tbr...@ja.../Home PC"

So, given this Resource field to play with,
some users inevitably decide to put funky 
things like ampersands in there, such as

"bu...@ja.../Black & White"

The ampersand gets converted to "&" in
the XML data stream, and then that has to
be parsed correctly by the client program 
on the receiving end.

See here for more:
http://docs.jabber.org/jpg/html/main.html#CH-ENTITY-TIER-RESOURCE

Right now, any user who tries to get update
information from our Jabber server or who 
tries to chat with Jabberbot and has a re-
source with an ampersand generates XML which
cannot be parsed by the TclXML parser.  

I've gotten around the problem by just ignoring 
those users for now, which isn't very polite,
but at least my Expect script doesn't crash.  
I could do something hokey like scan the XML 
for something that looks like a resource, chop 
it off, pass the XML to the parser, and then 
re-insert the resource afterwards.  But I'm 
sure you'll agree that isn't a very elegant 
solution.

So, there you go.  That's what I use TclXML
for.


Todd.

Re: [Tclxml-users] why won't TclXML parse this?

[Peter F. <pet...@zv...>]

Tom,

Your correct that it is valid XML . Entities are allowed in attributes,
though I'd personally steer clear of them. 

One of the reasons I do (apart from never having needed to use them  )
is that TclXML doesnt support them yet 8-). Its not a bug, its a
_missing_ feature ....  At the moment I dont know when it will added. It
depends on how much demand for it there is and how much time we can make
to work on it. Some paying clients have our almost undivided attention
at the moment 8-).
And the tclxml list has been awfully quite , it seems there's not much
interest . It would be nice to know if anyone's using it seriously  - it
cant be that good that no-one finds fault or lack with it 8-).


Peter


Todd Bradley wrote

> 
> The semicolon is necessary.  "&" is what's called
> a "predefined entity" and is the XML of representing
> the "&" character.  The other four predefined entities
> are:
> 
> &lt;   which means <
> &gt;   which means >
> &apos; which means '
> &quot; which means "
> 
> So, I THINK this is valid XML, but TclXML doesn't like
> it at all!
> 
> Todd.
> 
> > -----Original Message-----
> > From: James C. Moore [mailto:jm...@qn...]
> > Sent: Thursday, May 03, 2001 4:17 PM
> > To: Todd Bradley; 'tcl...@li...'
> > Subject: Re: [Tclxml-users] why won't TclXML parse this?
> >
> >
> > I'm pretty sure you are not allowed to use semicolons.    My
> > xml is a little
> > rusty, though.
> >
> > > I'm by no means an XML expert, so this may be a stupid
> > > question, but I was wondering why the TclXML parser
> > > chokes on something like this:
> > >
> > > <foo bar='Black &amp; White'/>
> > >
> > > The &amp; is giving ParseCommand fits.  If I take out
> > > the &amp; then things work fine.
> > >
> > > The trace I'm getting looks like this:
> > >
> > > {invalid attribute list} around line 0
> > >     while executing
> > > "::sgml::Error {invalid attribute list} around line 0"
> > >     ("uplevel" body line 1)
> > >     invoked from within
> > > "uplevel #0 $options(-errorcommand) [list $attr around line
> > $state(line)]"
> > >     (procedure "ParseEvent:ElementOpen" line 21)
> > >     invoked from within
> > > "ParseEvent:ElementOpen $tag $param options -empty 1"
> > >     ("*,0,,/" arm line 5)
> > >     invoked from within
> > > "switch -glob -- [string length $tag],[regexp {^\?|!.*}
> > $tag],$close,$empty
> > > {
> > >
> > >             0,0,, {
> > >                 # Ignore empty tag - dealt with non-normal
> > mode above
> > >           ..."
> > >     (procedure "::sgml::parseEvent" line 118)
> > >
> > >
> > >
> > > Possibly relevant version numbers from xml.tcl:
> > >
> > > package provide xml 1.9
> > >
> > > package require sgml 1.7
> > >
> > >
> > >

-- 
Peter Farmer            |  Custom XML software   | Internet Engineering 
Zveno Pty Ltd           | Website XML Solutions  | Training & Seminars
http://www.zveno.com/   |   Open Source Tools    |   - XML XSL Tcl
Pet...@zv...  +------------------------+---------------------
Ph. +61 8 92434146      | Mobile +61 417 906 851 | Fax +61 2 6242 4099

RE: [Tclxml-users] why won't TclXML parse this?

[Todd B. <TBr...@ja...>]

The semicolon is necessary.  "&" is what's called
a "predefined entity" and is the XML of representing
the "&" character.  The other four predefined entities 
are:

&lt;   which means <
&gt;   which means >
&apos; which means '
&quot; which means "

So, I THINK this is valid XML, but TclXML doesn't like
it at all!


Todd.

> -----Original Message-----
> From: James C. Moore [mailto:jm...@qn...]
> Sent: Thursday, May 03, 2001 4:17 PM
> To: Todd Bradley; 'tcl...@li...'
> Subject: Re: [Tclxml-users] why won't TclXML parse this?
> 
> 
> I'm pretty sure you are not allowed to use semicolons.    My 
> xml is a little
> rusty, though.
> 
> > I'm by no means an XML expert, so this may be a stupid
> > question, but I was wondering why the TclXML parser
> > chokes on something like this:
> > 
> > <foo bar='Black &amp; White'/>
> > 
> > The &amp; is giving ParseCommand fits.  If I take out
> > the &amp; then things work fine.
> > 
> > The trace I'm getting looks like this:
> > 
> > {invalid attribute list} around line 0
> >     while executing
> > "::sgml::Error {invalid attribute list} around line 0"
> >     ("uplevel" body line 1)
> >     invoked from within
> > "uplevel #0 $options(-errorcommand) [list $attr around line 
> $state(line)]"
> >     (procedure "ParseEvent:ElementOpen" line 21)
> >     invoked from within
> > "ParseEvent:ElementOpen $tag $param options -empty 1"
> >     ("*,0,,/" arm line 5)
> >     invoked from within
> > "switch -glob -- [string length $tag],[regexp {^\?|!.*}
> $tag],$close,$empty
> > {
> > 
> >             0,0,, {
> >                 # Ignore empty tag - dealt with non-normal 
> mode above
> >           ..."
> >     (procedure "::sgml::parseEvent" line 118)
> > 
> > 
> > 
> > Possibly relevant version numbers from xml.tcl:
> > 
> > package provide xml 1.9
> > 
> > package require sgml 1.7
> > 
> > 
> > 
> > Todd.
> > ----
> > Todd Bradley - Director, Support Services - Jabber.com
> > tbr...@ja... - 303-308-3666
> > 
> > See you at JabberCon August 20 and 21 - www.jabbercon.com
> > 
> > _______________________________________________
> > Tclxml-users mailing list
> > Tcl...@li...
> > http://lists.sourceforge.net/lists/listinfo/tclxml-users
> > 
> > 
> 
> --
> James C. Moore, Ph.D.
> 
> 

Re: [Tclxml-users] why won't TclXML parse this?

[James C. M. <jm...@qn...>]

I'm pretty sure you are not allowed to use semicolons.    My xml is a little
rusty, though.

> I'm by no means an XML expert, so this may be a stupid
> question, but I was wondering why the TclXML parser
> chokes on something like this:
> 
> <foo bar='Black &amp; White'/>
> 
> The &amp; is giving ParseCommand fits.  If I take out
> the &amp; then things work fine.
> 
> The trace I'm getting looks like this:
> 
> {invalid attribute list} around line 0
>     while executing
> "::sgml::Error {invalid attribute list} around line 0"
>     ("uplevel" body line 1)
>     invoked from within
> "uplevel #0 $options(-errorcommand) [list $attr around line $state(line)]"
>     (procedure "ParseEvent:ElementOpen" line 21)
>     invoked from within
> "ParseEvent:ElementOpen $tag $param options -empty 1"
>     ("*,0,,/" arm line 5)
>     invoked from within
> "switch -glob -- [string length $tag],[regexp {^\?|!.*}
$tag],$close,$empty
> {
> 
>             0,0,, {
>                 # Ignore empty tag - dealt with non-normal mode above
>           ..."
>     (procedure "::sgml::parseEvent" line 118)
> 
> 
> 
> Possibly relevant version numbers from xml.tcl:
> 
> package provide xml 1.9
> 
> package require sgml 1.7
> 
> 
> 
> Todd.
> ----
> Todd Bradley - Director, Support Services - Jabber.com
> tbr...@ja... - 303-308-3666
> 
> See you at JabberCon August 20 and 21 - www.jabbercon.com
> 
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> http://lists.sourceforge.net/lists/listinfo/tclxml-users
> 
> 

--
James C. Moore, Ph.D.

[Tclxml-users] why won't TclXML parse this?

[Todd B. <TBr...@ja...>]

I'm by no means an XML expert, so this may be a stupid
question, but I was wondering why the TclXML parser
chokes on something like this:

<foo bar='Black &amp; White'/>

The &amp; is giving ParseCommand fits.  If I take out
the &amp; then things work fine.

The trace I'm getting looks like this:

{invalid attribute list} around line 0
    while executing
"::sgml::Error {invalid attribute list} around line 0"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 $options(-errorcommand) [list $attr around line $state(line)]"
    (procedure "ParseEvent:ElementOpen" line 21)
    invoked from within
"ParseEvent:ElementOpen $tag $param options -empty 1"
    ("*,0,,/" arm line 5)
    invoked from within
"switch -glob -- [string length $tag],[regexp {^\?|!.*} $tag],$close,$empty
{

            0,0,, {
                # Ignore empty tag - dealt with non-normal mode above
          ..."
    (procedure "::sgml::parseEvent" line 118)



Possibly relevant version numbers from xml.tcl:

package provide xml 1.9

package require sgml 1.7



Todd.
----
Todd Bradley - Director, Support Services - Jabber.com
tbr...@ja... - 303-308-3666

See you at JabberCon August 20 and 21 - www.jabbercon.com

[Tclxml-users] Tcl Expat for Tcl 8.3.3

[Dan S. <sc...@is...>]

Does anyone know of a location where I could download the binary version of Tcl Expat compiled for
Tcl 8.3.3?

Thanks,

Dan Schenck

=================================================
Dan Schenck		mailto:sc...@is...
Technical Principal
The Information Store	http://www.istore.com

10777 Westheimer, Suite 1040
Houston, TX 77042
Ph: 713 787-6798 x166  Fax: 713 787-6772
=================================================

Re: [Tclxml-users] XML Parser - Low footprint, very fast, very easy to use

[Steve B. <Ste...@zv...>]

Mike Clark wrote:
> 
> We've just produced the following xml parser for named xml tags only.
> It perfect for splitting an XML string when you know what tags to expect.
> Because we're using named tags its also very, very quick.
> 
> Download the FREE Windows COM Component at...
> http://www.salcentral.com/plugins/xmlparser.zip

Maybe I'm missing something, but what has this got to do with
TclXML?  Have you written a Tcl interface for your parser?

Also, what do you mean by "named tags"?  Aren't all tags named?
I presume you're talking about a so-called "Simple-XML"
variant which doesn't handle attributes, entities, etc.
If so then your parser is not XML conformant.

BTW, a Windows COM component, even if it is free, doesn't do
me alot of good since most of my development is on Unix/Linux or
Mac platforms.

Regards,
Steve Ball

-- 
Steve Ball            | waX Me Lyrical XML Editor | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |      XML XSL
http://www.zveno.com/ |      TclXML TclDOM        | Tcl, Web Development
Ste...@zv...  +---------------------------+---------------------
Ph. +61 2 6242 4099   |   Mobile (0413) 594 462   | Fax +61 2 6242 4099

[Tclxml-users] XML Parser - Low footprint, very fast, very easy to use

[Mike C. <mi...@lu...>]

We've just produced the following xml parser for named xml tags only.
It perfect for splitting an XML string when you know what tags to expect.
Because we're using named tags its also very, very quick.

Download the FREE Windows COM Component at...
http://www.salcentral.com/plugins/xmlparser.zip

Thanks...
Mike Clark
@Lucin

[ http://www.salcentral.com ] Worlds FIRST XML Schema search engine