October 2004 - Dillo-dev - lists.mailman3.com

[Dillo-dev]protocol handler dpi for mailto:, etc.

by Lee Bigelow

Hello again, I did up a proto-type bash shell dpi for handling unsupported protocols, like mailto:, with external applications. I called it xproto. It uses the config file $HOME/dillo/protorc to decide what to do. The plugin will make a default one you can edit when it's first run. I'm working on the C version, but I'm just learning C, so it'll take me a bit. One thing I can't seem to figure out is how to send a url from the plugin to dillo and have dillo display that page. For example I would like the url gg:water to send dillo http://www.google.com/search?q=water For now I just have it open up another dillo. I tried sending <dpi cmd="open_url" url="http://www.google.com/search?q=water"> but that didn't work, booo. Again, xproto.filter.dpi is just a shell script, so play away. If you have any hints on the gg: thing let me know, please... The patch, against dillo-0.8.2: -------------------------------------- diff -pruN dillo-0.8.2/dpi/Makefile.am dillo-0.8.2-xproto/dpi/Makefile.am --- dillo-0.8.2/dpi/Makefile.am 2004-01-29 17:04:05.000000000 -0330 +++ dillo-0.8.2-xproto/dpi/Makefile.am 2004-10-31 09:51:39.000000000 -0330 @@ -5,11 +5,13 @@ downloadsdir = $(libdir)/dillo/dpi/downl ftpdir = $(libdir)/dillo/dpi/ftp httpsdir = $(libdir)/dillo/dpi/https hellodir = $(libdir)/dillo/dpi/hello +xprotodir = $(libdir)/dillo/dpi/xproto bookmarks_PROGRAMS = bookmarks.dpi downloads_PROGRAMS = downloads.dpi ftp_PROGRAMS = ftp.filter.dpi https_PROGRAMS = https.filter.dpi hello_PROGRAMS = hello.filter.dpi +xproto_PROGRAMS = xproto.filter.dpi bookmarks_dpi_LDADD = @GLIB_LIBS@ downloads_dpi_LDADD = @GLIB_LIBS@ diff -pruN dillo-0.8.2/dpi/Makefile.in dillo-0.8.2-xproto/dpi/Makefile.in --- dillo-0.8.2/dpi/Makefile.in 2004-07-06 14:31:24.000000000 -0230 +++ dillo-0.8.2-xproto/dpi/Makefile.in 2004-10-31 10:18:28.000000000 -0330 @@ -44,6 +44,7 @@ downloads_PROGRAMS = downloads.dpi$(EXEE ftp_PROGRAMS = ftp.filter.dpi$(EXEEXT) https_PROGRAMS = https.filter.dpi$(EXEEXT) hello_PROGRAMS = hello.filter.dpi$(EXEEXT) +xproto_PROGRAMS = xproto.filter.dpi$(EXEEXT) subdir = dpi DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 @@ -53,14 +54,15 @@ am__configure_deps = $(am__aclocal_m4_de mkinstalldirs = $(mkdir_p) CONFIG_HEADER = $(top_builddir)/config.h CONFIG_CLEAN_FILES = -am__installdirs = "$(DESTDIR)$(bookmarksdir)" "$(DESTDIR)$(downloadsdir)" "$(DESTDIR)$(ftpdir)" "$(DESTDIR)$(hellodir)" "$(DESTDIR)$(httpsdir)" +am__installdirs = "$(DESTDIR)$(bookmarksdir)" "$(DESTDIR)$(downloadsdir)" "$(DESTDIR)$(ftpdir)" "$(DESTDIR)$(xprotodir)" "$(DESTDIR)$(hellodir)" "$(DESTDIR)$(httpsdir)" bookmarksPROGRAMS_INSTALL = $(INSTALL_PROGRAM) downloadsPROGRAMS_INSTALL = $(INSTALL_PROGRAM) ftpPROGRAMS_INSTALL = $(INSTALL_PROGRAM) helloPROGRAMS_INSTALL = $(INSTALL_PROGRAM) +xprotoPROGRAMS_INSTALL = $(INSTALL_PROGRAM) httpsPROGRAMS_INSTALL = $(INSTALL_PROGRAM) PROGRAMS = $(bookmarks_PROGRAMS) $(downloads_PROGRAMS) $(ftp_PROGRAMS) \ - $(hello_PROGRAMS) $(https_PROGRAMS) + $(xproto_PROGRAMS) $(hello_PROGRAMS) $(https_PROGRAMS) am_bookmarks_dpi_OBJECTS = bookmarks.$(OBJEXT) bookmarks_dpi_OBJECTS = $(am_bookmarks_dpi_OBJECTS) bookmarks_dpi_DEPENDENCIES = @@ -81,7 +83,7 @@ depcomp = $(SHELL) $(top_srcdir)/depcomp am__depfiles_maybe = depfiles @AMDEP_TRUE@DEP_FILES = ./$(DEPDIR)/bookmarks.Po \ @AMDEP_TRUE@ ./$(DEPDIR)/downloads.Po ./$(DEPDIR)/ftp.Po \ -@AMDEP_TRUE@ ./$(DEPDIR)/hello.Po ./$(DEPDIR)/https.Po +@AMDEP_TRUE@ ./$(DEPDIR)/hello.Po ./$(DEPDIR)/https.Po COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) CCLD = $(CC) @@ -198,6 +200,7 @@ downloadsdir = $(libdir)/dillo/dpi/downl ftpdir = $(libdir)/dillo/dpi/ftp httpsdir = $(libdir)/dillo/dpi/https hellodir = $(libdir)/dillo/dpi/hello +xprotodir = $(libdir)/dillo/dpi/xproto bookmarks_dpi_LDADD = @GLIB_LIBS@ downloads_dpi_LDADD = @GLIB_LIBS@ ftp_filter_dpi_LDADD = @GLIB_LIBS@ @@ -333,6 +336,28 @@ uninstall-helloPROGRAMS: clean-helloPROGRAMS: -test -z "$(hello_PROGRAMS)" || rm -f $(hello_PROGRAMS) + +install-xprotoPROGRAMS: $(xproto_PROGRAMS) + @$(NORMAL_INSTALL) + test -z "$(xprotodir)" || $(mkdir_p) "$(DESTDIR)$(xprotodir)" + @list='$(xproto_PROGRAMS)'; for p in $$list; do \ + p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \ + if test -f $$p \ + ; then \ + f=`echo "$$p1" | sed 's,^.*/,,;$(transform);s/$$/$(EXEEXT)/'`; \ + echo " $(INSTALL_PROGRAM_ENV) $(xprotoPROGRAMS_INSTALL) '$$p' '$(DESTDIR)$(xprotodir)/$$f'"; \ + $(INSTALL_PROGRAM_ENV) $(xprotoPROGRAMS_INSTALL) "$$p" "$(DESTDIR)$(xprotodir)/$$f" || exit 1; \ + else :; fi; \ + done + +uninstall-xprotoPROGRAMS: + @$(NORMAL_UNINSTALL) + @list='$(xproto_PROGRAMS)'; for p in $$list; do \ + f=`echo "$$p" | sed 's,^.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/'`; \ + echo " rm -f '$(DESTDIR)$(xprotodir)/$$f'"; \ + rm -f "$(DESTDIR)$(xprotodir)/$$f"; \ + done + install-httpsPROGRAMS: $(https_PROGRAMS) @$(NORMAL_INSTALL) test -z "$(httpsdir)" || $(mkdir_p) "$(DESTDIR)$(httpsdir)" @@ -480,7 +505,7 @@ check-am: all-am check: check-am all-am: Makefile $(PROGRAMS) installdirs: - for dir in "$(DESTDIR)$(bookmarksdir)" "$(DESTDIR)$(downloadsdir)" "$(DESTDIR)$(ftpdir)" "$(DESTDIR)$(hellodir)" "$(DESTDIR)$(httpsdir)"; do \ + for dir in "$(DESTDIR)$(bookmarksdir)" "$(DESTDIR)$(downloadsdir)" "$(DESTDIR)$(ftpdir)" "$(DESTDIR)$(xprotodir)" "$(DESTDIR)$(hellodir)" "$(DESTDIR)$(httpsdir)"; do \ test -z "$$dir" || $(mkdir_p) "$$dir"; \ done install: install-am @@ -530,7 +555,7 @@ info: info-am info-am: install-data-am: install-bookmarksPROGRAMS install-downloadsPROGRAMS \ - install-ftpPROGRAMS install-helloPROGRAMS \ + install-ftpPROGRAMS install-helloPROGRAMS install-xprotoPROGRAMS \ install-httpsPROGRAMS install-exec-am: @@ -560,7 +585,7 @@ ps-am: uninstall-am: uninstall-bookmarksPROGRAMS uninstall-downloadsPROGRAMS \ uninstall-ftpPROGRAMS uninstall-helloPROGRAMS \ - uninstall-httpsPROGRAMS uninstall-info-am + uninstall-httpsPROGRAMS uninstall-xprotoPROGRAMS uninstall-info-am .PHONY: CTAGS GTAGS all all-am check check-am clean \ clean-bookmarksPROGRAMS clean-downloadsPROGRAMS \ @@ -570,14 +595,14 @@ uninstall-am: uninstall-bookmarksPROGRAM html-am info info-am install install-am \ install-bookmarksPROGRAMS install-data install-data-am \ install-downloadsPROGRAMS install-exec install-exec-am \ - install-ftpPROGRAMS install-helloPROGRAMS \ + install-ftpPROGRAMS install-xprotoPROGRAMS install-helloPROGRAMS \ install-httpsPROGRAMS install-info install-info-am install-man \ install-strip installcheck installcheck-am installdirs \ maintainer-clean maintainer-clean-generic mostlyclean \ mostlyclean-compile mostlyclean-generic pdf pdf-am ps ps-am \ tags uninstall uninstall-am uninstall-bookmarksPROGRAMS \ uninstall-downloadsPROGRAMS uninstall-ftpPROGRAMS \ - uninstall-helloPROGRAMS uninstall-httpsPROGRAMS \ + uninstall-xprotoPROGRAMS uninstall-helloPROGRAMS uninstall-httpsPROGRAMS \ uninstall-info-am # Tell versions [3.59,3.63) of GNU make to not export all variables. diff -pruN dillo-0.8.2/dpi/xproto.filter.dpi dillo-0.8.2-xproto/dpi/xproto.filter.dpi --- dillo-0.8.2/dpi/xproto.filter.dpi 1969-12-31 20:30:00.000000000 -0330 +++ dillo-0.8.2-xproto/dpi/xproto.filter.dpi 2004-10-31 09:44:40.000000000 -0330 @@ -0,0 +1,64 @@ +#!/bin/bash +read -d'>' dpip_tag + +url=${dpip_tag##*url=\'} +url=${url%\'} +dproto=${url%%:*} +ddata=${url#*:} + +confdir="$HOME/.dillo" +if [ ! -d "$confdir" ]; then + if ! mkdir $confdir; then + msg="Error, could not make directory $confdir" + fi +else + conffile="$confdir/xprotorc" +fi + +if [ "$conffile" ]; then + if [ ! -e "$conffile" ]; then + echo " +# %d is replaced with just the data after the : +# %s is replaced with the full url +ed2k; ed2k.sh %s +mailto; sylpheed --compose %d +rtsp; realplay %s +gg; dillo http://www.google.com/search?q=%d" > $conffile + fi + if [ -e "$conffile" ]; then + while read line; do + line=${line%%#*} + fproto=${line%%;*} + if [ x"$fproto" = x"$dproto" ]; then + handler=${line#*;} + break + fi + done < $conffile + else + msg="Error, could not create file $conffile" + fi +fi + +if [ "$handler" ]; then + handler=${handler//\\%s/"$url"} + handler=${handler//\\%d/"$ddata"} + msg="Using: $handler" + output=$($handler &) +else + msg="No handler registered for protocol: $dproto +Please edit the config file: $conffile" +fi + +cat <<EOF +<dpi cmd="start_send_page" url="dpi:/xproto/xproto.filter.dpi"> +Content-type: text/html + +<html> +<head><title>Xproto Feedback</title></head> +<body> +<hr><h1>Xproto Feedback</hq><hr> +<pre>$msg</pre> +<h3>Command Output, If Any:</h3> +<pre>$output</pre> +</body></html> +EOF diff -pruN dillo-0.8.2/src/capi.c dillo-0.8.2-xproto/src/capi.c --- dillo-0.8.2/src/capi.c 2004-05-21 19:43:07.000000000 -0230 +++ dillo-0.8.2-xproto/src/capi.c 2004-10-31 06:03:28.000000000 -0330 @@ -247,6 +247,9 @@ gint a_Capi_url_uses_dpi(gchar *url_str, } else if (g_strncasecmp(url_str, "https:/", 7) == 0) { server = g_strdup("https"); + + } else { + server = g_strdup("xproto"); } return ((*server_ptr = server) ? 1 : 0); diff -pruN dillo-0.8.2/src/IO/Url.c dillo-0.8.2-xproto/src/IO/Url.c --- dillo-0.8.2/src/IO/Url.c 2004-05-21 19:43:29.000000000 -0230 +++ dillo-0.8.2-xproto/src/IO/Url.c 2004-10-31 06:19:57.000000000 -0330 @@ -108,6 +108,6 @@ ChainFunction_t a_Url_get_ccc_funct(cons if ( j == KeyLen ) return cccList[i].cccFunction; } - return NULL; + return a_Dpi_ccc; } -- Lee Bigelow Blatch Enterprises <ligelowbee(a)yahoo.com>

Oct. 31, 2004

Re: [Dillo-dev]meta refresh patch for 0.8.2

by Brian Hechinger

On Fri, Oct 29, 2004 at 02:58:20PM -0300, Jorge Arellano Cid wrote: > Hi Brian, > > Sorry for the delayed answer, I had a lot of work with the > release and now I'm trying to catch up. not a problem. > Cookies will most probably end being a dpi server (to solve the > problem of enabling cookies in multiple Dillo instances). This > was planned long ago and hasn't been realized because of lack of > manpower (aka priorities :-). ok. > The configuration data problem (cacherc, cookiesrc, dillorc, > <dpi-name>rc) is also a general issue that we're considering with > Sebastian. Maybe it will all end in a generic preferences dpi; > this needs some further thought. ok, in that case, i'm going to leave things as they are the way i did them for now, when it is decided how configuration will be handled, i'd be more than happy to work on that to get it done. > Soon a prioritized task list will be available in dillo-dev (I > just sent back a good draft to Seb.). This account for what we, > the core developers, will be doing the next months. ok, i can't wait!! > The good news is that tasks that get lower priorities can be > advanced by the interested volunteers. you can count me in on this as well. > Please stay tuned, we're trying to cope with all the work we > have, by organizing the work. The cache issues intersect with SSL > (needs cache control), preferences handling, cookies dpi server, > and the universal CCC branch idea). When the commented task list > is posted, you'll get the idea. ok, at that point we can start discussing how things will be done as relates to what i've been working on. i'll wait till then! -brian -- IHTFP: I firmly believe that people dumber than me exist solely for my amusement. IHTFP: Okay, maybe not solely for my amusement. Some of them make good cake.

Oct. 30, 2004

[Dillo-dev]unsubscribe methods

by Patrick Shanahan

* Haines Brown <brownh(a)hartford-hwp.com> [10-29-04 19:40]: > I've tried to get myself unsubscribed to this list (to which someone > kindly subscribed me without my knowledge or permission), by emailing > the admistrator, but it seems my letter ended up on hold > somewhere. Would somone kindly suggest an alternative method for me to > unsubscribe? There's no facility on the web page for doing so. there is a mailto address in every header from dillo-dev and webpage provision in the trailer mailto:dillo-dev-request@lists.auriga.wearlab.de?subject=unsubscribe http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev directions for unsubing appear in the bottom section of the web page. ps: it is also common curtesy to give a subject indicative of the message content and to *not* hijack threads. Please have a good day and remember: read the instructions provided. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

Oct. 30, 2004

Re: [Dillo-dev]Memory leak bug (was dillo-0.8.3)

by brownh＠hartford-hwp.com

I've tried to get myself unsubscribed to this list (to which someone kindly subscribed me without my knowledge or permission), by emailing the admistrator, but it seems my letter ended up on hold somewhere. Would somone kindly suggest an alternative method for me to unsubscribe? There's no facility on the web page for doing so. Haines Brown

Oct. 29, 2004

Re: [Dillo-dev]meta refresh patch for 0.8.2

by Jorge Arellano Cid

Hi Brian, Sorry for the delayed answer, I had a lot of work with the release and now I'm trying to catch up. On Thu, Oct 28, 2004 at 12:17:29PM -0400, Brian Hechinger wrote: > On Thu, Oct 28, 2004 at 04:20:29PM +0200, Diego S?enz wrote: > > What is the difference between CACHE_ACCEPT and CACHE_ACCEPT_SESSION? > > nothing, i just wanted to keep the code as identical to the original cookie > version for now until it is decided what is going to be done with that hunk > of code. Cookies will most probably end being a dpi server (to solve the problem of enabling cookies in multiple Dillo instances). This was planned long ago and hasn't been realized because of lack of manpower (aka priorities :-). The configuration data problem (cacherc, cookiesrc, dillorc, <dpi-name>rc) is also a general issue that we're considering with Sebastian. Maybe it will all end in a generic preferences dpi; this needs some further thought. Soon a prioritized task list will be available in dillo-dev (I just sent back a good draft to Seb.). This account for what we, the core developers, will be doing the next months. The good news is that tasks that get lower priorities can be advanced by the interested volunteers. Please stay tuned, we're trying to cope with all the work we have, by organizing the work. The cache issues intersect with SSL (needs cache control), preferences handling, cookies dpi server, and the universal CCC branch idea). When the commented task list is posted, you'll get the idea. -- Cheers Jorge.-

Oct. 29, 2004

[Dillo-dev]Proper XHTML (was Re: dillo patch: anchor names)

by Kelson Vibber

Jorge Arellano Cid wrote: > BTW, it's hard to find a site that serves XHTML as > "application/xhtml+xml", that's not intended for testing. I think within the web design/web standards blogging community, you're more likely to find them. There was a "hall of fame"-type list someone did a while back, though I can't remember what it was called or where it was. Wordpress generates valid XHTML by default and sends it as text/html -- but some of the more standards-zealous and/or technically-inclined WP users have modified their sites to send the proper mime type when appropriate. (I haven't since I still don't quite trust user-supplied text not to break the XHTML -- but several sections of my site do.) Also, XHTML sites are going to be hard to find with a browser that doesn't support it, because most sites that *do* use the proper mime type use content negotiation to decide which mime type to send. This is the only way to keep the site visible to HTML-only browsers like that IE thing some people still use ;-). So unless your UA's HTTP Accept: header includes application/xhtml+xml, it won't see many sites using that mime type. > Maybe a partial validation can serve the standards compliance > objective. I mean, for instance: proper nesting, lowercase tags, > tag names in the XHTML namespace. Not much more than that. I don't recall exactly what the spec states, but from experience with Gecko browsers the main issue with broken XHTML appears to be with pages that aren't *well-formed*. So tossing in an unfamiliar attribute may break validation, but it's still well-formed XML (all tags nested and closed properly, including <img/>, <br/>, <meta/>, etc.) so the page will still display. The main errors I've noticed Mozilla complaining about are misnesting, missing closing tags, and undefined character entities. On a related note: is there a reason Dillo doesn't send an Accept: header? I'd think that something basic like "text/html, image/png, image/jpeg, image/gif, text/plain;q=0.9" with an optional ", */*;q=0.1" at the end would be about right. -- Kelson Vibber www.hyperborea.org

Oct. 29, 2004

Re: [Dillo-dev]Memory leak bug (was dillo-0.8.3)

by Roberto A. Foglietta

Jorge Arellano Cid wrote: > On Wed, Oct 27, 2004 at 07:58:36PM +0100, robert w hall wrote: > >>In article <417FCFE6.8040306(a)sad.it>, Roberto A. Foglietta >><roberto.foglietta(a)sad.it> writes >> >>>[...] >>>Sorry to inform you but v0.8.3 (far from, at least v0.8.2) has a >>>memory leak bug. >>> >>>Clicking on reload button used memory increase around 4kb for each >>>click. Stop clicking make used memory increasing stop too. So increase >>>memory size of dillo depends on reloads but not following links. >> >> >>Hmm - could this be distro/kernel dependent? > > > I don't think so. > > On the same machine, my testing shows no leak with 'http', but > leaks with 'file' and 'hello'. It looks like a leak in the dpi > branch. I'm working hard on it but it'very difficult... ...IMHO could be a_Web_free(web); in a_Capi_url_uses_dpi because moving out of that function the free (who make malloc, make free - policy) I see a lot of strange behaviure e segmentation fault in about:splash. The reason is because not all pointer freed are immediately set to NULL value. Cheers, -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

Oct. 29, 2004

Re: [Dillo-dev]Memory leak bug (was dillo-0.8.3)

by Jorge Arellano Cid

On Wed, Oct 27, 2004 at 07:58:36PM +0100, robert w hall wrote: > In article <417FCFE6.8040306(a)sad.it>, Roberto A. Foglietta > <roberto.foglietta(a)sad.it> writes > > [...] > > Sorry to inform you but v0.8.3 (far from, at least v0.8.2) has a > >memory leak bug. > > > > Clicking on reload button used memory increase around 4kb for each > >click. Stop clicking make used memory increasing stop too. So increase > >memory size of dillo depends on reloads but not following links. > > > Hmm - could this be distro/kernel dependent? I don't think so. On the same machine, my testing shows no leak with 'http', but leaks with 'file' and 'hello'. It looks like a leak in the dpi branch. Does anyone know whether g_mem_profile can help to track this down? -- Cheers Jorge.-

Oct. 29, 2004

Re: [Dillo-dev]news about memory leak

by Roberto A. Foglietta

Riccardo Mottola wrote: > Hey, > > I am on a NetBSD/ppc system. DIllo 0.8.3 and can reproduce the leak. I > noted however that: > > - clicking the reload button in thight succession gets an increment of > about 4K every time > - the leak is consitent, you can make the amount of leaked memory > skyrocket to megabytes. > - clicking slowly, waitning 10 seconds each time does NOT make dillo > leak > > I suspect the leak happens if you click reload before dillo has > "finished" the page and the "stop button" is disabled. > What is the best way to check if a page has been load completely? I mean checking BrowserWidows or DilloUrl structures... Cheers, -- Roberto A. Foglietta Analista Programmatore GNU/Linux SAD Trasporto Locale S.p.a. Corso Italia 13/N 39100 BOLZANO (I) Tel. +39/0471-450.261 Fax +39/0471-450.253

Oct. 29, 2004

Re: [Dillo-dev]Protocol Handlers

by Jorge Arellano Cid

Hi, On Thu, Oct 28, 2004 at 04:07:06AM -0230, Lee Bigelow wrote: > Hello there, I was playing with the dpi's and > made one for ed2k:// links (based on the Hello > World example). It was just a quicky, and not > generally useful, but I was wondering if anyone > was working on a general protocol handler. This is a good idea and some prototypes have been tried in the past. It'd be very good to implement this as a dpi. Please read: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-October/002278.html and ask Matthias (and Lars IIRC). If you're interested I can answer/develop/help with the dpi part. > > Along these lines: > > - Dillo doesn't recognize the protocol so sends it > to say external.dpi > > - external.dpi reads an external.conf file that > has a list of protocols and respective > external handlers. > > - If it finds a matching protocol it sends > the url(%s), or just the url data (%r), to > the handler. > > - If there's no matching > protocol it could show an edit page (like > bookmarks modify) for the external.conf. > > This could be used for mailto:, nntp:, telnet:, > etc.. > > Anyhow, I starting playing with it, and I > thought I should check to see if anyone else was > also working on it before I went any further. > > Also, if there's any advice on the approach, or > code I should look at, that would be cool. I am > no expert C programer, I'm just reading the docs > and modifying the code the other fellows already > did. (I hope that's ok) Yes, that's OK, and good for the project. :-) -- Cheers Jorge.-

Oct. 28, 2004