- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] Dillo on Windows fork
by Melvin Hadasht Sept. 4, 2003

Sept. 4, 2003

[Please, let's keep this discussion on the ML] Hi, > > If someone wants to port Dillo to Windows, he > > can look at how Sylpheed-Claws I/O infrastructure was ported to Windows. > > Sylpheed-Claws does not use pthreads, but it forks... > > Windows doesn't fork. That can be emulated with spawn. Threads is a better > approach. I don't know how he did that, but I remember those two parts (IO and forking) were the first things that needed to be ported to Windows. My message wasn't aimed at discussing technical points (I never programmed in Windows), but rather to point to some light-weight gtk 1.2 project that was already successfully ported to Windows, so less experienced developers could take a look on it. > > I think, if someone does not already have the experience of > > porting to Windows.... > > I ported CinePaint to Windows, the largest GTK project ever ported aside > from GIMP. Then disregard my email, it will not help you :). I thought someone was in need of technical help for porting to Windows, so I posted some hints in the case where the poster was not so experienced. > >...looking at Claws versions can be very helpful, as our port > > is done by a very knowledgeable guy. > > Cool, who was that? Just google for Sylpheed-Claws & win32 :) -- Melvin Hadasht

1 0

RE: [Dillo-dev] Dillo on Windows fork
by Eric Gaudet Sept. 3, 2003

Sept. 3, 2003

> Kelson, > > > If Jorge does not want to work on a Windows port, that's up > > to him.... > > That does not necessarily mean the project has to be forked.... > ... > It seems clear that I must take Dillo for Windows elsewhere, > that opinions are too firmly set for Windows users to feel > welcome here soon. It isn't a problem to put my version on > SourceForge. Does anyone here want to get involved now or > shall I go it alone? > That's the beauty fo the GPL: even if the developers of Dillo don't want to help with a feature, a port, you can still do it. And if you end-up adding interesting stuff, Dillo can even get it back! ... > Should I choose a new name for the Dillo fork on SourceForge? > It's not required, AFAIK. The only requirement is to release the sources under the GPL with any release you do. Regarding the need for a windows port, I don't quite see who would need such a thing (besides you, obviously). Windows has phoenix, which is lightweight enough when the OS itself need a big machine only to boot. As for running old versions of windows on a small machine, it really is ludicrous. Running an OS that's unsupported, crash-prone and hopelessly outdated like W9x sounds like a bad idea. This kind of machine is a perfect target for a small linux. Good luck anyway. Eric

1 0

Re: [Dillo-dev] Dillo on Windows fork
by Robin Rowe Sept. 3, 2003

Sept. 3, 2003

Robert, > Well, for me, one of the annoying things about M$ is it's policy of > aggressive obsolescence. Let's not debate the pros and cons of Microsoft. It isn't that interesting and anyone with an opinion is unlikely to change it. In my world, that is, motion picture animation and special effects, the O.S. situation is very different from elsewhere. If you read my articles in Linux Journal then you are aware that in motion picture production Linux dominates as the most popular O.S. on servers and desktops. Windows isn't even a close second. The largest corporate installations of Linux in the world are DreamWorks, ILM, and Disney. To support all operating systems -- even minor ones like Windows -- is a mark of professionalism where I come from. Cheers, Robin --------------------------------------------------------------------------- Robin.Rowe(a)MovieEditor.com Hollywood, California www.CinePaint.org Free motion picture and still image editing software

1 0

Dillo configure cannot find zlib, jpeglib not libpng
by Scorpio Rising Sept. 3, 2003

Sept. 3, 2003

Hello, just joined. I have a configuration problem in Debian stable. The configure file cannot find/use the z, jpeg or png libs that are in /usr/include. *** cannot locate***......disabling jpeg/png/libz I have tried the command line options and even hardcoding the paths in configure.in to no avail. I have installed the dev-headers for these packages. Other programs (GIMP, ShowIMG, etc) find and use them just fine. Dillo works, but no images :-\ Thanks, -- Gregg

2 1

Problems compiling tab+frame patch on Mandrake and RH 7
by Kelson Vibber Sept. 3, 2003

Sept. 3, 2003

I've built RPMs that include version 9 of the tab+frame patch at http://www.hyperborea.org/software/dillo/modified.html (a completely separate page from the mail page with the "vanilla" RPMs). In building these, I ran into problems trying to compile with up-to-date versions of: - Red Hat 7.3 - Red Hat 7.2 - Mandrake 8.2 - Mandrake 9.1 On these systems, after un-tarring the Dillo 0.7.3 source and applying the appropriate version of the patch, make would always fail at the same point: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/include -I/usr/local/include/libpng12 -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -g -O2 -DXHTML_DTD_FRAMESET -DXHTML_DTD_TRANSITIONAL -D_REENTRANT -D_THREAD_SAFE -Wall -Waggregate-return -c `test -f 'http.c' || echo './'`http.c http.c: In function `Http_query': http.c:167: `VERSION' undeclared (first use in this function) http.c:167: (Each undeclared identifier is reported only once http.c:167: for each function it appears in.) make[3]: *** [http.o] Error 1 make[3]: Leaving directory `/home/kelson/build/dillo-0.7.3/src/IO' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/kelson/build/dillo-0.7.3/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/kelson/build/dillo-0.7.3' make: *** [all] Error 2 The unpatched versions had no problems on any of the above systems. When I checked the patch to see what was changed in http.c, and saw how little there was, I started looking at library versions. At the time I had not tried Red Hat 7.2, so I started up my UML copy. On my first test (just compiling the patched source), it worked. I then checked for and installed updates before trying to build the RPM, and it failed just as the others had. To make a long story short, on Red hat 7.2 I narrowed the problem down to glibc. It worked with glibc 2.2.4-19.3, but not with 2.2.4-32. Unfortunately I can't narrow it down to a version in general. Red Hat 7.3 is on glibc-2.2.5-43, Mandrake 8.2 is on glibc-2.2.4-26.2mdk, and Mandrake 9.1 is on glibc-2.3.1-10mdk. Has anyone else encountered similar problems, and/or come up with a workaround? -- Kelson Vibber www.hyperborea.org

3 3

CPU hog with large selections
by Jorge Arellano Cid Sept. 2, 2003

Sept. 2, 2003

Hi there, Yesterday I came accross this bug while reading: http://freshmeat.net/articles/view/889/ (272KB) If you go to a comment in the middle of the page, start selecting text with the mouse, and move it to the leftmost border (so it selects all the text up to the start), the CPU will hog and dillo will become unresponsive as it was in a dead loop. For instance, from the bottom line it takes 10 minutes to recover on a pentium II 233Mhz. I almost sure this can be improved. Please someone give a hand to fixing it. Cheers Jorge.-

2 2

Dillo used in Puppy Linux
by Barry Kauler Sept. 2, 2003

Sept. 2, 2003

Hi, Introducing myself, just recently subscribed to this list. I'm developing a super tiny Linux distro called Puppy, that runs totally in a 48M or 64M ramdisk, yet has a full suite of GUI apps. The greatest advantage of having everything always in RAM is the fast startup and response. The 48M version 0.6 is on the web, hosted by ibiblio.org, and uses Hacked Links and Dillo. I'm currently using Dillo as the internal HTML viewer. Note, Puppy has a large amount of docs, in HTML. Also using Sylpheed, not Claws. For the "big" Puppy, running in 64M, I've experimented with Mozilla v0.9.8 and Konqueror-embedded. I've retained Dillo as the internal viewer. Note that the small Puppy uses only apps written in plain C, and only has the Athena (neXtaw) and GTK v1.2 libraries -- which is why I want to encourage you Dillo developers to stick with compatibility with the v1.2 library!!! ...and, I know it's dreaming, but if Dillo can get CSS, SSL, and a few other things, it could be the only browser I need. (Flash, SVG, ....) ... small Puppy runs ok on a PC with 128M RAM, but I dream of getting it going on a 64M system. Puppy site: http://www.goosee.com/puppy Regards, Barry Kauler

2 1

table cellspacing and borders
by Ralph Slooten Sept. 2, 2003

Sept. 2, 2003

In my attempts to make a nice design website from pure and propper html, I have discovered that Dillo differs from any other browser when it comes to rendering tables with set widths. Could anyone clarify for me why dillo expands the initially set width of a table when the cellspacing and/or border is increased? What I mean is like this: <table cellpadding="6" cellspacing="10" border="5" width="700" bgcolor="#E3E3E3"> <tr> <td>test</td> <td> test 2</td> </tr> </table> This produces a table which is wider than 700px. If cellspacing="0" and border="0", dillo renders the table fine to it's set width of 700. Is this a bug, or some w3.org specification other browsers like Mozilla / Opera / IE ignore? Using 0.7.3 here if it's any use ;-) Greetings Ralph -- http://axljab.homelinux.org:8080/ "...the software said Win95 or better, so I installed Linux"

1 0

Re: [Dillo-dev] tight loop on IO error
by Jorge Arellano Cid Sept. 1, 2003

Sept. 1, 2003

On Mon, 1 Sep 2003, Andreas Schweitzer wrote: > > All I did was fix the problem for me -- it's possible that there's > > still some object cleanup elsewhere that really needs doing ... > > It almost looks like that there needs some more digging. > > I did some tests comparing Linux and FreeBSD. > 1) The patch needs to be slightly modified for the Linux version, > otherwise dillo won't even start correctly :-) > 2a) When the timeout occurs while contacting unresponsive sites: > The Linux version actually stops eventually and puts > "ERROR: unable to connect to remote host" > in the status bar. However, none of the error debug > messgaes actually occur ... > 2b) Same as 2a but under FreeBSD: dillo still keeps > the "Contacting host" in the status bar, and the > stop-icon is still unfaded. And the error message > gets dumped as indicated in the patch. > > But I'm afraid the logic how all these routines are > accessed is a bit too compliacted for me right now :-) Hi! I just made a quick patch and tested http://primates.ximian.com/~miguel/all.html with a dialup on linux (no CPU hog, no problems, 80 of 83 images got). The idea was to make it analogous to IO_read(). Please test it under BSDs (it's on CVS). Cheers Jorge.-

1 0

tight loop on IO error
by Phil Pennock Sept. 1, 2003

Sept. 1, 2003

When viewing the page [warning, many images]: <URL:http://primates.ximian.com/~miguel/all.html> dillo runs into a tight loop when there's a broken pipe error on retrieving one of the last couple of images. I've tracked down the cause; I'm running the 0.7.3 code, with Frank's patch, but have confirmed the presence of the code in HEAD via the WebCVS interface (wonderful thing). In IO/IO.c:IO_write(), if the write() returns (-1) then unless the error is one of EINTR or EGAIN, the case isn't handled and the "while (1) {}" loop runs wild. With a quick change (including new debug statement) I now see: IO_callback: [GIOcond 4] IO_write IO_write: Broken pipe [errno 32] [St -1] IO_write: aborting: Broken pipe [errno 32] The patch includes some extra cosmetic DEBUG changes which can be safely discarded (and the DEBUG_LEVEL change probably should be ...) -----------------------------< cut here >------------------------------- --- /home/pdp/tmp/zshmiVuTI Mon Sep 1 13:43:24 2003 +++ IO.c Mon Sep 1 13:42:58 2003 @@ -30,7 +30,7 @@ #include "../klist.h" #include "IO.h" -#define DEBUG_LEVEL 5 +#define DEBUG_LEVEL 1 #include "../debug.h" @@ -399,8 +399,12 @@ St = read(io->FD, io->Buf, io->BufSize); io->Status = St; - DEBUG_MSG(3, " IO_read: %s [errno %d] [St %d]\n", - g_strerror(errno), errno, St); + if (errno) { + DEBUG_MSG(3, " IO_read: %s [errno %d] [St %d]\n", + g_strerror(errno), errno, St); + } else { + DEBUG_MSG(3, " IO_read: [St %d] success\n", St); + } if ( St < 0 ) { /* Error */ @@ -446,18 +450,27 @@ St = write(io->FD, io->Buf, io->BufSize); io->Status = St; - DEBUG_MSG(3, " IO_write: %s [errno %d] [St %d]\n", - g_strerror(errno), errno, St); + if (errno) { + DEBUG_MSG(3, " IO_write: %s [errno %d] [St %d]\n", + g_strerror(errno), errno, St); + } else { + DEBUG_MSG(3, " IO_write: success [St %d]\n", St); + } if ( St < 0 ) { /* Error */ io->Status = -errno; - if (errno == EINTR) { + switch (errno) { + case EINTR: continue; - } else if (errno == EAGAIN) { + case EAGAIN: DEBUG_MSG(4, " IO_write: EAGAIN\n"); ret = TRUE; break; + default: + DEBUG_MSG(5, " IO_write: aborting: %s [errno %d]\n", + g_strerror(errno), errno); + return FALSE; } } else if ( St < io->BufSize ){ /* Not all data written */

3 4