tclxml-users — Discussion on using the TclXML package

[Tclxml-users] Re: Building TclXML v3.0

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

Hi Rich,

TclXML version 3.0 is in beta release at the moment.  One implication of
its beta status is that not all release engineering has been performed,
so the build system may not be entirely robust.  I'm planning on getting
those issues resolved when the packages are made final.

As far as the 'make test' target is concerned I've been doing alot of 
work
on that lately, but mostly since the beta1 release.  At the moment I 
assume
that the packages are fully installed before they can be tested - not a 
good
assumption and something that probably needs more work.

Finally, the "libxml2, v3.0" vs "libxml, v23.0" issue is tricky.  
However, I have
got it working on my Mac OSX, Linux and Windows systems.

I'm working towards a beta2 release soon, so hopefully alot of these 
problems
will have been resolved.

Cheers,
Steve Ball

On 03/02/2004, at 11:27, R. T. Wurth wrote:

> I am having quite a bit of trouble building tclxml version 3.0.
>
> It is not clear to me whether I should use the installer in the top
> directory or do the configure/make/install cycle, so I did both
> (installer first).  I found I needed to run autoconf to generate the
> config file.  This I found strange because most packages come with a
> pre-generated config file.  Then I started on the subdirectories,
> per the instructions.
>
> In expat, I had to edit the configure file to bump the version to
> 3.0.  (Looking at SF CVS, I see it's out of date w/resp. to
> configure.in.)
>
> In libxml2, I had to do the same.  In addition, I found the 'test'
> step of the Makefile' has a bug.  Where it refers to
> $TclXML_LIBXML2_LIB_FILE, it should refer to
> $TclXML_libxml2_LIB_FILE (note upper vs. lower case libxml2). But
> now, I am at my wit's end.  When I do try to test the package, it
> fails with error message:
>      couldn't find procedure Tclxml_libxml_Init
> I couldn't find a function with that name in the code, but I did
> find Tclxml_libxml2_Init.  I think the problem is that the library
> file is named libTclXML_libxml23.0.sl, which is intended to mean it
> is libTclXML_libxml2, version 3.0, however, the Tcl interpreter's
> simple parsing rules interpret it as libTclXML_libxml, version 23.0.
> Thus, it is missing the terminal 2 when it constructs the name of
> the library's Init proc.  I don't have any idea how this might be
> fixed simply.  It strikes me as an architectural issue that might
> require changing the package name to not have a terminal digit.  I
> don't see how anyone could have built this or any prior version and
> gotten it to work with this bug, so I have to wonder if there is
> something wrong with my configuration causing me to have this problem.
>
> Would you like SF bug reports on these?  Do you prefer all-in one,
> one per package (2 total, 1 each for expat, and libxml2), or one per
> problem (3 total, splitting the two libxml2 problems into separate
> issues)?
>
> Thanks for nay help you can provide.
> -- 
>   Rich Wurth / rw...@at... / Rumson, NJ  USA
>
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] Possible bug with xml default namespace serialization?

[Steve M. <st...@re...>]

Thanks!

Yes, this problem happens in both the 2.6 and 3.0b1 versions of the 
pure-Tcl parser.  It does not happen with the 3.0b1 Combined Binary 
Packages available on the tclxml project page.

Thx, Steve

Steve Ball wrote:

> Looks like a bug to me.  I'll make sure the test suite has a test case
> for this situation.
>
> Given your previous post, I assume you're using 3.0b1?
> The pure-Tcl implementation?
>
> Cheers,
> Steve Ball
>
> On 05/01/2004, at 11:59, Steve McMillen wrote:
>
>> I am seeing behavior which I do not expect but I'm not positive its a 
>> bug.  If I serialize an XML document with a default namespace (e.g. 
>> xmlns="some-uri"), I get an null namespace in the output elements 
>> (e.g. <:tag> instead of <tag>).
>>
>> For example, I parse the following XML using dom::parse
>>
>> <rootnode xmlns="http://myuri">
>>   <tag>value</tag>
>> </rootnode>
>>
>> Then I serialize the dom with dom::serialize, I get the following:
>>
>> <?xml version='1.0'?>
>> <!DOCTYPE :rootnode>
>> <:rootnode xmlns:="http://myuri">
>>   <:tag1>value</:tag1>
>> </:rootnode>
>>
>> Note the semicolon before the element names.  I did not expect this 
>> semicolon to be included.
>>
>> Am I defining my XML document incorrectly?  It was my understanding 
>> that the default namespace (xmlns w/o any suffix) was the namespace 
>> for any element that did not have an explicit namespace attached.  I 
>> would expect the output from the serialize function to be identical 
>> to the input in this case.
>>
>> I made a tweak to the dom library as follows which results in the 
>> behavior I desired:
>> Change line 2851 in dom.tcl (tcldom 3.0b1) from:
>>        } elseif {[string length $node(node:namespaceURI)]} {
>> to:
>>        } elseif {[string length $node(node:namespaceURI)] && \
>>           [string length [GetNamespacePrefix $token 
>> $node(node:namespaceURI)]]} {
>>
>> * This does not fix the printing of the xmlns attribute in the root 
>> element and the DOCTYPE.
>>
>> but I'm not sure if this is the right thing to do.  Essentially my 
>> goal was that if the xmlns prefix is null, then don't prepend.  There 
>> might be a more appropriate place to handle this thought (if indeed I 
>> am using XML correctly).
>>
>> If needed, let me know and I'll log a bug.
>>
>> Thx, Steve
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: IBM Linux Tutorials.
>> Become an expert in LINUX or just sharpen your skills.  Sign up for 
>> IBM's
>> Free Linux Tutorials.  Learn everything from the bash shell to sys 
>> admin.
>> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>> _______________________________________________
>> Tclxml-users mailing list
>> Tcl...@li...
>> https://lists.sourceforge.net/lists/listinfo/tclxml-users
>>
> Steve Ball            |   XSLT Standard Library   | Training & Seminars
> Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
> 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
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tclxml-users
>
>

Re: [Tclxml-users] Possible bug with xml default namespace serialization?

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

Looks like a bug to me.  I'll make sure the test suite has a test case
for this situation.

Given your previous post, I assume you're using 3.0b1?
The pure-Tcl implementation?

Cheers,
Steve Ball

On 05/01/2004, at 11:59, Steve McMillen wrote:

> I am seeing behavior which I do not expect but I'm not positive its a 
> bug.  If I serialize an XML document with a default namespace (e.g. 
> xmlns="some-uri"), I get an null namespace in the output elements 
> (e.g. <:tag> instead of <tag>).
>
> For example, I parse the following XML using dom::parse
>
> <rootnode xmlns="http://myuri">
>   <tag>value</tag>
> </rootnode>
>
> Then I serialize the dom with dom::serialize, I get the following:
>
> <?xml version='1.0'?>
> <!DOCTYPE :rootnode>
> <:rootnode xmlns:="http://myuri">
>   <:tag1>value</:tag1>
> </:rootnode>
>
> Note the semicolon before the element names.  I did not expect this 
> semicolon to be included.
>
> Am I defining my XML document incorrectly?  It was my understanding 
> that the default namespace (xmlns w/o any suffix) was the namespace 
> for any element that did not have an explicit namespace attached.  I 
> would expect the output from the serialize function to be identical to 
> the input in this case.
>
> I made a tweak to the dom library as follows which results in the 
> behavior I desired:
> Change line 2851 in dom.tcl (tcldom 3.0b1) from:
>        } elseif {[string length $node(node:namespaceURI)]} {
> to:
>        } elseif {[string length $node(node:namespaceURI)] && \
>           [string length [GetNamespacePrefix $token 
> $node(node:namespaceURI)]]} {
>
> * This does not fix the printing of the xmlns attribute in the root 
> element and the DOCTYPE.
>
> but I'm not sure if this is the right thing to do.  Essentially my 
> goal was that if the xmlns prefix is null, then don't prepend.  There 
> might be a more appropriate place to handle this thought (if indeed I 
> am using XML correctly).
>
> If needed, let me know and I'll log a bug.
>
> Thx, Steve
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for 
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys 
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tclxml-users
>
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] problems with dom::trim in 3.0

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

Don't bother logging a bug on this one, as I'm working on the event
code at the moment.  Check again when beta2 is released.

Cheers,
Steve Ball

On 05/01/2004, at 11:59, Steve McMillen wrote:

> I'm seeing an error with dom::trim using the 3.0b1 tcldom/tclxml 
> packages but not the 2.6 versions of these packages.  The error only 
> occurs when I am using the tcl parser.
>
> Here is an example that fails:
>
> % set doc [dom::parse {<rootnode xmlns="http://myuri">
>   <tag1>value</tag1>
> </rootnode>}]
> ::dom::tcl::document2::Document
> % dom::trim $doc
> can't delete "::dom::tcl::document2::event7": command doesn't exist
>
> Should I log a bug?
>
> Thx, Steve
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for 
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys 
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Tclxml-users mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tclxml-users
>
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] problems with dom::trim in 3.0

[Steve M. <st...@re...>]

I'm seeing an error with dom::trim using the 3.0b1 tcldom/tclxml 
packages but not the 2.6 versions of these packages.  The error only 
occurs when I am using the tcl parser.

Here is an example that fails:

% set doc [dom::parse {<rootnode xmlns="http://myuri">
   <tag1>value</tag1>
</rootnode>}]
::dom::tcl::document2::Document
% dom::trim $doc
can't delete "::dom::tcl::document2::event7": command doesn't exist

Should I log a bug?

Thx, Steve

[Tclxml-users] Possible bug with xml default namespace serialization?

[Steve M. <st...@re...>]

I am seeing behavior which I do not expect but I'm not positive its a 
bug.  If I serialize an XML document with a default namespace (e.g. 
xmlns="some-uri"), I get an null namespace in the output elements (e.g. 
<:tag> instead of <tag>).

For example, I parse the following XML using dom::parse

<rootnode xmlns="http://myuri">
   <tag>value</tag>
</rootnode>

Then I serialize the dom with dom::serialize, I get the following:

<?xml version='1.0'?>
<!DOCTYPE :rootnode>
<:rootnode xmlns:="http://myuri">
   <:tag1>value</:tag1>
</:rootnode>

Note the semicolon before the element names.  I did not expect this 
semicolon to be included.

Am I defining my XML document incorrectly?  It was my understanding that 
the default namespace (xmlns w/o any suffix) was the namespace for any 
element that did not have an explicit namespace attached.  I would 
expect the output from the serialize function to be identical to the 
input in this case.

I made a tweak to the dom library as follows which results in the 
behavior I desired:
Change line 2851 in dom.tcl (tcldom 3.0b1) from:
        } elseif {[string length $node(node:namespaceURI)]} {
to:
        } elseif {[string length $node(node:namespaceURI)] && \
           [string length [GetNamespacePrefix $token 
$node(node:namespaceURI)]]} {

* This does not fix the printing of the xmlns attribute in the root 
element and the DOCTYPE.

but I'm not sure if this is the right thing to do.  Essentially my goal 
was that if the xmlns prefix is null, then don't prepend.  There might 
be a more appropriate place to handle this thought (if indeed I am using 
XML correctly).

If needed, let me know and I'll log a bug.

Thx, Steve

[Tclxml-users] Re: [xml] Application Releases

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

On 22/12/2003, at 20:46, Daniel Veillard wrote:
> On Mon, Dec 22, 2003 at 06:09:41PM +1100, Steve Ball wrote:
>> Version 1.3 of tkxsltproc also uses structured error messages,
>> as well as better support for stylesheet parameters.
>
>   Hum, that's one of the missing changes needed in libxslt, it
> should also use the structured error handler and doesn't at the moment.

Sorry, I should have said "also uses structured error messages *where 
possible*".
When reading & parsing the source & stylesheet documents any errors
are reported using structured errors (ie. when employing libxml2 
functions).
Any errors that occur while compiling the stylesheet and running the
transformation are reported as unstructured errors.

Hope that clears things up,
Steve Ball

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] Combo Distributions

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

To make life easier for Mac and Windows users, TclXML Combo 
distributions
are now available from the SourceForge download area.

These combo distributions include the TclXML, TclDOM and TclXSLT 
packages;
pre-compiled and ready to go!  All packages are at version 3.0b1.

Links to the downloads are at http://tclxml.sf.net/

Enjoy,
Steve Ball

Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] using the -final option

[Ihtisham K. <iht...@ya...>]

I have been unable to determine how to use the -final
option by reviewing the examples in the Reference
manual
(http://tclxml.sourceforge.net/tclxml/2.6/tclxml.html)
and in Zveno's tutorial
(http://www.zveno.com/courses/samples/XML-App-Dev-Tcl/Topics/Parsing-TclXML-4.html).

Perhaps someone has some better examples, and maybe
even a better explanation of what this option is
supposed to do?

Thanks,

Ihtisham

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/

[Tclxml-users] DOCTYPE not implemented?

[Ray B. I. <rba...@ve...>]

Hi,

I'm trying to generate the doctype node in my XML file, but since I've
upgraded from dom 2.2 to dom 2.6 the documented commands say they aren't
implemented - or they don't work.

set doctype [dom::libxml2::DOMImplementation createDocumentType $doc
Transaction {} RASalesOrders.dtd]

set doctype [dom::DOMImplementation createDocumentType $doc Transaction
{} RASalesOrders.dtd]

Any ideas on how I can generate the doctype directive short or opening
the file and seeking to the second line? :)

Thanks!

 Ray.
--
Ray Barrett III
Project Manager
Versatile Mobile Systems Inc.
www.versatilemobile.com 

Re: [Tclxml-users] dynamic XML

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

Maria M. Yu wrote:
> I am trying to test to see if I could use Tcl for dynamic XML as it's 
> claimed by tcltk.
>  
> Basically, I want to create a base xml document and then supply scripts 
> to fill in various parts of the base xml document with dynamic data.
>  
> Do you have anything that could help with my implementation?

I can think of a couple of different ways to achieve this.

Firstly, the simplest approach may be the "microscripting"
technique.  The technique involves embedding Tcl scripts in your
XML document and then use the 'subst' command to resolve the
scripts.  This approach was first developed for HTML documents
in the NeoWebServer and tclhttpd Web servers.  For example:

<article>
   <title>$title</title>

   <para>The time is [clock format [clock seconds]].</para>
</article>

Notice how the Tcl scripting and XML are intimately
tied together.

 From an XML purist point-of-view, another approach is to
use XSLT.  XSLT is very good at dynamically creating XML documents.
Parameters can be passed into the stylesheet as required.

Even more sophisticated is to use TclXSLT - XSLT combined
with Tcl extensions.

With TclXSLT you can make calls into Tcl scripts from an
XSL stylesheet.  The following example is a 'literal result element
as a stylesheet':

<article xsl:version='1.0'
   xmlns:xsl='http://www.w3.org/1999/XSL/Transform'
   xmlns:tcl='urn:my-tcl-extension'
   extension-element-prefixes='tcl'>

   <title><tcl:variable name='title'/></title>

   <para>The time is <tcl:format-time/>.</para>
</article>

The Tcl script(s) that implement the 'tcl:' extension
elements are not shown here.

This approach separates the Tcl code from the XML/XSLT document,
which is certainly a desirable characteristic.
However, you will notice that the overheads are high
so it is up to you as to whether that is acceptable.

There are other approaches - xmlgen springs to mind,
as well as using TclDOM to navigate and modify the document.

Hope that helps,
Steve Ball

-- 
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] dynamic XML

[Maria M. Y. <mm...@Co...>]

I am trying to test to see if I could use Tcl for dynamic XML as it's =
claimed by tcltk.
=20
Basically, I want to create a base xml document and then supply scripts =
to fill in various parts of the base xml document with dynamic data.
=20
Do you have anything that could help with my implementation?
=20
Thank you.
=20
Maria Yu

[Tclxml-users] Fw: empty element syntax (tclxml2.6)

[oliver <oli...@gm...>]

Forget my previous posting, should read the docs more carefully :-)

This was my missing: -reportempty 1

Cheers Oliver

----- Original Message ----- 
From: "oliver" <oli...@gm...>
To: <tcl...@li...>
Sent: Friday, July 11, 2003 1:04 AM
Subject: empty element syntax (tclxml2.6)


> Hi list,
> 
> I don't get this additional argument '-empty boolean' when reading an xml
> source:
> What am I doing wrong?
> 
> Regards Oliver
> 
> XML-Source:
> <?xml version="1.0"?>
> <menue>
>  <menu/>
>  <menu/>
>  <menu/>
> </menue>
> 
> TCL-Source:
> package require xml
> 
> proc ElementEndCmd {name_ args} {
>     puts "$name_ $args"
> }
> 
> proc ElementStartCmd {name_ attList_ args} {
>     puts "$name_ $attList_ $args"
> }
> 
> set parser [::xml::parser\
>  -elementendcommand ElementEndCmd\
>  -elementstartcommand ElementStartCmd]
> set file [file join c:/ pia menutest.xml]
> set fh [open $file r]
> $parser parse [read $fh]
> close $fh
> 

[Tclxml-users] empty element syntax (tclxml2.6)

[oliver <oli...@gm...>]

Hi list,

I don't get this additional argument '-empty boolean' when reading an xml
source:
What am I doing wrong?

Regards Oliver

XML-Source:
<?xml version="1.0"?>
<menue>
 <menu/>
 <menu/>
 <menu/>
</menue>

TCL-Source:
package require xml

proc ElementEndCmd {name_ args} {
    puts "$name_ $args"
}

proc ElementStartCmd {name_ attList_ args} {
    puts "$name_ $attList_ $args"
}

set parser [::xml::parser\
 -elementendcommand ElementEndCmd\
 -elementstartcommand ElementStartCmd]
set file [file join c:/ pia menutest.xml]
set fh [open $file r]
$parser parse [read $fh]
close $fh

Re: [Tclxml-users] Has anyone created a tclxml/tcldom/tclsoap/whatever starkit ?

[Steve C. <Ste...@mq...>]

Steve Ball wrote:

> Larry W. Virden wrote:
>
>> Until the creation of an automated binary repository and starkit 
>> generation
>> facility, is anyone maintaining a starkit of the tclxml suite of tools?
>
>
> [NB. I'm working on v3.0 at the moment and I really don't
> want to have to divert energy into StarKit packaging.
> This *really will* have to have someone other than myself
> do the work.]
>
FWIW the CANTCL code is now very close to being able to do this on 
demand for any set of packages stored in it. Hopefully before the 
conference I'll be able to have a version running with this capability. 
 So, the only effort needed is to ensure that there's a DESCRIPTION.txt 
file for each package and that they're laid out in about the right way 
(the normal installed package layout is now fine although TIP55 layout 
provides more features).

Steve

Re: [Tclxml-users] Installation of tclxml2.6

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

Mar...@ar... wrote:
> I need to perform some xml-tcl parsing and heard that the tclxml2.6 
> package was a good place to start.  However, as I tried to install the 
> software I kept getting an error message and hence installation would 
> not complete. I was following the instructions given on how to build and 
> install tclxml2.6 at 
> http://tclxml.sourceforge.net/tclxml/2.6/README.html#installation
> and was using the compiled installation unix instructions. I have tcl 
> 8.3 and tcllib 1.4 installed so thought there would be no problem but 
> when it came to installing the expat parser class (the last step) the 
> following error message was generated:
> make: Fatal error: Don't know how to make target "tclexpat.o"

I tested the build process on Mac OS X and Linux (RedHat 8.0)
and it worked for me.  Perhaps you could send a log of your effort
to see if you have missed a step or whether something else
went wrong?

Cheers,
Steve Ball

-- 
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] Has anyone created a tclxml/tcldom/tclsoap/whatever starkit ?

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

Larry W. Virden wrote:
> The starkit distribution format is a great way to distribute a binary
> distribution.

I couldn't agree more!

> Until the creation of an automated binary repository and starkit generation
> facility, is anyone maintaining a starkit of the tclxml suite of tools?

I have discussed this with Jean-Claude, but it has stalled
for lack of a volunteer to do the builds, particularly for
Windows.

Given that Andreas has everything building just fine for the
ActiveState distribution, it should be straight-forward to
get TclXML/libxml2, TclDOM/libxml2 and TclXSLT building
for Kitten... any volunteer(s)?

[NB. I'm working on v3.0 at the moment and I really don't
want to have to divert energy into StarKit packaging.
This *really will* have to have someone other than myself
do the work.]

Cheers,
Steve Ball

-- 
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] Has anyone created a tclxml/tcldom/tclsoap/whatever starkit ?

[Larry W. V. <lv...@ca...>]

The starkit distribution format is a great way to distribute a binary
distribution.

Until the creation of an automated binary repository and starkit generation
facility, is anyone maintaining a starkit of the tclxml suite of tools?
-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

[Tclxml-users] Installation of tclxml2.6

[<Mar...@ar...>]

Hi there,

I need to perform some xml-tcl parsing and heard that the tclxml2.6 
package was a good place to start.  However, as I tried to install the 
software I kept getting an error message and hence installation would not 
complete. I was following the instructions given on how to build and 
install tclxml2.6 at 
http://tclxml.sourceforge.net/tclxml/2.6/README.html#installation 
and was using the compiled installation unix instructions. I have tcl 8.3 
and tcllib 1.4 installed so thought there would be no problem but when it 
came to installing the expat parser class (the last step) the following 
error message was generated:
make: Fatal error: Don't know how to make target "tclexpat.o"

I have tried using gnumake and this was also unsuccessful.

Any suggestions as to what might be the problem and how it can be 
rectified are greatly appreciated.

Mark Sprawson

Re: [Tclxml-users] xslt translation problem

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

wjax . wrote:
> I have tried to do this:
> 
> package require xslt 2.6
> package require dom 2.6
> set XML "c:/tcl/to_translate.xml"
> set xls  "c:/tcl/rules.xls"
> set source_doc [::dom::libxml2::parse $XML]
> set ssheet_doc [::dom::libxml2::parse $xls]
> set ssheet [::xslt::compile $ssheet_doc]
> set result [$ssheet transform $source_doc]
> 
> and it gives an error, it does not find "<", so i have though that the 
> $XML must be a string with all the file read inside.

Correct.

> So i have tried this:
> 
> package require xslt 2.6
> package require dom 2.6
> set ch [open c:/tcl/meta.xml]
> fconfigure $ch -encoding shiftjis
> set XML [read $ch]
> set ch1 [open c:/tcl/engtra.xsl]
> fconfigure $ch1 -encoding shiftjis
> set xls [read $ch1]
> set source_doc [::dom::libxml2::parse $XML]
> set ssheet_doc [::dom::libxml2::parse $xls]
> set ssheet [::xslt::compile $ssheet_doc]
> set result [$ssheet transform $source_doc]
> 
> And now it does not give error but it does not show anything, it says 
> only "doc3" or something like that. But it does not return a translated 
> file....

You must serialize the DOM tree of the result document, ie:

puts [dom::serialize $result]

HTHs,
Steve Ball

-- 
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] xslt translation problem

[wjax . <wj...@ho...>]

Hello,

I am really desperate. I have started to use tcl/tk for a few days. And i 
need to make a xslt translation.
So i have a rule file called rules.xsl and a xml called to_translate.xml.
I have tried to do this:

package require xslt 2.6

package require dom 2.6

set XML "c:/tcl/to_translate.xml"
set xls  "c:/tcl/rules.xls"
set source_doc [::dom::libxml2::parse $XML]
set ssheet_doc [::dom::libxml2::parse $xls]
set ssheet [::xslt::compile $ssheet_doc]
set result [$ssheet transform $source_doc]

and it gives an error, it does not find "<", so i have though that the $XML 
must be a string with all the file read inside. So i have tried this:

package require xslt 2.6

package require dom 2.6

set ch [open c:/tcl/meta.xml]
fconfigure $ch -encoding shiftjis
set XML [read $ch]
set ch1 [open c:/tcl/engtra.xsl]
fconfigure $ch1 -encoding shiftjis
set xls [read $ch1]
set source_doc [::dom::libxml2::parse $XML]
set ssheet_doc [::dom::libxml2::parse $xls]
set ssheet [::xslt::compile $ssheet_doc]
set result [$ssheet transform $source_doc]

And now it does not give error but it does not show anything, it says only 
"doc3" or something like that. But it does not return a translated file....

Can you help me please????

Thanks a lot.
Ciao

_________________________________________________________________
Descubre el mayor catálogo de coches de la Red en MSN Motor. 
http://motor.msn.es/researchcentre/

Re: [Tclxml-users] more on dom::c

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

Larry W. Virden wrote:
> Well, the good news is that I figured out why I am missing dom::c .
> The bad news is this.  A few days ago, I started getting this error:
> 
> $ tclsh     
> % package require SOAP
> require dom package greater than 1.6
> 
> When I deleted the version of dom::c that was in tcldom 2.6, this
> error went away.

dom::c is a completely separate package to dom::tcl and dom::libxml2.
The former is maintained by Joe English, the latter by Yours Truly.
They share the same distribution, but not much else.
Integration of the packages could be much better, but Joe seems
happy with things as they are (iow, talk to Joe about changing
aspects of that package).

> Is there something wrong with the code in the latest CVS head of
> TclDOM that is causing this?

Not as far as I am aware...

Cheers,
Steve Ball

-- 
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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] more on dom::c

[Larry W. V. <lv...@ca...>]

Well, the good news is that I figured out why I am missing dom::c .
The bad news is this.  A few days ago, I started getting this error:

$ tclsh     
% package require SOAP
require dom package greater than 1.6

When I deleted the version of dom::c that was in tcldom 2.6, this
error went away.

Is there something wrong with the code in the latest CVS head of
TclDOM that is causing this?
-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

Re: [Tclxml-users] Anyone ever seen this?

[Larry W. V. <lv...@ca...>]

I am still seeing peculiar things with tcldom.

$ tclsh
% package require SOAP
1.6.6
% package require dom::generic
2.6
% package require dom::tclgeneric
2.6
% package require dom::c
can't find package dom::c
% package require dom::libxml2
2.6
% 


Shouldn't there be a dom::c installed if the generic and libxml2 and
tcl are installed?
-- 
Tcl - The glue of a new generation.  <URL: http://wiki.tcl.tk/ >
Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/>
Even if explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

Re: [Tclxml-users] Anyone ever seen this?

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

Larry W. Virden wrote:
> From: Steve Ball <Ste...@zv...>
>>Looks like a problem with the installation.  Which versions
>>do you have installed (or *think* you have installed ;-)
[...snip...]
> Too bad that multiple versions of these extensions can't be installed
> at the same time. 

That may be something I need to look into.  There's no reason
why that shouldn't be the case.

Cheers,
Steve Ball

-- 
Steve Ball            |   XSLT Standard Library   | Training & Seminars
Zveno Pty Ltd         |     Web Tcl Complete      |   XML XSL Schemas
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