- Dillo-dev - lists.mailman3.com

New developers?

by corvid＠lavabit.com

Jorge wrote: > Some people have written me expressing their will to join as > developers. They have introduced themselves, asked questions and > for some advice. I've answered, hinted and made suggestions. > Since all of them have remained silent, I wonder whether they are > concentrated studying the code, or simply changed their mind... Maybe the answers/suggestions should always go on the website somewhere so that you don't have to repeat yourself to people who just disappear. [So much ink has been spilled in the free software world over the years about being very very welcoming -- usually in the context of why women have better things to do than contribute to free software -- and I can really see now why those involved in projects might not roll out the parades and fireworks until seeing attempts at patches or at least detailed discussion...]

Nov. 22, 2008

Q: Thoughts on a user/password dialog for an HTTP AUTH dpi?

by Johannes.Hofmann＠gmx.de

Hi, On Thu, Nov 20, 2008 at 04:08:21PM +0000, Jeremy Henty wrote: > On Thu, Nov 20, 2008 at 09:14:56AM -0300, Jorge Arellano Cid wrote: > > On Thu, Nov 20, 2008 at 02:42:19AM +0000, Jeremy Henty wrote: > > > > > > Is this a good way to do it or is there a smarter way? All > > > comments and advice are welcome. > > > > It looks OK. > > Good! > > > I wonder why a dpi is deemed necessary for this. > > I don't know whether it is necessary. That's why I asked for > comments. I just thought that HTTP authentication looked rather > "cookie-ish" and decided to copy and modify the cookies > implementation. I'm new to this part of Dillo so I am following > established practice. I already have a dummy auth dpi running and > hooked into the main Dillo program, so I think that the dpi part of > things is by far the easiest bit. The most work is actually > implementing authentication! Debian seems to ship dillo with a patch for basic authentication: http://patch-tracking.debian.net/patch/series/dl/dillo/0.8.5-4.1/01_i18n Might be worth looking at. Cheers, Johannes

Nov. 22, 2008

shaded colors and css

by Johannes.Hofmann＠gmx.de

Hello, mapping css properties to dw::core::style::Style members went very smooth, because Style was obviously implemented with css in mind. Just for the shaded color thing I can't find a corresponding concept in css. What exactly is the definition of a shaded color? Is it just a bit darker than the normal one? Does anyone know the corresponding concept in css? Cheers, Johannes

Nov. 22, 2008

New developers?

by jcid＠dillo.org

Hi, Some people have written me expressing their will to join as developers. They have introduced themselves, asked questions and for some advice. I've answered, hinted and made suggestions. Since all of them have remained silent, I wonder whether they are concentrated studying the code, or simply changed their mind... Are you still there? -- Cheers Jorge.-

Nov. 22, 2008

[jcid@dillo.org: Re: CSS merge looks great!]

by jcid＠dillo.org

On Sat, Nov 22, 2008 at 01:15:56PM +0100, Andreas Kemnade wrote: > Hi, > > On Fri, 21 Nov 2008 14:11:23 -0300 > Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > > > Hi Jorge, > > > > > > On Thu, Nov 20, 2008 at 02:31:19PM -0300, Jorge Arellano Cid wrote: > > > > Hi Johannes, > > > > > > > > After sometime finally I'm back to CSS. So far the merged code > > > > looks great. I'd like to make this the official branch soon. > > > > > > Great! But I still consider the CSS support a prototype and I think > > > it's time to step back for a moment and consider what we've learned > > > so far. > > > > OK. > > > > As CSS is the most demanded feature, I was thinking along the > > lines of making a release that implements a small subset of CSS, > > to let the world know that the main pieces are already coded, and > > to attract more developers to help completing it. > > > I really hope there will be a switch to *disable* css parsing. > In my opinion there are a lot of sites which are more usable on > mobile devices or devices with unusual screen sizes (800x480 like the eeepc) > without CSS. Yes, that's simple to do. Even more, currently (i.e. with the mercurial repository) you can specify *your* CSS stylesheet in ~/.dillo/style.css, and tailor it for your needs. As remote stylesheet loading isn't hooked yet, you can see the desired effect now. > I can really remember cases where I switched from firefox to dillo > because css (or its interpretation by firefox?) was so bad that I even cannot > click on some links. > > But if course, in more cases having css is really great! > > > For instance, if just colors were working OK (i.e. rendering > > looked better with CSS-colors support), that's be a good starting > > point. > > Yes, colors would be nice. That would probably give the opportunity to write > small patches for e.g. font support in CSS without the need for deep conceptual > decisions. So that can be a starting point for developers which are not that > deep in the code yet. That's the idea! -- Cheers Jorge.-

Nov. 22, 2008

[jcid@dillo.org: Re: CSS merge looks great!]

by akemnade＠tzi.de

Hi, On Fri, 21 Nov 2008 14:11:23 -0300 Jorge Arellano Cid <jcid(a)dillo.org> wrote: > > Hi Jorge, > > > > On Thu, Nov 20, 2008 at 02:31:19PM -0300, Jorge Arellano Cid wrote: > > > Hi Johannes, > > > > > > After sometime finally I'm back to CSS. So far the merged code > > > looks great. I'd like to make this the official branch soon. > > > > Great! But I still consider the CSS support a prototype and I think > > it's time to step back for a moment and consider what we've learned > > so far. > > OK. > > As CSS is the most demanded feature, I was thinking along the > lines of making a release that implements a small subset of CSS, > to let the world know that the main pieces are already coded, and > to attract more developers to help completing it. > I really hope there will be a switch to *disable* css parsing. In my opinion there are a lot of sites which are more usable on mobile devices or devices with unusual screen sizes (800x480 like the eeepc) without CSS. I can really remember cases where I switched from firefox to dillo because css (or its interpretation by firefox?) was so bad that I even cannot click on some links. But if course, in more cases having css is really great! > For instance, if just colors were working OK (i.e. rendering > looked better with CSS-colors support), that's be a good starting > point. Yes, colors would be nice. That would probably give the opportunity to write small patches for e.g. font support in CSS without the need for deep conceptual decisions. So that can be a starting point for developers which are not that deep in the code yet. Greetings Andreas Kemnade

Nov. 22, 2008

A warning about HTTPS and proxies

by corvid＠lavabit.com

In the dillo 2.0 dillorc, I had written that HTTPS uses wget, and that configuring wget to use a proxy would therefore send https traffic through it. That's wrong; I was repeating outdated information. Right now, HTTPS will not use a proxy at all. I bring this to your attention in case it matters to those using Tor and the like. ------ In other news, have you noticed that the dillo website is particularly speedy now? Andreas turned on HTTP compression :)

Nov. 21, 2008

[Johannes.Hofmann@gmx.de: Re: CSS merge looks great!]

by jcid＠dillo.org

FYI, -- Cheers Jorge.-

Nov. 21, 2008

[jcid@dillo.org: Re: CSS merge looks great!]

by jcid＠dillo.org

FYI, -- Cheers Jorge.-

Nov. 21, 2008

[Johannes.Hofmann@gmx.de: Re: CSS merge looks great!]

by jcid＠dillo.org

FYI, -- Cheers Jorge.-

Nov. 21, 2008