- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] dillo-0.8.6-rc1

by robert w hall

In message <200603232236.29512.kelson(a)pobox.com>, Kelson Vibber <kelson(a)pobox.com> writes >On Tuesday 21 March 2006 10:13 am, Jorge Arellano Cid wrote: >> The new dillo-0.8.6-rc1.tar.bz2 tarball is ready for testing! > >So far, so good. Tested (not under much load) on Fedora Core 4 and 5, >Mandriva 2006, and Mandrake 10.1, all 32-bit Intel. I've finally managed to >get SuSE 10 to boot (it kept hanging on hardware config), so I should have >that available by the time the release is ready. Am I the only person likely to test on a Playstation 2? (I haven't used the PS2 for a bit and my sons say the CDROM only works when the whole thing is in bits). If someone else is testing I may not > >> Packagers are encouraged to include the statically linked FLTK2 >> GUI for downloads in their end-user packages. (And I'm not aware of any FLTK packages for it...) -- robert w hall

March 24, 2006

Re: [Dillo-dev] dillo-0.8.6-rc1

by Kelson Vibber

On Tuesday 21 March 2006 10:13 am, Jorge Arellano Cid wrote: > The new dillo-0.8.6-rc1.tar.bz2 tarball is ready for testing! So far, so good. Tested (not under much load) on Fedora Core 4 and 5, Mandriva 2006, and Mandrake 10.1, all 32-bit Intel. I've finally managed to get SuSE 10 to boot (it kept hanging on hardware config), so I should have that available by the time the release is ready. > Packagers are encouraged to include the statically linked FLTK2 > GUI for downloads in their end-user packages. This is probably going to be tricky, since several of the older Red Hat distributions I build for are done using mach, which relies on rpm dependencies to install packages needed for building. Anything for which I have a real installation should be fine, since I can get a command line and build the FLTK2 libraries. Also, since I know people are downloading the source RPM for distributions on which I haven't built it, I'm working out ways to make the FLTK-based GUI optional. I've added an option to the RPM spec that lets you turn on the --disable-dlgui configure option. The only thing I'm trying to decide is which way to set the default. I'll definitely be able to get Fedora Core 4 and 5, Mandriva 2006, and SuSE 10. Over the next few days, I'll be checking to see which other partitions, chroots, and UMLs still work. -- Kelson Vibber www.hyperborea.org

March 24, 2006

Re: [Dillo-dev] dillo and no-cache

by digitek

Jorge Arellano Cid wrote: <snip> > > Yes, send it directly to me. Will do. I'll send you a link off list (my server is an old p266 thinkpad and doesn't like a lot of traffic) The changes I made to 0.8.5 are actually here: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-October/002389.html These were for 0.8.3 but I didn't see them rolled into 0.8.5, so I figured the patch was just not included yet, or it was dropped for whatever reason. I added them into 0.8.5 to the best of my ability. > > A long time ago, some sites discovered that a reload request on > every page could boost their advertising hits (i.e. more money). Yeah, that figures... > It would be interesting to know what you're using the patch > for (as far as the NDA allows). Having some background always > helps. > > What I'm using it for is a menuing system on an embedded device. The user selects icons to get from menu to menu, however each icon needs to trigger through a cgi call. With the caching in place, these triggers are not being sent (much the same as an advertisement). So, Dillo is working perfectly, and exactly as it is supposed to. I just need a little different functionality. Yes, as you mention NDA, I don't know how much more detail I can go into, but if you would like to know more, shoot me an email off list and I'll talk to the Head Honcho and see what he is willing to discuss. Also, thanks to everyone that has put so much effort into this great little browser. It is a perfect fit for what I'm working on. No bloat, just render some html and interface with CGI. It really is a nice piece of work guys (and gals?) Thomas -- digitek(a)charter.net key id: 0xF6FA6D1E huh?: http://google.com/search?q=gnupg+secure+email

March 23, 2006

[article] trimming down autoconf's configure scripts by using pkg-config

by Enrico 'nekrad' Weigelt

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 ---------------------------------------------------------------------

March 23, 2006

Re: [Dillo-dev] Progress on porting to FLTK2?

by Diego Sáenz

El Tue, 21 Mar 2006 11:49:09 -0400 Jorge Arellano Cid <jcid(a)dillo.org> escribio: > Hola Diego! Hola [...] > > One thing that's independent and that you can help us with is > with a preferences file parser. At some point we'll get rid of > glib so the parser needs a rewrite. A very simple parser, not as > complex as the current. Ok, i have see that code yet for a preferences.dpi(it must show and allow changes in rc files with a html UI when finished, the code is too dirty to show now) that i write when i have time and mood. Rewrite parser seems easy to me. > > This is roughly: > > variable=<string-value> pairs and > e.g. > url=http://foo.bar/here > title="Hi there" // Double quoted > font_factor=1.2 // let conversion later > > #<comments> > > with some spelling error checking. Ok > Another one is to replace the g_string_* functions, but I have > some code for that. Just need to search my harddisk! ;) I think i can do that too, pass me the code if you want :) > > -- > Cheers > Jorge.- Saludos Diego.

March 22, 2006

Re: [Dillo-dev] dillo-0.8.6-rc1

by Jorge Arellano Cid

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)

March 22, 2006

Re: [Dillo-dev] dillo-0.8.6-rc1

by Jorge Arellano Cid

Hi, On Tue, Mar 21, 2006 at 11:40:04PM -0500, mike obrien wrote: > sorry, is this one an FLTK version? No, it is a GTK1 version that comes with a FLTK2-based downloads plugin. The build process will stop if you don't have FLTK2 installed, because the FLTK2-based downloads dpi is the default, and suggested choice. A simple way to install FLTK2 is to go to www.fltk.org and download the latest weekly snapshot. Now, if you don't want FLTK2 at all, it is possible to use the old downloads dpi. Just check "./configure --help" to know how. End users (those that install from packaged binaries) don't need FLTK2 installed at all, because the downloads dpi will be built statically-linked. -- Cheers Jorge.-

March 22, 2006

Re: [Dillo-dev] dillo and no-cache

by Jorge Arellano Cid

Hi, On Tue, Mar 21, 2006 at 05:23:09PM -0600, digitek wrote: > > > Francis Daly wrote: > >On Tue, Mar 21, 2006 at 04:45:44PM -0600, digitek wrote: > > > >>I noticed 0.8.5 loads pages from cache regardless of the > >>'content=no-cache' meta tag. > > > >Yes. > > Cool. > > > > > >>Near as I can tell from the mailing list, this is by design. > > > >Also yes. > > Also cool. > > <snip> > >(Although without having seen the patch, it should probably honour the > >HTTP headers rather than the meta tag. But that's a topic that doesn't > >need to be discussed here.) > > > >All the best, > > > > f > > Understood. Thanks. > > I intend to use this in a commercial product and need to make my changes > freely available under the GPL. > Does anyone have a preference where ? Yes, send it directly to me. A long time ago, some sites discovered that a reload request on every page could boost their advertising hits (i.e. more money). Dillo avoids this problem by letting the user hit reload for the latest page. Of course this has the downside of breaking on honest sites that use the reload request to somehow keep state of a session. A good solution is like with cookies, to only honour certain trusted sites on such cache directives. It would be interesting to know what you're using the patch for (as far as the NDA allows). Having some background always helps. -- Cheers Jorge.-

March 22, 2006

Re: [Dillo-dev] dillo-0.8.6-rc1

by mike obrien

sorry, is this one an FLTK version? mike On Tue, 21 Mar 2006 14:13:38 -0400 Jorge Arellano Cid <jcid(a)dillo.org> wrote: > Hi there, > > The new dillo-0.8.6-rc1.tar.bz2 tarball is ready for testing! > > Please grab it from: > > http://www.dillo.org/download/dillo-0.8.6-rc1.tar.bz2 > > ... test and send feedback. > > Packagers are encouraged to include the statically linked FLTK2 > GUI for downloads in their end-user packages. > > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

March 22, 2006

Re: [Dillo-dev] dillo and no-cache

by digitek

Francis Daly wrote: > On Tue, Mar 21, 2006 at 04:45:44PM -0600, digitek wrote: > >> I noticed 0.8.5 loads pages from cache regardless of the 'content=no-cache' >> meta tag. > > Yes. Cool. > >> Near as I can tell from the mailing list, this is by design. > > Also yes. Also cool. <snip> > (Although without having seen the patch, it should probably honour the > HTTP headers rather than the meta tag. But that's a topic that doesn't > need to be discussed here.) > > All the best, > > f Understood. Thanks. I intend to use this in a commercial product and need to make my changes freely available under the GPL. Does anyone have a preference where ? Thanks. -- digitek(a)charter.net key id: 0xF6FA6D1E huh?: http://google.com/search?q=gnupg+secure+email

March 21, 2006