ANNOUNCE: TclXML Version 3.1

[Steve Ball]

TclXML, TclDOM and TclXSLT version 3.1 are now available.
Source code may be downloaded immediately,
Mac OS X and MS Windows binaries will be available shortly.

TclXML is a package that provides XML parsing for the Tcl scripting
language.
It has three implementations of XML parsers: one written purely in Tcl
and wrappers for the expat and Gnome libxml2 C libraries.

TclDOM is a package that implements the W3C DOM interfaces for the
Tcl scripting language. It also has three implementations: one written
purely in Tcl, one written in C and a wrapper for the Gnome libxml2 C
library.

TclXSLT is a package that provides a Tcl interface to the Gnome libxslt

C library.

These packages may be downloaded from the TclXML website:

http://tclxml.sourceforge.net/

Enjoy,
Steve Ball
Explain
http://www.explain.com.au/

[davidh...@simplifiedlogic.com]

Thank you for your contribution!

Please announce the windows binaries when you get a chance.

Dave

[Ivan Lazarte]

congratulations and thanks steve

[Robert Hicks]

I am curious. The 3.0 version has been out for a while but the latest
ActiveTcl distro still has the 2.6 version. Any idea why?

Robert

[Steve Ball]

I can't speak for the ActiveState team, but 3.0 did have some stability
problems; these have been addressed in 3.1.

[chang...@hotmail.com]

Great work. One thing I am wondering is that the tcldom2.0 is only
180KB but the Tcldom_libxm230.dll is 1.4MB. The difference of size is
huge what happened?

[Steve Ball]

At one point I was statically linking libxml2 into TclDOM/libxml2.
This would explain the size of the DLL you are reporting. However, I
subsequently discovered that this does not work so now the DLLs are
dynamically linked.

For version 3.1, Tcldom_libxml231.dll is 60KB.

HTHs,
Steve Ball

[Steve Ball]

Following-up on this announcement, binaries for Mac OS X and MS Windows
are now available.

See http://tclxml.sourceforge.net/combo.html for details.

Enjoy,
Steve Ball

[Jeff Hobbs]

Steve Ball wrote:
> I can't speak for the ActiveState team, but 3.0 did have some stability
> problems; these have been addressed in 3.1.

We were aware of the stability problems - we'll look again at 3.1.
However, the move of major versions sometimes confuses users that
were restricting themselves to v2 features. We are looking into
making a code repository that would alleviate these issues (both
being available for users). When md5 went from v1 to v2 it really
tripped up several users.

--
Jeff Hobbs, The Tcl Guy
http://www.ActiveState.com/, a division of Sophos

[Robert Hicks]

Steve,

I get the following error on a "package require xslt":

couldn't load library "C:/Tcl/lib/Tclxslt3.1/Tclxslt31.dll": this
library or a dependent library could not be found in library path

I have libxslt.dll, libxml2.dll and libexslt.dll in C:/Tcl/bin. I
downloaded the versions per the directions on the COMBO distro page.

Any ideas?

Robert

[Helmut Giese]

On 8 Nov 2005 06:01:57 -0800, "Robert Hicks" <sig...@gmail.com>
wrote:

Hi Robert,
get the dependency walker from (IIRC)
www.dependencywalker.com,
let it load Tclxslt31.dll and look what other DLLs it needs.
HTH
Helmut Giese

[Robert Hicks]

Helmut Giese wrote:
<snip>

> Hi Robert,
> get the dependency walker from (IIRC)
> www.dependencywalker.com,
> let it load Tclxslt31.dll and look what other DLLs it needs.
> HTH
> Helmut Giese

[ ? ] TCLDOM_LIBXML231.DLL Error opening file. The system cannot find
the file specified (2).
[ ? ] TCLLIBXML231.DLL Error opening file. The system cannot find
the file specified (2).
[ ? ] ZLIB1.DLL Error opening file. The system cannot find
the file specified (2).

I guess this is what it is telling me?

The first one: C:\Tcl\lib\Tcldom_libxml23.1
The second one: C:\Tcl\lib\Tcllibxml3.1
The third one: I have zlib11.dll in C:\Tcl\lib\zlib1.1

They are all there...?

[Helmut Giese]

On 8 Nov 2005 12:32:05 -0800, "Robert Hicks" <sig...@gmail.com>
wrote:

>

Hm, the names do look a bit different:
- TCLDOM_LIBXML231.DLL vs Tcldom_libxml23.1
- TCLLIBXML231.DLL vs Tcllibxml3.1
Capitalization does not matter on Windows but the DLLs you have seem
to have an additional '.' like '23.1' vs '231'. If this is the case
(and not just a typo in your post) try renaming the ones you have to
match the expectations of the computer.
Ah, if only the TIP for RMMADWIM (133 ?) were already implemented.
HTH
Helmut Giese

[Robert Hicks]

Helmut Giese wrote:
<snip>

> >I guess this is what it is telling me?
> >
> >The first one: C:\Tcl\lib\Tcldom_libxml23.1
> >The second one: C:\Tcl\lib\Tcllibxml3.1
> >The third one: I have zlib11.dll in C:\Tcl\lib\zlib1.1
> >
> >They are all there...?
> Hm, the names do look a bit different:
> - TCLDOM_LIBXML231.DLL vs Tcldom_libxml23.1
> - TCLLIBXML231.DLL vs Tcllibxml3.1

The ones above are the directories the DLLs are in and not the DLLs
themselves. I will look at that when I get to work though.

Robert

[Steve Ball]

You also need zlib and iconv. These are dependencies of libxml2 and
libxslt, not TclXSLT per se, and are available from the xmlsoft.org
download site.

You may also need msvcr71.dll. Since this is a MS library and I am
uncertain as to whether it can be redistributed, I do not include it in
the binary distro.

An example of how to package up these DLLs are the tkxmllint and
tkxsltproc applications, also available from tclxml.sf.net. I haven't
updated these for the final v3.1 release, but they still serve to show
what dependent libraries to include.

[Robert Hicks]

iconv.dll is in the C:\Tcl\bin directory. I will have to see about the
msv one but I think that I did a search and that is there as well.

I will let you know.

[Chang Li]

I can compiler tclxml in msys for windows. But it failed to compile
tcldom and tclxslt. Some configure files missed?

Chang