April 2004 - Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]A button theme for Dillo 0.8.0

by Jorge Arellano Cid

On Wed, 7 Apr 2004, Geek wrote: > While I was stuck with no internet, I made a theme for Dillo I call "cobalt". > > Enjoy! Oh, it was added to http://www.dillo.org/Icons/ by Apr 8! :-) I assume you didn't get the answer message. Thxs & Cheers Jorge.-

April 12, 2004

Re: [Dillo-dev]Can't start dpid

by Barry Kauler

Ok, for those reading this thread for the first time, the problem is dpid won't start in my custom Puppy Linux distro. Maybe I've found the solution? I have a build environment, but then I run a script to create the Puppy filesystem, which copies files from the build environment. It copies dillo, dpid, dpidc into /usr/local/bin, all of the stuff in /usr/local/lib/dillo gets copied across, however, the script doesn't copy dpidrc and dillorc from /usr/local/etc, as in Puppy all of /usr is read-only. Instead, I have placed dpidrc and dillorc into ~/.dillo, except that this seems to have not been upgraded. I'm running Puppy right now and what I see in ~/.dillo are the files .073 cookiesrc dillorc So, is this my problem? I just checked the dates on those files, and they are from the old 0.7.3 version. It does seem that my oversight is to blame here! One question though, is there any problem with continuing to use the old dillorc? I ask this as when people upgrade to the latest Puppy they may have modified dillorc and I don't want to just overwrite their dillorc file. Looks like Puppy and Dillo are back in business! Puppy v0.8.5 should be out soon, like maybe another week. Regards, Barry Kauler On Sat, 10 Apr 2004 00:56:07 -0600 Barry Kauler <bkauler(a)goosee.com> wrote: > Ok, I've joined the dillo-dev list! > > On Fri, 9 Apr 2004 08:13:17 -0400 (CLT) > Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > > > I should also explain that I have my own distro, Puppy Linux, > > > and everything is compiled against uClibc, not glibc. > > > (www.goosee.com/puppy) > > > > Oh, it would be interesting to have Dillo running under uClibc! > > Dillo has been in Puppy right from the start (which was about one > year ago). A few months ago I changed over to uClibc and recompiled > everything, including Dillo, and all was well until I upgraded to > Dillo v0.8.0. > > > Check if you can run them crom the CLI: > > > > cd /usr/local/lib/dillo/dpi/hello > > ./hello.filter.dpi > > I'm doing this as root. When I try this I get: > > hello.dpi:: starting... > > and that's it, nothing more, doesn't exit until I ctrl-c. > No error message. > ...what is it supposed to do? > > Regards, > Barry Kauler > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

April 10, 2004

Re: [Dillo-dev]Can't start dpid

by Barry Kauler

Ok, for those reading this thread for the first time, the problem is dpid won't start in my custom Puppy Linux distro. Maybe I've found the solution? I have a build environment, but then I run a script to create the Puppy filesystem, which copies files from the build environment. It copies dillo, dpid, dpidc into /usr/local/bin, all of the stuff in /usr/local/lib/dillo gets copied across, however, the script doesn't copy dpidrc and dillorc from /usr/local/etc, as in Puppy all of /usr is read-only. Instead, I have placed dpidrc and dillorc into ~/.dillo, except that this seems to have not been upgraded. I'm running Puppy right now and what I see in ~/.dillo are the files .073 cookiesrc dillorc So, is this my problem? I just checked the dates on those files, and they are from the old 0.7.3 version. It does seem that my oversight is to blame here! One question though, is there any problem with continuing to use the old dillorc? I ask this as when people upgrade to the latest Puppy they may have modified dillorc and I don't want to just overwrite their dillorc file. Looks like Puppy and Dillo are back in business! Puppy v0.8.5 should be out soon, like maybe another week. Regards, Barry Kauler On Sat, 10 Apr 2004 00:56:07 -0600 Barry Kauler <bkauler(a)goosee.com> wrote: > Ok, I've joined the dillo-dev list! > > On Fri, 9 Apr 2004 08:13:17 -0400 (CLT) > Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > > > I should also explain that I have my own distro, Puppy Linux, > > > and everything is compiled against uClibc, not glibc. > > > (www.goosee.com/puppy) > > > > Oh, it would be interesting to have Dillo running under uClibc! > > Dillo has been in Puppy right from the start (which was about one > year ago). A few months ago I changed over to uClibc and recompiled > everything, including Dillo, and all was well until I upgraded to > Dillo v0.8.0. > > > Check if you can run them crom the CLI: > > > > cd /usr/local/lib/dillo/dpi/hello > > ./hello.filter.dpi > > I'm doing this as root. When I try this I get: > > hello.dpi:: starting... > > and that's it, nothing more, doesn't exit until I ctrl-c. > No error message. > ...what is it supposed to do? > > Regards, > Barry Kauler > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

April 10, 2004

Re: [Dillo-dev]Can't start dpid

by Barry Kauler

Ok, I've joined the dillo-dev list! On Fri, 9 Apr 2004 08:13:17 -0400 (CLT) Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > I should also explain that I have my own distro, Puppy Linux, > > and everything is compiled against uClibc, not glibc. > > (www.goosee.com/puppy) > > Oh, it would be interesting to have Dillo running under uClibc! Dillo has been in Puppy right from the start (which was about one year ago). A few months ago I changed over to uClibc and recompiled everything, including Dillo, and all was well until I upgraded to Dillo v0.8.0. > Check if you can run them crom the CLI: > > cd /usr/local/lib/dillo/dpi/hello > ./hello.filter.dpi I'm doing this as root. When I try this I get: hello.dpi:: starting... and that's it, nothing more, doesn't exit until I ctrl-c. No error message. ...what is it supposed to do? Regards, Barry Kauler

April 10, 2004

Re: [Dillo-dev]Can't start dpid

by Barry Kauler

Ok, I've joined the dillo-dev list! On Fri, 9 Apr 2004 08:13:17 -0400 (CLT) Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > I should also explain that I have my own distro, Puppy Linux, > > and everything is compiled against uClibc, not glibc. > > (www.goosee.com/puppy) > > Oh, it would be interesting to have Dillo running under uClibc! Dillo has been in Puppy right from the start (which was about one year ago). A few months ago I changed over to uClibc and recompiled everything, including Dillo, and all was well until I upgraded to Dillo v0.8.0. > Check if you can run them crom the CLI: > > cd /usr/local/lib/dillo/dpi/hello > ./hello.filter.dpi I'm doing this as root. When I try this I get: hello.dpi:: starting... and that's it, nothing more, doesn't exit until I ctrl-c. No error message. ...what is it supposed to do? Regards, Barry Kauler

April 10, 2004

[Dillo-dev]Re: bugfix for bug#500

by Jorge Arellano Cid

On Thu, 8 Apr 2004, Andreas Mueller wrote: > Hi, Hi! > the attached small patch fixes bug#500. > > > Andreas Thanks a lot, that one was hard to chase! Commited. Cheers Jorge.-

April 8, 2004

Re: [Dillo-dev]Theme for Dillo 0.8.0

by Jorge Arellano Cid

On Thu, 8 Apr 2004, Gregg wrote: > Hi all, > > I made a button theme for 0.8.0 - Cobalt. > > Enjoy! Nice theme. Just added it to our Icons section: http://www.dillo.org/Icons/ Cheers Jorge.-

April 8, 2004

Re: [Dillo-dev]About proxy authorization && password storing

by Ivan Daniluk

Hi! You wrote at Tue 06 Apr 2004 17:06: > AFAIS the simplest way to to it is to ask for the proxy > password when dillo starts, that is, before any query is made, > probably after the splash screen is displayed. > > That way, things would reach the same simplicity as in the > first patch! Yes, this simplify all that mess =) I've done as you suggested. > Now, if after this patch, you want to keep on working on basic > authentication, be sure to contact Madis (AFAIR he once worked on > it), and I can make the CCC bindings to stop/resume/forward the > querying process. Ok! Great. I'll contact him. > > > And, the last note on patch. It's about following lines in > > IO/http.c: + if ( strchr(prefs.http_proxyuser, ':') ) > > + { > > + DEBUG_MSG(5, "Storing proxy password in dillorc is > > insecure!\n"); + ask_proxy_passwd = FALSE; > > + HTTP_Proxy_Auth_base64 = > > a_Misc_encode_base64(prefs.http_proxyuser); + } > > It allows user to store in config file not only proxy user name, > > but pair "user:password" as well. I've done it's mainly for > > convenience, but of cource we can remove it from patch. > > Hmmm, this is one I'm not yet sure of. On one hand, it is very > handy not to have to enter the password every time, and on the > other, stealing the proxy's password becomes quite simple > (for instance, a bathroom break and it's gone! ;). > > [minutes thinking...] > > It's not a thing I'd recommend. Now, as Dillo project is > explicitly concerned about security, it can't do otherwise. > Perhaps you may leave that portion of code commented out, so the > responsibility is left to the one that decides to enable it. Ok, I just commented it out. Here attached pre2 :) patch. What about hiding symbols, when entering password? (i.e, replacing visible characters by asterisk symbol). Maybe we just have to add additional parameter in a_Interface_make_dialog(..), like "gboolean entry_hidden" or smth? Or implement a new dialog_window type specially for login/password asking? It will be useful for basic authentication stuff. Regards! -- Ivan Daniluk, software developer, Ukrainian Computer Labs, Kiev, Ukraine mailto:Ivan.Daniluk@ucl.com.ua

April 8, 2004

[Dillo-dev]Theme for Dillo 0.8.0

by Gregg

Hi all, I made a button theme for 0.8.0 - Cobalt. Enjoy! -- Gregg

April 8, 2004

Re: [Dillo-dev]GTK 1.2 and Dillo's future

by Philip Blundell

On Wed, 2004-04-07 at 14:46, John wrote: > But I have to ask, why not just keep using GTK 1.2? GTK 1.2 is mature, and lite. Perhaps it will start an effort to keep GTK 1.x alive? As far as I'm concerned, the disadvantages of sticking with 1.2 are: - lack of support for client-side antialiased fonts, multiple displays, internationalisation, and other modern toolkit features - abandoned upstream; nobody is even fixing bugs in 1.2 at this point. - used by increasingly few other programs, which creates a headache for system integrators. For example, every other program in the distributions that I work with is using GTK 2 now. I would love to be able to ship a recent Dillo, but this would mean installing libgtk1.2 and libglib1.2 (plus probably a pile of server-side fonts for it to use) and I can't spare that amount of flash. p.

April 8, 2004