You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(18) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(11) |
Feb
(2) |
Mar
(1) |
Apr
(4) |
May
(23) |
Jun
(17) |
Jul
(1) |
Aug
(17) |
Sep
(4) |
Oct
(14) |
Nov
(1) |
Dec
(2) |
2002 |
Jan
|
Feb
(2) |
Mar
(15) |
Apr
|
May
(19) |
Jun
(2) |
Jul
(8) |
Aug
(24) |
Sep
(21) |
Oct
(17) |
Nov
(11) |
Dec
(20) |
2003 |
Jan
(17) |
Feb
(19) |
Mar
(21) |
Apr
(13) |
May
(14) |
Jun
(7) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(3) |
2004 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
(5) |
Jul
(12) |
Aug
(3) |
Sep
(14) |
Oct
(1) |
Nov
(4) |
Dec
(3) |
2005 |
Jan
(1) |
Feb
(6) |
Mar
(3) |
Apr
|
May
(2) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
2006 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2007 |
Jan
(1) |
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(8) |
Oct
(1) |
Nov
|
Dec
|
From: Larry W. V. <lv...@ca...> - 2003-05-13 10:55:00
|
From: Steve Ball <Ste...@zv...> > Looks like a problem with the installation. Which versions > do you have installed (or *think* you have installed ;-) I had a couple of older versions of TclXML, TclDOM and TclSOAP installed. Normally I don't like removing these too soon, because I can't tell whether any of my users have linked against the .so files, etc. In this case, I moved the files out of the way for a bit, and that resolved the problems. Too bad that multiple versions of these extensions can't be installed at the same time. -- 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. -><- |
From: Steve B. <Ste...@zv...> - 2003-05-12 21:24:59
|
Larry W. Virden wrote: > $ tclsh > % package require dom > conflicting versions provided for package "dom": 2.0, then 2.6 > % Looks like a problem with the installation. Which versions do you have installed (or *think* you have installed ;-) 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 |
From: Larry W. V. <lv...@ca...> - 2003-05-12 15:48:56
|
$ tclsh % package require dom conflicting versions provided for package "dom": 2.0, then 2.6 % -- 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. -><- |
From: Larry W. V. <lv...@ca...> - 2003-05-04 09:11:45
|
I found the problem, thanks to a neat routine provided by Joe English (maybe it should be part of the std Tcl environment!) Anyways, what it showed me was that there was still a bogus dom::c installed from a TclDOM 2.5 release that was installed. Once I cleared that out, the proper dom::c was found. Thanks all. -- 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. -><- |
From: Larry W. V. <lv...@ca...> - 2003-05-03 03:29:38
|
> From: Forest Wilkinson <lyr...@ti...> > To: tcl...@li... > Subject: Re: [Tclxml-users] more tcldom questions > Date: Fri, 02 May 2003 10:45:49 -0700 > > >% package require dom > >2.6 > > [snip] > > >% package require tcldom > >2.0 > > The discrepency between version numbers is most likely because > tcldompro (the implementation built from the tcldom/src dir) is at > version 2.0, while the other implementations of tcldom are at 2.6. > You only need one of the three implementations. I am using the > tcldompro (2.0) version, because I am able to build it and it is > complete enough for my application (using tclsoap). Note that the version descrepancy isn't the issue for me - I understand that. The problem is that dom::c just won't be resolved by itself, even though it should be. $ tclsh % package require dom::c can't find package dom::c % ^d $ tclsh % package require tcldom 2.0 % package require dom::c 2.0 % Why do I have to package require tcldom before dom::c for dom::c to be found? -- 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. -><- |
From: Forest W. <lyr...@ti...> - 2003-05-02 17:45:58
|
>% package require dom >2.6 [snip] >% package require tcldom >2.0 The discrepency between version numbers is most likely because tcldompro (the implementation built from the tcldom/src dir) is at version 2.0, while the other implementations of tcldom are at 2.6. You only need one of the three implementations. I am using the tcldompro (2.0) version, because I am able to build it and it is complete enough for my application (using tclsoap). =46orest |
From: Larry W. V. <lv...@ca...> - 2003-05-02 17:19:39
|
Okay, I did something similar. I fetched expat, configured, built and installed it. I got tcldom from the CVS. I configured, built, and installed all 3 parts - the top level directory, then the src-libxml2 version, and finally the stuff in the plain src directory. What I see is this $ tclsh % package require dom::c can't find package dom::c % ^d $ tclsh % package require dom 2.6 % package require dom::c can't find package dom::c % ^d $ tclsh % package require tcldom 2.0 % package require dom::c 2.0 % Looks to me like there's something wrong in the pkgIndex.tcl files that are created. -- 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. -><- |
From: Forest W. <lyr...@ti...> - 2003-05-02 17:05:49
|
>Can anyone help? The tcldom/src directory contains the tcldompro implementation of tcldom. As of the version 2.6 distribution, it didn't build properly, but that was fixed in CVS just over a month ago. Here are the steps I used to build from a CVS checkout I did on 28 March: (This worked on linux and solaris.) 1. build expat: cd expat-1.95.6 ./configure --enable-shared=3Dno --prefix=3D/usr/local make make install 2. build tcldom: (TclDOMPro implementation) cd tcldom-2.6/src ./configure --prefix=3D/usr/local make make install |
From: Larry W. V. <lv...@ca...> - 2003-05-02 12:30:38
|
Okay, after searching around the tcldom distribution, I found that there are at least 3 directories that one can configure and install. I went into the tcldom/src directory, configured against my expat installation directory. I did the make, and an install. Now, here's what I am seeing. $ grep dom::c /usr/tcl84/lib/*/pkg*tcl /usr/tcl84/lib/Tcldom2.5/pkgIndex.tcl:package ifneeded dom::c 2.5 [list load [file join $dir libTcldom2.5g.so]] /usr/tcl84/lib/Tcldom2.5/pkgIndex.tcl:# list of packages loaded (and looking for dom::c or dom::tclgeneric). /usr/tcl84/lib/Tcldom2.5/pkgIndex.tcl: catch {package require dom::c} /usr/tcl84/lib/Tcldom2.6/pkgIndex.tcl:package ifneeded dom::c 2.6 [list load [file join $dir libTcldom2.6g.so]] /usr/tcl84/lib/Tcldom2.6/pkgIndex.tcl:# list of packages loaded (and looking for dom::c or dom::tclgeneric). /usr/tcl84/lib/Tcldom2.6/pkgIndex.tcl: catch {package require dom::c} $ tclsh % package require dom::c can't find package dom::c % load /usr/tcl84/lib/Tcldom2.6/libTcldom2.6g.so % package require dom::c can't find package dom::c % So I'm confused - the shared library appears to be there. However, tcl isn't loading the package. Can anyone help? -- 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. -><- |
From: Larry W. V. <lv...@ca...> - 2003-05-02 11:58:38
|
Okay, can someone walk me through what it takes to install TclDOM? Here's why I ask. I downloaded the tar file. I configure, make and install it. Now, a user tries to use it and says: The Tcl DOM docs recommend going with a C implementation (rather than the default tcl implementation) for speed purposes. They mention TclDOMPro and libxml2, with the latter being preferred for some reason. Only the tcl implementation seems to be available to me: % package require dom 2.6 % package require dom::tcl 2.6 % package require dom::c can't find package dom::c % package require dom::TclDOMPro can't find package dom::TclDOMPro % package require dom::libxml2 couldn't load file "/usr/tcl84/lib/tcldomxml2.6/libtcldomxml2.6g.so": ld.so.1: tclsh: fatal: libxml2.so.2: open failed: No such file or directory So, here are my questions: 1. Is dom:cc still an active extension, or is it deprecated? To get dom::c to work, do I need to install a seperate package? If so, what? 2. Is TclDOMPro still an active extension that people are expected to use, or is it deprecated? I'll investigate the hand editing needed of the libxml2 Makefile so it no longer fails to find the library; it's too bad that isn't handled in the distribution, but I can fix that. -- 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. -><- |
From: Joe E. <jen...@fl...> - 2003-04-18 21:24:32
|
Forest Wilkinson wrote: > Will TclDOMPro build on Windows yet? What issues remain with MSVC? The current CVS HEAD (committed 2 Apr 2003) worked for me with cygwin+MSVC and with MSYS+MinGW. See tcldom/src/README.txt r1.1 for more details. Hrm... looks like I neglected to notify the list as promised when I got this working. My apologies. Anyway, please try it out and let me know if you have any problems; I think it should work now. --Joe English jen...@fl... |
From: Forest W. <lyr...@ti...> - 2003-04-18 16:39:41
|
Will TclDOMPro build on Windows yet? What issues remain with MSVC? If there is a sticky problem, perhaps the developer of tclsoap can help, as his site has an older precompiled windows version available for download: http://tclsoap.sourceforge.net/dom-packages.html On Tue, 01 Apr 2003 20:12:48 -0800, Joe English wrote: > >Update on the tcldompro Windows build: > >I've updated the build system to use the new tcl.m4, >and it's mostly working with MSVC. It appears to compile=20 >and link OK with cygwin+gcc, but the interpreter locks up=20 >when you try to [load] the .DLL. I suspect CYGWIN problems. > >Have to go home now, will fight with this some more >tomorrow. More later. Haven't checked anything into=20 >CVS yet, it's still a bit of a mess and still basically >broken. > > >--Joe English > > jen...@fl... |
From: Larry W. V. <lv...@ca...> - 2003-04-04 20:08:30
|
Ah - I will bet I have an old cache around. I will check into that - thanks for the tip! -- 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. -><- |
From: Andreas K. <and...@Ac...> - 2003-04-04 19:56:17
|
> -----Original Message----- > From: tcl...@li... > [mailto:tcl...@li...]On Behalf Of Larry W. > Virden > Sent: Friday, April 04, 2003 11:45 AM > To: tcl...@li... > Subject: [Tclxml-users] tclxml question > > > Okay, when I take a look at what RELNOTES says is tclxml 2.6, I am seeing > this in library/pkgIndex.tcl: This file is generated from tclxml/librar/pkgIndex.tcl.in and when I do it here I get the correct version number, 2.6. Do you have an older config.cache lying around ? Also, have the generated shared libraries a 2.6 or 2.5 suffix ? > # Requesting the generic package leaves the choice of default > parser automatic > > package ifneeded xml 2.5 { > if {[catch {package require xml::c 2.5}]} { > package require xml::tcl 2.5 > package require xmldefs > # Only choice is tclparser > package require xml::tclparser 2.5 > } else { > package require xmldefs > package require xml::tclparser 2.5 > catch {package require xml::expat 2.5} > } > package provide xml 2.5 > } > > > When I do a > package require xml > I get 2.5 back. > > So, is TclXML 2.6 _supposed_ to have package xml as 2.5 ? Because there > is code in TclDOM 2.6 that does a package require xml 2.6 ... -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com Join the community at the 10th Tcl conference http://wiki.tcl.tk/6274 |
From: Larry W. V. <lv...@ca...> - 2003-04-04 19:45:30
|
Okay, when I take a look at what RELNOTES says is tclxml 2.6, I am seeing this in library/pkgIndex.tcl: # Requesting the generic package leaves the choice of default parser automatic package ifneeded xml 2.5 { if {[catch {package require xml::c 2.5}]} { package require xml::tcl 2.5 package require xmldefs # Only choice is tclparser package require xml::tclparser 2.5 } else { package require xmldefs package require xml::tclparser 2.5 catch {package require xml::expat 2.5} } package provide xml 2.5 } When I do a package require xml I get 2.5 back. So, is TclXML 2.6 _supposed_ to have package xml as 2.5 ? Because there is code in TclDOM 2.6 that does a package require xml 2.6 ... -- 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. -><- |
From: Joe E. <jen...@fl...> - 2003-04-02 23:12:36
|
Moisei RABINOVITCH > > I just wondering what version of TCL should be used when compile the latest > version of tcldompro? (My env is: Windows 2000, SP3.) The current version (just checked into CVS, 2 Apr 2003) works for me with ActiveTcl 8.3.5, (MSVC, Windows 2000, don't know the SP number). It should work with the current ActiveTcl release (8.4.2) as well. > I tried both 8.3.5 and 8.4.1 and in the both cases I have a warnings during > the compilation but the compilation passed without errors > and then, when I try to load the DLL it just crashes the tclshell(83 and > 84) Please try again with the current CVS HEAD and see if the problem persists. If not, post the compiler warnings here. (There are still a few warnings related to unused variables, these should be harmless). > And one more question: do you have any progress on the "Unicode" issue? What issue is that? I'm not aware of any problems in that area. --Joe English jen...@fl... |
From: Moisei R. <mra...@il...> - 2003-04-02 14:21:58
|
Hello dear All. I just wondering what version of TCL should be used when compile the latest version of tcldompro? (My env is: Windows 2000, SP3.) I tried both 8.3.5 and 8.4.1 and in the both cases I have a warnings during the compilation but the compilation passed without errors and then, when I try to load the DLL it just crashes the tclshell(83 and 84) And one more question: do you have any progress on the "Unicode" issue? Thanks, Best Regards, Moisei Joe English <jen...@fl...> To: tcl...@li... Sent by: cc: tcl...@li...ur Subject: Re: [Tclxml-users] building TclDOMPro on Windows ceforge.net 04/02/2003 06:12 AM Update on the tcldompro Windows build: I've updated the build system to use the new tcl.m4, and it's mostly working with MSVC. It appears to compile and link OK with cygwin+gcc, but the interpreter locks up when you try to [load] the .DLL. I suspect CYGWIN problems. Have to go home now, will fight with this some more tomorrow. More later. Haven't checked anything into CVS yet, it's still a bit of a mess and still basically broken. --Joe English jen...@fl... ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Tclxml-users mailing list Tcl...@li... https://lists.sourceforge.net/lists/listinfo/tclxml-users |
From: Larry W. V. <lv...@ca...> - 2003-04-02 12:08:11
|
http://www.cs.man.ac.uk/fellowsd-bin/TIP/131.html - an April 1 proposal for a "Read the developer's mind and do what he wants" command for Tcl... -- 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. -><- |
From: Joe E. <jen...@fl...> - 2003-04-02 04:13:00
|
Update on the tcldompro Windows build: I've updated the build system to use the new tcl.m4, and it's mostly working with MSVC. It appears to compile and link OK with cygwin+gcc, but the interpreter locks up when you try to [load] the .DLL. I suspect CYGWIN problems. Have to go home now, will fight with this some more tomorrow. More later. Haven't checked anything into CVS yet, it's still a bit of a mess and still basically broken. --Joe English jen...@fl... |
From: Forest W <lyr...@ti...> - 2003-04-01 01:56:46
|
>Isn't this an excellent example of the need that TIP #131 will address? > >Michael TIP #131? What's that? |
From: Michael A. C. <mi...@cl...> - 2003-04-01 01:40:31
|
On Mon, 31 Mar 2003, Joe English wrote: > I was afraid you were going to ask about that next :-( > Let me get back to you in a few days... This may be a case > of "edit the Makefile by hand..." Joe, Isn't this an excellent example of the need that TIP #131 will address? Michael |
From: Joe E. <jen...@fl...> - 2003-04-01 01:29:45
|
Forest W wrote: > I'm trying to build TclDOMPro (from the tcldom/src directory) on > Windows, but I don't see anything that looks like a windows makefile, > and ./configure dies this message under cygwin: > > "checking for expat library... Usage: cygpath (-d|-m|-u|-w|-t TYPE) > [-c HANDLE] [-f FILE] [options] NAME" > > How do I build TclDOMPro on Windows? I was afraid you were going to ask about that next :-( Truth is, I've never built it on Windows. You can try: sh configure --with-expat=/some/path where /some/path is the directory containing the expat archive library. But that probably won't work either, there's other stuff that needs to be ported. Also: cygwin might not work very well for compiling Tcl extensions. AFAIK, mingw and MSVC are the currently-recommended compilers. Let me get back to you in a few days... This may be a case of "edit the Makefile by hand..." --Joe English jen...@fl... |
From: Steve B. <Ste...@zv...> - 2003-04-01 00:37:34
|
Forest W wrote: >>The 'src' subdirectory is independent of the top-level directory; >>"cd src ; ./configure ; make ; make install" should do the trick. > > Wait a minute. Independent? Are you saying that, if I get the > TclDOMPro code in tcldom/src to build and install, it will work > without requiring any code from the parent directory, or from tclxml? Joe has already answered this, but yes. tcldom/src is completely independant - I maintain the parent directory and Joe maintains the src directory. > Out of curiosity: > > Is TclDOMPro now officially called TclDOM/C? Yes. This is a (relatively) new naming convention I adopted last year in order to correctly identify the various subprojects. > Will it continue to be supported, or is it being dropped in favor of > libxml2? Joe is maintaining that code, so you would have to ask him. As long as someone maintains it, it won't be dropped. My efforts are going into the libxml2 wrapper, since I believe that gives me more leverage. 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 |
From: Forest W <lyr...@ti...> - 2003-03-31 22:04:27
|
I'm trying to build TclDOMPro (from the tcldom/src directory) on Windows, but I don't see anything that looks like a windows makefile, and ./configure dies this message under cygwin: "checking for expat library... Usage: cygpath (-d|-m|-u|-w|-t TYPE) [-c HANDLE] [-f FILE] [options] NAME" How do I build TclDOMPro on Windows? |
From: Forest W <lyr...@ti...> - 2003-03-28 22:02:18
|
>[ Forest -- are you subscribed to the tclxml-users list, I am subscribed. >> 1. Replace #include <xmlparse.h> with #include <expat.h> in the >> tcldom/src code. >> >> 2. Fix the "incompatible pointer type" warnings when building the >> tcldom/src code. > >Already done (see previous message), fix is now in CVS. Thank you. I just checked out the current HEAD, and built against expat-1.95.6 on solaris with no warnings or errors. I'll try building on other platforms and try using it with tclsoap later today. |