- Dillo-dev - lists.mailman3.com

dillo and no-cache
by digitek March 23, 2006

March 23, 2006

Hello All. Nice browser! I noticed 0.8.5 loads pages from cache regardless of the 'content=no-cache' meta tag. Near as I can tell from the mailing list, this is by design. I also found the no-cache patch for 0.8.2 and applied to 0.8.5 (by hand). Is this the best way right now to get cache control working? Thanks -- digitek(a)charter.net key id: 0xF6FA6D1E huh?: http://google.com/search?q=gnupg+secure+email

3 4

[article] trimming down autoconf's configure scripts by using pkg-config
by Enrico 'nekrad' Weigelt March 23, 2006

March 23, 2006

Hi folks, here's a little article I wrote about an approach for encapsulating platform dependent stdc-lib fixes (ie. some platforms have broken string handling, etc) behind pkg-config. It is mostly directed on autoconf (It is the one I have most of my daily trouble with), but of course the approach works with other buildsystems, even plain make, too. The permanent URL of the article: * http://www.metux.de/articles/coding/trimming-down-autoconf-with-pkg-config I'm also currently working on concrete wrapper packages: * http://wiki.metux.de/public/OSS_QM_Taskforce/projects/stdc-pkgconfig Comments and suggestions please to the Maillist: oss-qm-discuss(a)metux.de Thanks. -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: info(a)metux.de cellphone: +49 174 7066481 ---------------------------------------------------------------------

1 0

Progress on porting to FLTK2?
by Roberto C. Sanchez March 22, 2006

March 22, 2006

Hello, I became interested in Dillo a while back and even made some small contributions and helped fix some bugs, but I was eventually disuaded by the fact that Dillo uses GTK+. I was happy when I heard that Dillo would be ported to FLTK. Has there been any progress on this? I would like to start contributing again, but I have not seen anything other than a few mailing list posts in the archive and a mention of it on the "Current Plans" page. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto

5 6

Re: [Dillo-dev] dillo-0.8.6-rc1
by Jorge Arellano Cid March 22, 2006

March 22, 2006

Hi Francis, Thanks for the good feedback. On Wed, Mar 22, 2006 at 09:21:21AM +0000, Francis Daly wrote: > On Tue, Mar 21, 2006 at 02:13:38PM -0400, Jorge Arellano Cid wrote: > > Hi there, > > > ... test and send feedback. > > Some minor thing that you might like to tidy before release: > > * ChangeLog has a few entries with a leading hyphen. Yes, this visually separates batches of patches by the same authors. > * ChangeLog says > > * Added dpi/downloads.cc (Default FLTK2-based GUI for downloads dpi). > and > * Made the downloads plugin dillo-cookie aware. > > It's only the *old* plugin which handles cookies. (And modifying the new > one to is more than just a two line addition, because the arguments are > counted in (I think) two other places.) But overall, it's no regression > from 0.8.5, so no problem. It just might be worth clarifying the > distinction. Ooops. This is a BUG! I'll clarify the distinction in rc2. > * README says > > Here's a list of some well known problems: > > * no FRAMES rendering > * no https -- read the FAQ to enable a protoype. > > while the code now defaults to https enabled. Change README or change > dpi/https.c > > If you choose to change README and you want to keep at least two problems, > you could mention "javascript" or "http authentication". But only if > you consider their absence a problem ;-) > > Leaving https enabled will get the code tested more, but will likely cause > a warning for each https: url accessed, unless the user's distribution > happens to store trusted root certs in /etc/ssl/certs. > > You can choose whether you want https.c polished more before being exposed > to the world. Possibly a note in README or FAQ saying "dillo reads root > certs from the directories /etc/ssl/certs or $HOME/.dillo/certs; they > should be named after the hash of the certificate subject name -- see > e.g. the openssl x509 documentation, '-hash' option for more information." Yes, this needs some fixes. I'll disable the https dpi as usual (it's too rough now, and it needs a conversion from dpi filter to dpi server too). Sending the users to dig the openssl x509 documentation is too much, and the https dpi hangs when there are concurrent https requests. As for the known problems, I'll add "http authentication". :-) > (Yes, I know, if I *really* cared, there'd be patches in this mail. But > I'm not sure if you're looking at releasing in a day or a week, and > think the things should be mentioned early so you can consider whether > you want to change any of them.) I think more or less one week. Until the release candidate is tested and not having new problems. -- Cheers Jorge.- PS: Your email reply was addressed to me, not to the list. (usually a MUA choice that needs a tweak)

1 0

Refresh via external signal?
by Bill Gatliff March 21, 2006

March 21, 2006

Greetings again! If I have an instance of Dillo already running, is there a way for an external program to tell it to browse a certain URL? I'm trying to "drive" Dillo from another application as part of a mobility-impaired application... Thanks! b.g. -- Bill Gatliff bgat(a)billgatliff.com

4 5

[mike@easysw.com: Re: FLTK2-based Dillo for Debian installer]
by Jorge Arellano Cid March 21, 2006

March 21, 2006

Hi there, A follow-up of FLTK2-based Dillo for Debian installer. -- Cheers Jorge.-

2 2

Audio?
by Bill Gatliff March 21, 2006

March 21, 2006

Greetings! Can Dillo "do audio" for web pages that have it? b.g. -- Bill Gatliff bgat(a)billgatliff.com

2 2

Dillo and GTK+
by Attilio Fiandrotti March 21, 2006

March 21, 2006

Hi Recently the debian-installer, Debian's installation system, went graphical [1]: a GTK frontend was developed and to keep the instalation ISO as small as possible, so that runs even on low-mem systems, we choosed the DirectFrameBuffer [2] GTK backend (that has recently become part of GTK mainline to replace the old linux-fb). As the DFB backend allows multiple applications to render on the same VT, i was investigating about intergrating a web browser into the debian-installer so that the user is able to browse the installation manual while installing. As we need a very small and non X11-tied browser, dillo looks perfect for our purpose, but, as dillo is based on GTK 1.x, it's currently not possible running it on a GTKDFB system. I was wondering how hard would it be porting Dillo to GTK+, so that we can use it into our installer? Also, having dillo running on top of GTKDFB, would make it a very good solution for embedded applications. friendly Attilio Fiandrotti [1] http://wiki.debian.org/DebianInstaller/GUI [2] http://www.directfb.org/wiki/index.php/Projects:GTK_on_DirectFB

2 1

Re: [Dillo-dev] dillo 0.8.5 / OpenBSD 3.6 help request
by Jorge Arellano Cid March 16, 2006

March 16, 2006

Francis, > > > [...] > > > In the spirit of the suggestion at > > > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-April/000422.html > > > here's a patch which implements a configure --disable-threaded-dns option. > > > > OK. I checked the patch, and recoded it to use D_DNS_THREADED, > > D_DNS*, and the same "./configure --disable-threaded-dns". > > > > Commited and in CVS now. > > > > Please test it. > > Got it, working on it. > > Be aware, though, that I'm on Linux here too. If there's someone with > a Real Live BSD box they'll be able to do a proper test. > > The person who reported bug#703 might be willing and able to work from > CVS -- I'll happily contact them and ask, unless you've had a volunteer > from the list already. Please do so. There're some BSDers on the list, but we need one that doesn't have a reentrant resolver library. > For what it's worth, though, the code looks right. :) > > > I'll make a 0.8.6rc1 after receiving your feedback with a view > > to a next release (its been a long time, and the CVS is stable > > enough). > > One possible caveat -- I've had some trouble with local file browsing > using cvs-dillo. strace says the file is being accessed and read, but > the contents don't appear on screen. > > pkill dillo > pkill dpi > ./configure && make > sudo make install > dillo ./dillorc > > and the screen stays grey. > > It may be a local config issue here; but confirm that it works for you > before calling it released! It works here. Note: while typing fast I managed to "reproduce" the bug, but it was because I standed on src/ while doing make, and "dillorc" is in "../" from there! :-) If you find a way to reproduce the bug, it should be tackled before the release. > More when I've played with new-CVS a bit. Good! -- Cheers Jorge.-

2 2

Re: [Dillo-dev] dillo 0.8.5 / OpenBSD 3.6 help request
by Jorge Arellano Cid March 15, 2006

March 15, 2006

Hi Francis, On Sun, Mar 12, 2006 at 02:32:36PM +0000, Francis Daly wrote: > On Sat, Mar 11, 2006 at 04:45:39PM -0300, Jorge Arellano Cid wrote: > > On Sat, Mar 11, 2006 at 05:12:21PM +0000, Francis Daly wrote: > > Hi Jorge, > > > > I have a report than on a stock OpenBSD 3.6 box, using dillo 0.8.5, > > > the following recipe seems to reliably(*) cause dillo to cease responding. > > > > Some of the BSDs don't provide a reentrant gethostbyname() > > function. This makes "Dillo" freeze when resolving names > > concurrently. > > D'oh, yes, of course, it's there in README. > > Preliminary reports suggest that commenting dns.c line 41 helps the > problem, and quite possibly fixes it altogether. > > > I went to the site and saw several different hostnames. This > > may be the answer. > > > > One way to solve this is to delegate the DNS resolving to a dpi > > and to have a special one linked to an async DNS library for > > BSDs. > > In the spirit of the suggestion at > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-April/000422.html > here's a patch which implements a configure --disable-threaded-dns option. > > In order to keep threaded as the default, I switched the logic of > G_DNS_THREADED to be G_NO_GNS_THREADED; I'm not sure what the reason for > the name is (it's been in CVS since April 2000 when the file was added) > but possibly NO_G_DNS_THREADED or something would fit the pattern better. > > The alternative is to make no-threaded the default and require > --enable-threaded-dns to turn it on -- that would have a working system > for everyone, but threaded users would have a less effective system than > they could have. > > If you prefer that I'll code it. OK. I checked the patch, and recoded it to use D_DNS_THREADED, D_DNS*, and the same "./configure --disable-threaded-dns". Commited and in CVS now. Please test it. I'll make a 0.8.6rc1 after receiving your feedback with a view to a next release (its been a long time, and the CVS is stable enough). Note: I'm keeping 0.8.6pre in sync with the FLTK2-based tree. -- Cheers Jorge.-

1 0