- Dillo-dev - lists.mailman3.com

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

Re: [Dillo-dev] Rendering problem
by Jorge Arellano Cid Sept. 1, 2003

Sept. 1, 2003

On Thu, 28 Aug 2003, Ralph Slooten wrote: > On Thu, 28 Aug 2003 12:57:36 -0400 (EDT) > "Andrew A. Gill" <superluser(a)frontiernet.net> wrote: > > > I've been having a problem with dillo rendering some portions of text. > > For instance, the Google sponsored links always take up vertical space > > before the results. > > > > Normally, this isn't something that I really care about, but now it's > > causing slashdot to be rendered as black-on-black text, thus depriving me > > of my ability to read about the new MD5 sums that the RIAA is using. > > Yes, I'm getting this too since today. It's probably a small html error > somewhere, but it's totally skrewed up dillo's rendering to the fullest here. Unfortunately slashdot is sending awful HTML-like content. The black text can be explained because they explicitly set the background, textcolor and visited links to black! (<BODY ...>). Probably it changes with CSS. > > Since about 2 weeks ago I'm also getting a black border on the right (with > exception to today of course where most of the page is black) which just takes > up valuable space ;-) > > Tried the light mode too like Frank suggests, but I prefer the default layout > myself. Anyway, it's not a dillo problem I think, as I get a total of 530 errors > just on the index page itself!!!!! Check now too if ya want: > http://validator.w3.org/check?uri=http%3A%2F%2Fwww.slashdot.org%2F Try with "force_my_colors=YES". Now, it still shows several rendering problems. If those are because of lack of implementation of "floats" we should fix it someday. If it's because of bad HTML, you know our policy. OTOH, I believe slashdot webmasters will not pose major problems to fix their HTML if they're emailed with the facts... Please investigate those and report to them. Cheers Jorge.-

4 5

path for support chinese
by super_hoo Sept. 1, 2003

Sept. 1, 2003

I knowed that it had a patch for dillo0.7.2 to supportting Chinese. Where could I find this patch ? thanks a lot. ______________________________________ =================================================================== µ±µ±ÍøÈ«³¡ÒôÏñ5ÕÛ·â¶¥£¬ÓÅ»ÝŒŽœ«œáÊø£¡ (http://ad4.sina.com.cn/sina/dangdang0825.html)

1 0

Problems with tab patch
by Nigel Wilkinson Aug. 29, 2003

Aug. 29, 2003

Evenin' all I'm trying to patch the CVS with the tab patch but I haven't used patch much. The problem I'm haveing is that I don't know which directory to run the path from, it keeps complaining that it can't find the file to patch Cheers Nigel

2 4

[PATCH]: commands & auto-reload (was Re: dillo / time-controlled reloads)
by Melvin Hadasht Aug. 29, 2003

Aug. 29, 2003

[Henning, you may be interested: the patch implements a --reload option] Hi, To implement the server and remote commands feature in Dillo, I'm going to go step by step. First, I'll implement commands to control Dillo at startup time, then I'll implement the server mode (where a Dillo instance can send the aforementioned commands to another Dillo instance). This is because I may try two differents approaches for the server mode part and because the commands are just a generalization of the command line options and can be implemented separately. Here is my first step: implement commands (like -c "open(URL)"). Patch is attached and is against CVS version. This is a generalization of the command line interface, and in fact, most of the old command line options are translated to a Dillo -c command. The advantage of such approach is that the commands can take optional parameters, like in: dillo -c "open(URL newwindow reload=10 fullwindow=yes)" which is approximately equivalent to: dillo -f -r 10 URL The commands are passed to Dillo as arguments to the -c, --command command line option: dillo -c "open(http://www.google.com)" 1. Command Syntax The argument to the -c command line option is of the form: CMD([STRING][ PARAM=VALUE]...) CMD: command name STRING: first and generic argument: in general a URL or yes|no PARAM: name of optional parameter VALUE: value of optional parameter. Currently, only booleans (yes|no) and integer values are supported. Boolean value can be omitted, in which case the value is considered to be "yes". Integer value cannot be omitted. Parameters are separated with a single space (no commas, to simplify the parser) Commands can be divided into two groups: actions commands, and options commands 2. Action Commands: They do some action: currently implemented commands: open(URL [ fullwindow[=yes|no]] [ reload=SECONDS] [ spamsafe[=yes|no]] [ xid=XID]) parameters speak for themselves. The "reload" parameter is a new feature: it allows to reload the URL each SECONDS seconds. The reload is halted when the page is not viewed and restarted if the user comes back to it. exit() exit the instance. This will be useful when passed to another Dillo instance running as a server. Other commands can be added. The framework is quite flexible and extensible. 3. Options Commands These commands set some options that will affect the following commands. For example, the parameters used in the open() command act only on that particular URL. But it can be useful to be able to set some defaults values. The currently implemented commands that influence these defaults are: fullwindow([yes|no]) reload(SECONDS) spamsafe([yes|no]) xid(XID) all open() commands that come after these options commands will have these default values, unless explicitly overridden. 4. Examples: dillo -c "open(http://www.google.com)" -c "open(file:///home/mhadasht/test.html newwindow spamsafe)" will open two windows: the first with google, and the second with the local file opened in spamsafe mode. dillo -c "reload(10)" -c "open(http://www.freshmeat.net)" -c "open(http://news.google.com newwindow)" will open 2 windows and will reload both URLs each 10s. This is equivalent to: dillo --reload 10 http://www.freshmeat.net http://news.google.com 5. Implementation details: 5.1. Command Line Parsing Command line options other than the help/version options are translated into a -c command and stored in a list. The list of commands is then executed (or, when the server mode will is implemented, sent to another Dillo instance) 5.2. Reload Function a URL can be set to auto-reload itself if it is currently viewed. For that, a new member (reload_interval [milliseconds]) to DilloUrl is added and set with a_Url_set_reload(). Each BrowserWindow can trigger a timer function if the viewed URL (Nav_open_url()) has a non-zero reload_interval. (As soon as another URL is viewed, or when the BrowserWindow is destroyed, the eventually pending timeout function is removed.) The timer is of the one-shot type: when it is triggered, it requests its BrowserWindow to reload the URL, then it stops itself. There is currently no UI to start/stop an auto-reload of a URL, but it is just a matter of using a_Url_set_reload() to a non-zero or a zero reload interval. 6. Remark The -c command and the normal command line options can be seen as two ways of doing the same thing: passing commands to Dillo. But the -c command is more generic and flexible and has a more powerful syntax. 7. Future Plans I plan to implement the server mode. After reading the dpi doc and source, I found that it cannot be used to make Dillo act as a plugin unless we accept to have only one Dillo server. This is because the socket names are tightly linked to the service name. Each service has only one socket. Whereas Dillo servers must have a distinct socket. If the we add another argument to the "start_plugin" cmd: <dpi cmd="start_plugin" msg="dillo" param="SERVER_NAME"> and if we modify the socket naming scheme, then it could be possible. I have to think about that again. But I may still use the communication infrastructure of the dpi. If I find this overkill, I'll revert to the straightforward approach I used before, that is, I won't use the dpi framework. OK, it's late, I hope I managed to be somewhat clear... Cheers. -- Melvin Hadasht

2 5

Rendering
by Jorge Arellano Cid Aug. 29, 2003

Aug. 29, 2003

Hi Sebastian! Hope you're not under a pile of workload... Please review this site: http://cocoon.apache.org/index2.html When loaded slowly (dialup speed) it renders the leftmost column too wide (almost a screen), but Back&Forward fixes it. I you can also give a look at the slashdot problem it'd be great. I'm much more interested in the first though. Regards Jorge.-

1 0