You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(10) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(3) |
2002 |
Jan
(2) |
Feb
(8) |
Mar
(1) |
Apr
(1) |
May
(5) |
Jun
(1) |
Jul
(1) |
Aug
(5) |
Sep
(2) |
Oct
(8) |
Nov
(3) |
Dec
(3) |
2003 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2004 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Steve B. <Ste...@zv...> - 2002-11-08 21:57:40
|
Hi Andreas, You wrote: > your latest change to tclxslt/tclxslt.h > > #include > to #include > > breaks all unix builds, and windows. Reason > > Tcldom./libxml2 installs its headers in > > $prefix/include > > I.e. $prefix/include/tcldom-libxml2.h > > As TclXSLT uses -I$prefix/include it finds the header. > Now with tcldom-libxml2/tcldom-libxml2.h the header is > searched for in a different place, and not found. > > Is there a way to conditionalize the #include for Darwin ? I expected there would be problems... was going to work on fixing them next. Yes, Mac OS X frameworks are strange beasts and the change was necessary to accommodate them. I was going to adapt the header installation to fixup finding the libraries, so that the source code doesn't need to change. In any case, I'll work on getting it fixed and updates committed today (it is Saturday now, so no guarantees). Cheers, Steve -- 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: Andreas K. <and...@Ac...> - 2002-11-04 21:47:37
|
> -----Original Message----- > From: Steve Ball [mailto:Ste...@zv...] > Sent: Monday, November 04, 2002 1:46 PM > To: Andreas Kupries > Cc: Jeff Hobbs; tclxml-devel > Subject: Re: TclDOM/libxml2, TclXSLT - Tcl 8.3.5 > > > Hi Andreas, > > You wrote: > > > I was wrong in this. Bad memory. The old API is 'TclpGetTime', > > and it is available via the internal stub table of Tcl 8.3.5. > > > > So TclDOM/libxml2 could be made to configure and run with 8.3.5. > > Question is, should we ? > I've made a note in the source code. It is only used in > one place, as part of the event system. My preferred > option would be to simply put in a macro that disables > the use of the time function if TCL_VERSION < 8.4 > and document the lack of functionality in 8.3.5 (and earlier) > in the man page. Oh, so this is an external XSLT function provided by Tcl and not something from the standard ? ... Ok, just removing that functionality for 8.3.5 would be an easy solution. I won't object if you do it that way. Just tell which way you went. > Cheers, > Steve Ball -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com |
From: Steve B. <Ste...@zv...> - 2002-11-04 21:43:10
|
Hi Andreas, You wrote: > I was wrong in this. Bad memory. The old API is 'TclpGetTime', > and it is available via the internal stub table of Tcl 8.3.5. > > So TclDOM/libxml2 could be made to configure and run with 8.3.5. > Question is, should we ? I've made a note in the source code. It is only used in one place, as part of the event system. My preferred option would be to simply put in a macro that disables the use of the time function if TCL_VERSION < 8.4 and document the lack of functionality in 8.3.5 (and earlier) in the man page. 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: Steve B. <Ste...@zv...> - 2002-10-31 20:01:47
|
Lothar Arndt wrote: > As well I noticed that there is no configure script in tcldom/, however > tcldom/src-libxml2/ holds a configure script. What is expected in > tclxslt ? Should there be a configure script or not? If yes, I can > provide it. I've been removing all files from the CVS repository that are generated. Before releasing the package I generate these files for the tarball/zipfile. This ensures that files that might possibly be stale do not go into the release. Also in this category are the HTML and nroff man pages. 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: Andreas K. <and...@Ac...> - 2002-10-30 23:01:47
|
> -----Original Message----- > From: Steve Ball [mailto:Ste...@zv...] > Sent: Wednesday, October 30, 2002 3:03 PM > To: Andreas Kupries > Cc: Lothar Arndt; tclxml-devel > Subject: Re: Tcldom - update > > > > >Eastern-Aussie-time (Melbourne-ACT-Sydney) is 10 hours ahead of > > >mideuropean time. > > > > > > Ok, so Steve is 19 hours ahead of me. I'll have to jot that down > > somewhere. > > The Sun never sets on the TclXML empire... > > Keep up the good work! > > BTW, I'll work on the TclDOMDeleteEvent problem - > that's a showstopper bug. There's already a SF bug report > on that topic. Oh, I hadn't noticed. I just worked from the warnings I got from the VC++ compiler. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com |
From: Steve B. <Ste...@zv...> - 2002-10-30 22:59:32
|
> >Eastern-Aussie-time (Melbourne-ACT-Sydney) is 10 hours ahead of > >mideuropean time. > > > Ok, so Steve is 19 hours ahead of me. I'll have to jot that down > somewhere. The Sun never sets on the TclXML empire... Keep up the good work! BTW, I'll work on the TclDOMDeleteEvent problem - that's a showstopper bug. There's already a SF bug report on that topic. Cheers, Steve -- 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: Steve B. <Ste...@zv...> - 2002-10-29 07:01:17
|
TclXML v2.4 Release Candidate 1 is now available. As previously noted, the aim of this release is to fix build & install problems. PLEASE download and try installing this preview release, and submit bug reports if there are any difficulties. NB. Testing the various combinations of build configurations is now non-trivial. To keep track of which platforms are known to work I've added a section to RELNOTES for platform installation testing. I've filled in those sections that I've personally tested, but I need others to fill in the blanks. If you've built, installed and tested TclXML on a particular platform successfully then fill in your initials and cvs commit the change. V2.4 features a new TEA2 build system and improved stubs. There have been some bug fixes, but at this stage these are being kept to a minimum so that this release does not get too out-of-sync with the ActiveTcl 8.4.1.0, which includes a TclXML package named "2.4". 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 |
From: Steve B. <Ste...@zv...> - 2002-10-23 21:11:47
|
Dear TclXML'ers, Just thought I'd discuss release plans with everyone. Changes to the TclXML family for easier building and installation are quite urgent, so that's the focus of the upcoming v2.4 release. Now that I've got TclXSLT TEA2'ified all that remains is to test the building and configuration on most popular platforms and once that is satisfactory, and any show-stopper bugs fixed, make the release. Other outstanding bugs and patches will have to wait for the v2.5 release, which we can start working on after v2.4 is out-the-door. I would hope to have v2.5 released a month or so after v2.4. The next thing to do after that is v3.0. 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: Steve B. <Ste...@zv...> - 2002-10-21 07:43:52
|
FYI, I upgraded the TclXSLT package to use TEA2. Committed the changes this morning. One thing to note is that I have changed the pkgIndex.tcl.in script to detect if the system is "Darwin" (iow Mac OS X) and find the dylib in the appropriate place. However, it assumes that the package has been installed as a Framework, which is not necessarily true. I'll need to modify the TEA setup (ie the configure script) to know about Frameworks so that pkgIndex.tcl can revert to its normal state. Stay tuned... Cheers, Steve -- 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: Steve B. <Ste...@zv...> - 2002-10-15 21:17:28
|
Hi Lothar, I'm cc'ing this to the tclxml-devel mailing list, as it is of more general interest. For the benefit of others on the mailing list, Lothar has joined the TclXML project and has an interest in getting TclXSLT working well. You wrote: > I can support the build of V2.4 of tclxslt on Suse Linux - this is my > private box. As I have temporarily access to a HPUX, AIX and Solaris box > I could then try to run the test suite there as well. My company has a need for a HPUX build as well, so would be very helpful. When you run the test suite, bear in mind that it is a known problem that not all of the tests pass. In many cases, these "failures" are not really a problem. > At the moment I'm most interessted in tclxslt, as I just need it. I have > a feeling what sort of problem I was running into with this > "segmentation violation" ......linking the library statically into the > tclsh seems to work now. Then that indicates some kind of problem in how the shared library gets built. I'd suggest looking at how Andreas has setup TclXML and TclDOM for TEA2 and applying that to TclXSLT. > What I will do now is, setup a proper Makefile.in and config.in for > tclxslt2.3 to make it run properly with using shared libs. So far I was > just trying to "MacDo" the Makefile, but I think that is not a good idea. I don't know what "MacDo" is... > Once I made version 2.3 work I could then shift over this experience > into 2.4. Would that be a good starting point ? Certainly. It should be fairly easy to merge the changes into the CVS head at this stage. > So, that's it for today. Tell me, what's the weather like in canberra ? > Over here (around Stuttgart/Germany) we are going towards winter in big > steps. However, I have been in canberra for christmas in '98 and it was > very cold. Somebody even told me that they had snow in the mountains. I > haven't seen any, but temperaturewise I could believe that easliy. At the moment we are getting typical spring weather; beautiful days most of the time, but reverting to cold(-ish) overcast days - just to remind us that winter has only just ended. Looking out my window it looks like it will be a lovely day, probably around 20-22 deg. We're looking forward to Xmas, though it doesn't really start to get hot until January/February (when it can get to 40 some days). Real beer drinking season! 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: Steve B. <Ste...@zv...> - 2002-10-15 03:40:20
|
FYI, I have bumped the package version numbers to 2.4 in the TclXML, TclDOM and TclXSLT CVS trees. Obviously, this is in preparation for the v2.4 release. NB. work has not yet finished on the next release, so don't be surprised if some things fail. I'll be making candidate releases soon in order to shake some bugs out. 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: Steve B. <Ste...@zv...> - 2002-09-24 21:26:25
|
Hi All, Back from the Tcl Conference now... those trans-Pacific flights are such a joy because they give you a loooong time to hack code! Well, at least until the TiBook's battery runs out ;-) I have checked in my changes to the TclXML, TclDOM and TclXSLT packages. The main additions are to TclXSLT; extension elements have been implemented as well as preservation of XPath object data types. Implementing extension elements has opened a can of worms :-( I'd stear clear of them until I've sorted out the implications. Specifically, making nodes in the stylesheet available to the application conflicts with TclDOM, since both TclDOM and libxslt use the _private hook in the xmlNode structure. Preserving XPath object data types is a happier story. XPath objects have four types: nodeset, boolean, number and string. These are mapped to a Tcl list of TclDOM nodes, boolean, double and (surprise) string objects. The return result Tcl_Obj is mapped back to one of the XPath data types. No more pesky parsing of string values! 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 |
From: Steve B. <Ste...@zv...> - 2002-09-09 10:56:37
|
This morning the TclXML trio - TclXML, TclDOM and TclXSLT - were uploaded to SourceForge as version 2.3 release candidate 2. My intention is to make the final release of v2.3 before leaving for Vancouver on Saturday. So PLEASE check these distributions out and let me know about any problems ASAP! Most likely day for cutting the final release will be Thursday or Friday. I've closed all major outstanding bugs for the packages, but there remain several bug reports assigned to other developers. Please either close the bugs or let me know their status. 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: Steve B. <Ste...@zv...> - 2002-08-29 07:41:29
|
TclDOM v2.3 Release Candidate 1 is now available on SourceForge. Given the problems with TclDOM v2.2, I'm being a little more cautious with this next release %-} Please download the rc1 release and give it a try. Report any installation or build problems via the SF bug tracking system. NB. While I have tested the pure-Tcl installation, I *HAVE NOT* tested the 'configure/make/make install' build method, though I have run autoconf for this release. My expectation is that *someone* will attempt to build TclDOM and/or TclDOM/libxml2 using 'configure/make/make install' and if there are problems (which I fully expect) submit a patch. I no longer use configure, so there is little point in doing that testing myself. 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 |
From: Steve B. <Ste...@zv...> - 2002-08-13 21:06:28
|
As noted in my previous message, I will be focusing on libxml2 support in TclDOM in the forseeable future. Now, as part of making a v2.2 release of TclXML I had a quick look at the expat wrapper. This module is now quite outdated wrt to the version of expat on SourceForge (http://sourceforge.net/projects/expat). For the purpose of getting v2.2 out in a reasonable time I'll just work with the current (old) sources, but is anyone willing to adopt this module and bring it into line with the SF expat? There appears to be a modest amount of engineering involved - not trivial, but not overwhelming either. 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: Steve B. <Ste...@zv...> - 2002-08-13 21:01:36
|
Now that TclDOM & TclXSLT v2.2 have been released, I thought it might be helpful to provide a roadmap for future development of the TclXML family; at least the part that I'm responsible for. Most of my effort has been concentrated on libxml2/libxslt support. This will continue into the future. In the short-term I'm planning on releasing v2.2 of the TclXML package. This should (must) occur before the Tcl Conference. This release will simply catch-up on bug fixes, patches, etc, that have been backlogged. I only just realised that it's been over a year since the last TclXML release :-( After that the next phase will be to work on a v3.0 release of all the packages. There are two major changes planned: i. move libxml2 support into the TclXML package. This will allow access to the SAX interface of the parser, as well as validation support, XPath, etc. ii. Revamp the TclDOM API. The "generic-layer" concept hasn't really worked out very well, so I'm dropping it. There will be no notion of loading multiple DOM implementations into a single Tcl interpreter. Instead, a single implementation will provide all of the features of the API and the package loading mechanism will take care of finding a package to load. The issue of node Tcl commands also rears its ugly head (ala tDOM). The current implementation of TclDOM/libxml2 creates hash tables to keep track of node string reps, and I suspect that there are no efficiency gains in not defining Tcl commands for DOM nodes. I will do some experimentation. As noted on the website, version numbers for TclXML, TclDOM and TclXSLT will be synchronised. In future, all three will be released simultaneously, just like Tcl and Tk. Of course, I have no timetable at this stage for the v3.0 release. Please send your comments, 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: Steve B. <Ste...@zv...> - 2002-08-09 10:57:57
|
Apologies for the spam that slipped through. I have changed the mailing list configuration to hopefully prevent any more being sent to the list. 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: <gwe...@em...> - 2002-08-08 20:34:01
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!-- saved from url=(0025)http://www.mealstogo.com/ --> <!-- saved from url=(0022)http://internet.e-mail --><HTML><HEAD><TITLE>Mealstogo : Bay Area's restaurant menus and restaurant delivery services. Food delivery in Bay Area, catering in Bay Area, food catering, Bay Area restaurant menus, restaurant food, restaurant delivery services, restaurant take out, togo restaurant delivery, togo food delivery, togo delivery service, togo restaurant menus, togo take out,togo Bay Area, togo catering, Bay Area catering, catering menus, restaurant catering, catering delivery service, office food delivery, office catering, business catering, business food delivery, office lunch, Bay Area's restaurant delivery services!</TITLE> <META content="text/html; charset=windows-1252" http-equiv=Content-Type> <META content="Updated restaurant menus for Dine-in, Pick-up and Delivery. To Go! is a unique delivery service that picks up meals from Bay Area's best restaurants and delivers them to your home or office in about an hour." name=description> <META content="Bay Area's restaurant menus and restaurant food delivery services. Food delivery in Bay Area, catering in Bay Area, food catering, Bay Area restaurant menus, restaurant food, restaurant delivery services, restaurant take out, togo restaurant delivery, togo food delivery, togo delivery service, togo restaurant menus, togo take out,togo Bay Area, togo catering, Bay Area catering, catering menus, restaurant catering, catering delivery service, office food delivery, office catering, business catering, business food delivery, office lunch, Bay Area's restaurant delivery services." name=keywords> <META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD> <BODY bgColor=#ffffff> <P> <TABLE border=0 width="100%"> <TBODY> <TR> <TD width="100%"> <P> <CENTER><IMG align=top height=100 src="http://www.mealstogo.com/logo500.gif" width=480><BR><FONT color=#00af00 face="Arial, Helvetica, sans-serif"></FONT><FONT color=#000000 size=+1>SAN FRANCISCO : 1-800-853-0211 PENINSULA : (650) 692-4200 <BR>Fax (650) 692-4882<BR><FONT face="Arial, Helvetica, sans-serif" size=-1></FONT>Delivery Charge: $8.00 Minimum Order: $15.00 Suggested Gratuity: 12%<BR>Hours:M-F 9:30-2:00PM 4:30-9:00PM , SAT & SUN's:4:30-9:00 PM</FONT><FONT size=-1><BR><FONT color=#ff0000 face="Arial, Helvetica, sans-serif" size=2><B>Please Select Your City for Restaurant Choices and Menus. <BR></B></FONT><B><FONT color=#008b00 face="Arial, Helvetica, sans-serif"></FONT></B><FONT color=#00af00 size=+1></FONT><FONT color=#00af00><A href="http://www.mealstogo.com/_SF.html"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[SAN FRANCISCO] </font></a><FONT color=#00af00 size=+1><A href="http://www.mealstogo.com/_mil.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1><BR></font></A><FONT color=#00af00 size=+1><A href="http://www.mealstogo.com/_ssf.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[South SF & Brisbane] </font></A><FONT color=#00af00 size=+1><A href="http://www.mealstogo.com/_mil.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Millbrae]</FONT></A> <A href="http://www.mealstogo.com/_bur.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Burlingame]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_hil.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Hillsborough]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_sm.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[San Mateo]</font></A><FONT color=#00af00 size=+1><BR><A href="http://www.mealstogo.com/_fc.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Foster City]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_bel.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Belmont]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_sc.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[San Carlos]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_rs.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Redwoodshores]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_rc.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Redwood City]</font></A><FONT color=#00af00 size=+1><BR><A href="http://www.mealstogo.com/_ath.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Atherton]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_mp.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Menlo Park]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_pa.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Palo Alto]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_la.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Los Altos]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_mv.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Mt. View]</font></A><FONT color=#00af00 size=+1> <A href="http://www.mealstogo.com/_sv.htm"><FONT face="Arial, Helvetica, sans-serif"></FONT><FONT color=#00af00 size=+1>[Sunnyvale]</font></A> </font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></CENTER><FONT size=-1><FONT color=#00af00><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1> <CENTER> <FONT color=#ffffff size=1><IMG align=bottom height=125 src="http://www.mealstogo.com/burger1.jpg" vspace=3 width=130></FONT><FONT color=#ffffff size=1>|</FONT><FONT color=#00af00 size=+1><IMG align=bottom src="http://www.mealstogo.com/ctogo.gif" vspace=6></FONT><FONT color=#ffffff size=1>|</FONT><FONT color=#00af00 size=+1><IMG align=bottom height=125 src="http://www.mealstogo.com/soup1.jpg" vspace=3 width=130><BR> <FONT color=#ff0000 face="Arial, Helvetica, sans-serif" size=2><B>YOUR RESTAURANT DELIVERY SERVICE<BR>Delivers from over 125 Bay Area restaurants. Established since 1992</B></FONT><BR></FONT><B><FONT color=#00af00><A href="mailto:Da...@me..." target=""><FONT face="Arial, Helvetica, sans-serif" size=2>Feedbacks, Comments and Suggestions</FONT></A></FONT></B> </CENTER> <CENTER><a><FONT color=#00af00 size=+1><IMG align=absMiddle border=0 height=20 hspace=6 src="http://counter.digits.com/wc/-rz/-d/6/kwsta" vspace=2 width=90></FONT> </a> </CENTER></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT></FONT><A><FONT size=-1><FONT color=#00af00><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1><FONT color=#00af00 size=+1></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></a></TD></TR></TBODY></TABLE><p> </p> <p><br> <font size="2">To be optout from our future mailing please email op...@em... </font></P> <p><font size="2">You can also opt out by mail; Please send your request to: </font></p> <p><font size="2">11314 Ventura Blvd Suite #141 <br> Studio City, CA 91604</font></p> <p><font size="2">Or by Phone (213) 216 8305</font></p> </BODY></HTML> |
From: <en...@ao...> - 2002-07-22 18:48:33
|
subscribe = __________________________________________________________________________= _______ Eric Newman =95 System Architect =95 Web Systems & Publishing - AOL/TW Ph. (703) 265-1579 | Cell:(703) 728-1021 | 2-way Pager:(888) 260-1117 mailto:888...@ai...= |
From: Ed S. <ed...@ee...> - 2002-06-09 14:51:27
|
I spent half the day yesterday working on XMLGEN, mostly doing cleanup to make the code work on my TCL installation (8.4a4, Windows 2000) and more easy to work with. One fairly major step I took was avoiding any potentially disruptive changes to core TCL commands (i.e., renaming puts to tclputs) by using the proc "putx" (which means "put xml") instead of a modified puts ("put string"). Since this is mostly used internally to XMLGEN/HTMLGEN, I don't think the change should cause anyone any heartburn. It will certainly result in less heartburn for users who would otherwise have to change any code that uses the "puts" command, e.g., for writing out html to files. Now I'm working on a WEBUTILS extension that preprocesses plain text into proto-html with links, formatted spans, and smart quotes: #<<<<<<<<<<<< LINKSUB >>>>>>>>>>>>>># # linksub ?-class <class>? ?-wwwclass <wwwclass>? ?-domains <list>? ?-autowww? subList string # class = CSS class name for normal links # wwwclass = CSS class name for links starting with "www." # domains = list of recognized domains, without leading "." # subList = keyword/link pairs. "http://" will be added if # omitted and link is to a known domain from optional # list -domains <list> # Modifies string in stringName #<<<<<<<<<<<< SPANSUB >>>>>>>>>>>>>># # spansub stringName subList # subList = keyword/class pairs. # Modifies string in stringName #<<<<<<<<<<<< PUNCTSUB >>>>>>>>>>>>>># # punctsub ?-smart? stringName subList # smart = specify if proc should try using smart quotes # Modifies string in stringName Please take a look at the diffs below and reply with any comments before I do the commit. Thanks, Ed =================================================================== RCS file: /cvsroot/tclxml/xmlgen/LICENSE,v retrieving revision 1.1 diff -r1.1 LICENSE 15c15 < * The name of the contributors may be used to endorse or promote --- > * The name of the contributors may not be used to endorse or promote Index: htmlgen.tcl =================================================================== RCS file: /cvsroot/tclxml/xmlgen/htmlgen.tcl,v retrieving revision 1.2 diff -r1.2 htmlgen.tcl 18c18 < namespace import ::xmlgen::buffer ::xmlgen::put ::xmlgen::esc --- > namespace import -force ::xmlgen::buffer ::xmlgen::put ::xmlgen::esc 56a57,58 > # Note: import of 'dir' will overwrite TCL's internal 'dir' command, > # which is used in TKCON but probably not otherwise 91c93 < puts "<pre>[esc $::errorInfo]</pre>" --- > putx "<pre>[esc $::errorInfo]</pre>" 93c95 < puts "<pre>cgi script error encountered</pre>" --- > putx "<pre>cgi script error encountered</pre>" 112c114 < if {"[file tail $argv0]"!=[file tail [info script]]} return --- > if { ![string match "[file tail $argv0]" [file tail [info script]] ] } return 115c117 < namespace import ::htmlgen::* --- > namespace import -force ::htmlgen::* 142,143c144,145 < puts [th style=$CuteStyle Eins] < puts [th Zwei] --- > putx [th style=$CuteStyle Eins] > putx [th Zwei] 185c187 < puts $Page --- > putx $Page Index: pkgIndex.tcl =================================================================== RCS file: /cvsroot/tclxml/xmlgen/pkgIndex.tcl,v retrieving revision 1.3 diff -r1.3 pkgIndex.tcl 1c1 < # I must admit that I find it much easier to write a pkgIndex.tcl by --- > # HK: I must admit that I find it much easier to write a pkgIndex.tcl by 2a3 > # EAS: Sounds fine, but tightened up the structure of the code 8d8 < 12,31c12,30 < < ##### xmlgen ##### < set script [subst -nocommands { < namespace eval ::xmlgen [list set VERSION $VERSION] < namespace eval ::xmlgen [list set VERDATE $VERDATE] < package provide xmlgen $VERSION < source [file join "$dir" xmlgen.tcl] < }] < package ifneeded xmlgen $VERSION $script < < < ##### htmlgen ##### < set script [subst -nocommands { < namespace eval ::htmlgen [list set VERSION $VERSION] < namespace eval ::htmlgen [list set VERDATE $VERDATE] < source [file join "$dir" htmlgen.tcl] < source [file join "$dir" tab.tcl] < source [file join "$dir" sidenav.tcl] < }] < package ifneeded htmlgen $VERSION $script --- > # Define the package names and sourced script files > set packageSetupList { > xmlgen {xmlgen.tcl} > htmlgen {htmlgen.tcl tab.tcl sidenav.tcl webutils.tcl} > webutils {webutils.tcl} > parse {parse.tcl} > } > > # Now setup the packages > foreach {i j} $packageSetupList { > set script [subst -nocommands { > eval namespace eval ::$i [list set VERSION $VERSION] > eval namespace eval ::$i [list set VERDATE $VERDATE] > }] > foreach {k} $j { > set script "$script ;source \[file join \"$dir\" $k\]" > } > package ifneeded $i $VERSION $script > } \ No newline at end of file Index: sidenav.tcl =================================================================== RCS file: /cvsroot/tclxml/xmlgen/sidenav.tcl,v retrieving revision 1.1 diff -r1.1 sidenav.tcl 14d13 < namespace export sidenav 16,17c15,18 < ## default values for configurable attributes of sidenav < set sidenavDefaultAttrs { --- > namespace export sidenav > > ## default values for configurable attributes of sidenav > set sidenavDefaultAttrs { 26,27c27 < navByUrl 0 < } --- > navByUrl 1 32d31 < ## 37c36 < proc ::htmlgen::sidenav::onerow {text level} { --- > proc onerow {text level} { 44a44,45 > > 48c49 < proc ::htmlgen::sidenav::digTree {current tree} { --- > proc digTree {current tree} { 59,60c60,62 < ## < ## renders a navigation tree along a path given by $current leading --- > > ######################################################################## > ## Render a navigation tree along a path given by $current leading 66c68 < ## We descent into subtrees only if $current really selects one of --- > ## We descend into subtrees only if $current really selects one of 70c72 < proc ::htmlgen::sidenav::renderTree {ID url current tree} { --- > proc renderTree {ID url current tree} { 121a124 > 134c137,138 < proc ::htmlgen::sidenav::sidenav {pathvar url tree args} { --- > > proc sidenav {pathvar url tree args} { 154,166d157 < ## If sourced by another script, its time to return < if {"-test"!=[lindex $argv 0]} return < set argv [lrange $argv 1 end] < < < < ## TEST CODE < set auto_path [concat /home/kir/work /usr/local/lib $auto_path] < #puts $auto_path < package require tcllib < package require htmlgen < namespace import htmlgen::* < namespace import ::htmlgen::sidenav::* 168,180c159,182 < < < < puts "Content-Type: text/html\n" < ::ncgi::parse < < set navtree { < home Home . < tcl Tcl { < kit TclKit . < w83 Wish83 { < story Story . < doc Documentation . --- > set testScript { > ## BEGIN TEST SCRIPT > set auto_path [concat . /home/kir/work /usr/local/lib $auto_path] > foreach {i} {tcllib htmlgen ncgi} { package require $i } > namespace import -force htmlgen::* > namespace import -force ::htmlgen::sidenav::* > > # Start of HTML Content > ::ncgi::parse > > set navTree { > home Home . > tcl Tcl { > kit TclKit . > w83 Wish83 { > story Story . > doc Documentation . > } > fw FreeWrap . > } > perl Perl { > bad {Perl No Fun} . > doc {NO DOCS} . > } 182,208c184,206 < fw FreeWrap . < } < perl Perl { < bad {Perl No Fun} . < doc {NO DOCS} . < } < } < < html ! { < body ! { < set url [ncgi::urlStub] < set Path [ncgi::value Path {tcl}] < sidenav Path $url $navtree nav.bgcolor=\#dddd55 txt.bgcolor=\#dddd00 ! { < h2 - Some Information about [join $Path /] < p + { < The selected path is < } < blockquote - [code . Path="$Path"]. < p + { < Depending on that, < we could have different content introduced here in several < ways, e.g. < } < ul ! { < li - use a [code switch on \$Path] < li - access a content array like [code \$Content(\$Path)] < li - source a file depending on \$Path --- > > html ! { > body ! { > set url [ncgi::urlStub] > set path [ncgi::value path {tcl}] > sidenav path $url $navTree nav.bgcolor=\#dddd55 txt.bgcolor=\#dddd00 ! { > h2 - Some Information about [join $path /] > p + { > The selected path is > } > blockquote - [code . path="$path"]. > p + { > Depending on that, > we could have different content introduced here in several > ways, e.g. > } > ul ! { > li - use a [code switch on \$path] > li - access a content array like [code \$Content(\$path)] > li - source a file depending on \$path > } > table ! tr ! td height=1000 - " " > } 210d207 < table ! tr ! td height=1000 - " " 212c209,212 < } --- > # Finish with regular puts to end with newline > puts {} > > ### END TEST SCRIPT 213a214,222 > > ### END NAMESPACE > } > > # Execute test script if -test option specified > if { [string match "-test" [lindex $argv 0]] } { > ::xmlgen::buffer html $::htmlgen::sidenav::testScript > set fh [open test.html w]; puts $fh $html; close $fh > } \ No newline at end of file Index: tab.tcl =================================================================== RCS file: /cvsroot/tclxml/xmlgen/tab.tcl,v retrieving revision 1.1 diff -r1.1 tab.tcl 88,89c88 < set auto_path [concat /home/kir/work /usr/local/lib $auto_path] < #puts $auto_path --- > set auto_path [concat . /home/kir/work /usr/local/lib $auto_path] 92,93c91,92 < namespace import htmlgen::* < namespace import ::htmlgen::extra::* --- > namespace import -force htmlgen::* > namespace import -force ::htmlgen::extra::* 96c95 < puts "Content-Type: text/html\n" --- > putx "Content-Type: text/html\n" 129c128 < puts [b Ooooops] --- > putx [b Ooooops] 145c144 < puts [title . a test tab] --- > putx [title . a test tab] 147c146 < puts $Page --- > putx $Page Index: xmlgen.tcl =================================================================== RCS file: /cvsroot/tclxml/xmlgen/xmlgen.tcl,v retrieving revision 1.2 diff -r1.2 xmlgen.tcl 50,51c50,54 < rename ::puts ::xmlgen::tclputs < interp alias {} ::puts {} ::xmlgen::tclputs --- > > ## EAS: This is very confusing and didn't work on my system > ## Left the original TCL puts alone and called our proc "putx" instead > # rename ::puts ::xmlgen::tclputs > interp alias {} ::putx {} ::xmlgen::putx 61c64 < proc puts {args} { --- > proc putx {args} { 63c66 < if {"-nonewline"==[lindex $args $i]} { --- > if { "-nonewline" == [lindex $args $i] } { 72,73c75,76 < if {[llength $args]-$i!=1} { < eval tclputs $args --- > if { [llength $args]-$i != 1 } { > eval puts $args 88c91 < tclputs -nonewline [join $args] --- > puts -nonewline [join $args] 100c103 < interp alias {} ::puts {} ::xmlgen::puts --- > interp alias {} ::putx {} ::xmlgen::putx 102c105,107 < interp alias {} ::puts {} ::xmlgen::tclputs --- > # EAS: Let's not do the confusing alias to tclputs anymore, because > # original puts is now left intact > # interp alias {} ::putx {} ::xmlgen::tclputs 289c294 < if {"[file tail $argv0]"!=[file tail [info script]]} return --- > if { ![string match "[file tail $argv0]" [file tail [info script]] ] } return 296c301 < namespace import ::xmlgen::* --- > namespace import -force ::xmlgen::* 303c308 < puts dddddddddddddddddd --- > putx dddddddddddddddddd 307c312 < puts dddddddddddddddddd --- > putx dddddddddddddddddd 310c315 < puts ||$Page|| --- > putx ||$Page|| Index: doc/common.tcl =================================================================== RCS file: /cvsroot/tclxml/xmlgen/doc/common.tcl,v retrieving revision 1.1 diff -r1.1 common.tcl 80c80 < lappend l [a href=$url?[cgiset Path $p] $text] --- > lappend l [a href=$url?[cgiset path $p] $text] |
From: Joe E. <jen...@fl...> - 2002-05-30 15:06:28
|
Steve Ball <Ste...@zv...> wrote: > Joe English wrote: > > (Using strings with handle semantics is actually the safest > > thing to do in the presence of [dom::DOMImplementation destroy]. > > Using a custom Tcl_ObjType can lead to Tcl_Obj's with dangling > > pointers in their internal reps if you're not _extremely_ careful.) > > TclDOM/libxml2 defines a string handle for an object, as well as > an internal rep. I maintain a hash table of string reps, > so if the object loses its internal rep it can be retrieved > from the string rep. This strategy allows faster performance > when the internal rep is preserved, but is still reliable. > > I haven't fully resolved object destruction yet. That's where the trouble comes in -- if a node is deleted, then any TclDOM_NodeObj's which have _not_ lost their internal rep will contain dangling pointers to deleted nodes. One possibility: add a reference count to the internal xmlNode structure, and increment/decrement it in the TclDOM_NodeObjType's SetFromAnyProc/FreeInternalRepProc. Or maybe associate reference counts with the owner xmlDocument. > > Even if dom::c did use a custom Tcl_ObjType, there would still > > be a danger if multiple DOMImplementations are loaded into the > > same process. > > My assumption was that having multiple implementations > simultaneously loaded might be useful for some applications. > Is that an incorrect assumption? It doesn't seem to me that this will be needed very often. At the Tcl script level, one DOMImplementation should be as good as another modulo features supported in one but not in the other. --Joe English jen...@fl... |
From: Steve B. <Ste...@zv...> - 2002-05-30 03:00:19
|
Joe English wrote: > It looks like integrating dom::c into the new Tcl-DOM > generic framework is going to be more difficult than > I first expected. Also, there are some serious pitfalls > in the generic implementation. We're still in an alpha stage with that code, so changes/ suggestions are welcome. > The main issue is that the generic layer checks the > Tcl_Obj 'typePtr' field of DOM node objects to determine > which DOM implementation created the node. dom::c doesn't > actually use a separate Tcl_ObjType to represent nodes; > instead, it uses strings with handle semantics. Yes, that didn't really work after all. Object shimmering blew that design out of the water :-( I've changed the code recently to always use the default implementation, falling back to the Tcl implementation if it fails. > (Using strings with handle semantics is actually the safest > thing to do in the presence of [dom::DOMImplementation destroy]. > Using a custom Tcl_ObjType can lead to Tcl_Obj's with dangling > pointers in their internal reps if you're not _extremely_ careful.) TclDOM/libxml2 defines a string handle for an object, as well as an internal rep. I maintain a hash table of string reps, so if the object loses its internal rep it can be retrieved from the string rep. This strategy allows faster performance when the internal rep is preserved, but is still reliable. I haven't fully resolved object destruction yet. > Even if dom::c did use a custom Tcl_ObjType, there would still > be a danger if multiple DOMImplementations are loaded into the > same process. My assumption was that having multiple implementations simultaneously loaded might be useful for some applications. Is that an incorrect assumption? What if I wanted to import nodes to/from a TclDOMPro tree into a (hypothetical) e4graph-based DOM tree? > It's very easy for the internal rep to be discarded, > and there's no way to get from the string rep back to the > DOMImplementation which created the node. That's true, see above. > If there's only one DOMImplementation registered, this > problem won't be fatal (since the generic layer will just > dispatch to the single, default, DOMImplementation), but if > there are more than one the generic layer is likely to break > badly. > > I'm not sure how to fix this. We may need to change the underlying design. The problem is allowing scripts to be portable between implementations. 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: Joe E. <jen...@fl...> - 2002-05-30 00:32:43
|
Steve et. al -- It looks like integrating dom::c into the new Tcl-DOM generic framework is going to be more difficult than I first expected. Also, there are some serious pitfalls in the generic implementation. The main issue is that the generic layer checks the Tcl_Obj 'typePtr' field of DOM node objects to determine which DOM implementation created the node. dom::c doesn't actually use a separate Tcl_ObjType to represent nodes; instead, it uses strings with handle semantics. (Using strings with handle semantics is actually the safest thing to do in the presence of [dom::DOMImplementation destroy]. Using a custom Tcl_ObjType can lead to Tcl_Obj's with dangling pointers in their internal reps if you're not _extremely_ careful.) Even if dom::c did use a custom Tcl_ObjType, there would still be a danger if multiple DOMImplementations are loaded into the same process. It's very easy for the internal rep to be discarded, and there's no way to get from the string rep back to the DOMImplementation which created the node. If there's only one DOMImplementation registered, this problem won't be fatal (since the generic layer will just dispatch to the single, default, DOMImplementation), but if there are more than one the generic layer is likely to break badly. I'm not sure how to fix this. --Joe English jen...@fl... |
From: Steve B. <Ste...@zv...> - 2002-05-29 21:27:55
|
Hi Guys, Just to let you know, I've converted the TclDOM package to use ChangeLog instead of changes. Please update your CVS trees accordingly. This is to take advantage of the ^X-4-a Emacs trick Jeff Hobbs mentioned in a c.l.t message recently (thanks Jeff!). BTW, I'd to work towards a full release of the TclDOM package. If you're planning on making changes to either the Tcl or C code please let me know, with an anticipated completion date. 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: Steve B. <Ste...@zv...> - 2002-05-20 11:41:53
|
Hi Developers, There are quite a few TclXML improvements and bug fixes mounted up, so I feel it's time to make a new release. It would be nice to include the C code (TclExpat) in this one to make it a full (rather than 'theta') release. I'm not using the TclXML C code in any of my projects at the moment (everything's going through TclDOM/libxml2), so what's the feeling out there for the readiness of TclXML/expat for release? 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 |