Hi all, On Aug 24 17:07:21, Sam Trenholme wrote:
The problem is that Dillo doesn't support a lot of high-profile internet sites right now.
I would look at the "i18n" version and try and add Javascript support to it (or, better yet, EMCAscript support). Personally, I think Dillo needs some level of Javascript support; a lot of high-profile sites (can we say MySpace and their crappy JavaScript and HTML) plain simply do not work without Javascript.
I also believe that Dillo shouldn't try to get CSS support; the last thing I want is yet another browser with buggy CSS that I have to design around. If Dillo is going to support CSS, I don't think the support should become a part of a stable release of Dillo until Dillo can render ACID2 perfectly. A site that uses CSS is perfectly usable, albeit a bit ugly, in a browser that doesn't have CSS.
On Aug 24 21:56:17, Hans Hohenfeld wrote:
I definitely disagree. From my point of view, CSS is the most missing feature in Dillo. Frames are minor impotant (as only bad websites use them), Javascript is very much necessary, but CSS seems to be the most important feature Dillo needs. Some basic CSS attributes like colors, positioning would be a good start. I agree, that it is very important to implement CSS support as close to the standard as possible.
I also think that CSS is the most missing feature - while a well written page using CSS looks good even without it, many pages just rely on being CSS-interpreted (or look ugly). HTML/CSS is the most basic combo for a browser anyway, I think. As for JavaScript, what pages worth reading need JavaScript to work? With the lack of dillo-dev manpower, this is a feature I don't really miss. Tabs, on the other hand, are extremely useful - I dream of the day they come to dillo, making it able to have many pages rendered at once (each with dillo's lightning speed). Frames are evil, everybody knows that. On Aug 26 12:11:46, Jorge Arellano Cid wrote:
GTK1 is an abandoned library, it has become the much bigger, slower and capable GTK2, precisely because it was not suited for solving certain "desktop" problems. Dillo's main advantage is a tradeoff of features for speed. If the speed edge disappears, what do we have?
Totaly agreed.
As a matter of fact, the widget style structures inside Dillo are shaped for CSS, and we presented a CSS parser prototype at FOSDEM 2005. Merging the CSS parser into the current tree would start CSS support.
Looking at the FOSDEM presentation, I can't seem to find the CSS bits (in neither mgp or html - http://www.dillo.org/fosdem2005/dillo-18.html points to "http://www.dillo.org/fosdem2005/....." Can I get the CSS part of the presentation somewhere? Thanks Jan