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