March 2005 - Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]GTK 1.2 ..?

by Kelson Vibber

R. Tyler Ballance wrote: > Is there any reason Dillo is still building against the GTK+ 1.2 > libraries as opposed to 2.0 ? People have done tests, and Dillo becomes much slower and much larger under GTK2. The current plan (unless it's been changed off-list) is to move to FLTK instead, which should pick up things like Unicode support and a more current code base. -- Kelson Vibber www.hyperborea.org

March 30, 2005

[Dillo-dev]GTK 1.2 ..?

by R. Tyler Ballance

Is there any reason Dillo is still building against the GTK+ 1.2 libraries as opposed to 2.0 ? I'm not sure what it would break to build against the 2.0 libs, but I would really like to start building against them so I can add the clipboard code that i've had my eye on ;) I don't think the size would grow _that_ much, and I think the benefits would be large from using 2.0. Right now, the only difference I can see would be in the autoconf files, GTK+ 2.0 uses pkg-config to supply the correct cflags and ldflags, while GTK+ 1.2 uses gtk-config. Ideas, suggestions? -R. Tyler Ballance p.s. I'm working through bug #668 which I added last night on my NetBSD laptop right now, woo

March 30, 2005

Re: [Dillo-dev]Refresh patch for 0.8.4

by Brian Hechinger

On Mon, Feb 21, 2005 at 09:19:34AM +0100, Roberto A. Foglietta wrote: > > For this reason I decide to have -r option instead put an option in a > config file because packager could deliver its own default config with > that option activated by default. It could be much more difficult for > the packager to force me using that option by command line, instead. > ;-) this is why my plan was to have an rc file similar to the cookierc file so you can have fine grained control over which sites are allowed to meta-refresh and which ones aren't. IMNSHO, the best solution. ;) -brian -- "Now you know why I got the everliving hell OUT of Windows administration. Knowing it doesn't make it any easier. It's just broken-as-designed."

March 16, 2005

Re: [Dillo-dev]Patch: config option for page increment

by Jorge Arellano Cid

On Mon, Mar 14, 2005 at 02:41:31PM +0100, Alexander Becher wrote: > Hi everyone, Hi! > I have made a small change to dillo-0.8.4, so I can put a line like > > scroll_factor=0.5 > > in my dillorc and get the old behaviour for scrolling a page. > > It would be great if this could be included in the dillo distribution, > so I don't have to patch my source every time I build a new version. > > I know that the current effort is the port to FLTK. If this makes this > patch useless for new versions, I'll try to adapt it once the port to > FLTK is done. Don't worry, most probably there will not be a 0.8.5. Just be sure that once the protoype is available (with scrolling ;) you submit a patch for it. -- Cheers Jorge.-

March 14, 2005

[Dillo-dev]Patch: config option for page increment

by Alexander Becher

Hi everyone, I have made a small change to dillo-0.8.4, so I can put a line like scroll_factor=0.5 in my dillorc and get the old behaviour for scrolling a page. It would be great if this could be included in the dillo distribution, so I don't have to patch my source every time I build a new version. I know that the current effort is the port to FLTK. If this makes this patch useless for new versions, I'll try to adapt it once the port to FLTK is done. Regards Alexander -- PGP key available

March 14, 2005

Re: [Dillo-dev]configure cache size

by Jorge Arellano Cid

On Thu, Mar 10, 2005 at 09:09:39AM +0100, G. Milde wrote: > > Dear developers, > > thanks for dillo. :-) > [...] > > PS: This is a re-post. I sent this mail once, before subscribing and it > seems like it did not get through the moderation process. dillo-dev receives too much SPAM, so the moderation process became: if (!subscribed) reject; -- Cheers Jorge.-

March 14, 2005

Re: [Dillo-dev]configure cache size

by Jorge Arellano Cid

On Sun, Mar 13, 2005 at 02:56:39PM -0500, Livio Soares wrote: > Hi Günter, > > G. Milde writes: > > > > Dear developers, > > [...] > > > What could I do to turn off (or limit) the internal cache? > > No, not in "vanilla" Dillo. > > > Was the cache_size option in the debian package an unofficial patch? I > > would really like to see this patch in the mainstream, as I am short on > > RAM here... > > Yes, this is an unofficial patch. I wrote that patch in 2002-2003. Since then, > my life turned upside down a few times. Right now, I'm just focusing on > avoiding heart attacks from overworking ;-) > > Regardless, there are two relevant posts about the subject: > > The message explaining the internals of the patch: > http://sourceforge.net/mailarchive/message.php?msg_id=1642897 > > The lastest version of the patch: > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-January/000073.html > > > I think it last applied cleanly to Dillo 0.7.0 (from early 2003). Of course, I > expect it to not apply cleanly at all today. However, the good part is that the > entire patch was only less than 150 lines of code; it probably would take > someone just a few days to reintegrate it. > > If anyone wants to grab this patch and update it, before you do, please make > sure with Jorge if he is interested. Although _I_ feel that this patch is > extremely important to Dillo, I have no idea why Jorge didn't integrate it in > the first place, at the time (although, I have a hunch he was too busy, and this > was not so high in his priority list...). Hi Livio! Good to see you can respond even at peak work levels! :-) You're right on both things, it _is_ very important, and I did not have the time... Unfortunately this is not rare because I have much more work than I can handle so only the top priorities get a time slice. For instance, now, the official CVS is frozen because Sebastian and I are working with exclusive dedication to the port to FLTK. As soon as we get an interesting prototype, we'll upload the source tree so everyone can play and help with it. Of course, if there's a person with high knowledge on Dillo internals and enough time to review/integrate/QA the patches, I'm more than willing to hear from him! BTW, Livio was my perfect candidate, but he has no time now... -- Cheers Jorge.-

March 14, 2005

Re: [Dillo-dev]configure cache size

by Livio Soares

Hi Günter, G. Milde writes: > > Dear developers, [...] > What could I do to turn off (or limit) the internal cache? No, not in "vanilla" Dillo. > Was the cache_size option in the debian package an unofficial patch? I > would really like to see this patch in the mainstream, as I am short on > RAM here... Yes, this is an unofficial patch. I wrote that patch in 2002-2003. Since then, my life turned upside down a few times. Right now, I'm just focusing on avoiding heart attacks from overworking ;-) Regardless, there are two relevant posts about the subject: The message explaining the internals of the patch: http://sourceforge.net/mailarchive/message.php?msg_id=1642897 The lastest version of the patch: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-January/000073.html I think it last applied cleanly to Dillo 0.7.0 (from early 2003). Of course, I expect it to not apply cleanly at all today. However, the good part is that the entire patch was only less than 150 lines of code; it probably would take someone just a few days to reintegrate it. If anyone wants to grab this patch and update it, before you do, please make sure with Jorge if he is interested. Although _I_ feel that this patch is extremely important to Dillo, I have no idea why Jorge didn't integrate it in the first place, at the time (although, I have a hunch he was too busy, and this was not so high in his priority list...). If you have any questions, please go ahead and ask. Oh, and just for the record, there used to be a "featureful" version of the patch, which had a couple of interesting facilities (viewing the cache contents, and flushing everything from the cache). They were ripped from the newest versions of the patch, but are described here: http://sourceforge.net/mailarchive/message.php?msg_id=1642897 And links to all patches are within the posts I linked here. Good luck, Livio

March 13, 2005

Re: [Dillo-dev]dillo bug : not using the whole space

by Sebastian Geerken

On Tue, Mar 08, Denis BUCHER wrote: > I found another bug or problem in dillo : It doesn't use all the space > provided ! > > For example, let's take a 320x240 screen/window (in full screen mode). > If your content takes more than 305-310 pixels wide, the scrollbars are > appearing, while they only should appear if your content is larger than > "window size less borders", like 316... > > I hope my question is clear and thank anyone would could reply/help me :-) I hope that I mean the same problem: I type "dillo -geometry 615x665 somePicture.png", where "somePicture.png" is 600x600 pixels large. "-geometry 615x665" is just the size, where the viewport should provide space for this image. Initially, the scrollbars are visible, but when I enlarge the window and restore its size again, the scrollbars are not visible anymore, interestingly. There seems to be some bug in Dw_gtk_viewport_calc_size (in dw_gtk_viewport.c), actually, the way as it is supposed to work (initially assume that the scrollbars are not visible) suggests to work it the way you expect. Sebastian

March 12, 2005

Re: [Dillo-dev]javascript ...

by Sebastian Geerken

On Wed, Mar 09, Lars Segerlund wrote: > I have a theoretical question, as follows. > > What would be needed for Dillo to support javascript ? Of course > it would need a javascript interpreter, but there are also issues > about variables and how to handle stuff like mouseover and such in > the rest of the code. The script interpreter could be a dpi; to handle variables, the dpi should provide the possibility to handle different states (something like a key, which dillo creates for each page, and which helps the dpi to distinguish different states, which have independant sets of variables etc.). Then there are events ('on...' attributes of the HTML tags). There is a document tree already in the CSS prototype (see <http://www.dillo.org/CSS.html>), which provides some signals based on document *elements* (not on dillo widgets anymore), this could be extended. Somehow, these signals need to be connected to the script engine dpi. Also, there needs to be another interface, so that the dpi can access properties of dillo (i.e. HTML DOM). For the XML subset (XML DOM), the document tree in the CSS prototype must be extended a bit. (The planned functionality is not that much less than the functionality needed for a full XML DOM implementation). The rest of HTML DOM is related to the DilloHtmlLB structure. > Is there any possibility that the dpi interface would suffice for > a task like this ? ( what I mean here is if there is a possibility > to somhow use it for this functionality, perhaps 'filtering' the > pages through it or something ? ). > > Basicly I'm curious, and I would like to have a look at if it's > doable. It should be doable, but there are some changes in dillo needed. Sebastian

March 12, 2005