January 2009 - Dillo-dev - lists.mailman3.com

Dillo 2 in Tiny Core Linux

by corvid＠lavabit.com

Colin wrote: > Dillo 2 doesn't use any OpenGL does it? I compiled FLTK 2 without OpenGL > support, and I didn't know if that would be a problem. Nope. I normally configure fltk without gl. It's a little bit annoying that fltk2 still tries to compile its tests that use OpenGL, but not a big deal... PS I was trying to list my idea of dependencies in the FAQ recently because one of my pet peeves is when I want to try some software but it turns out that it won't compile unless I get a ton of libraries...which in turn each require a ton of libraries...and then I typically cut my losses and delete it all.

Jan. 15, 2009

Dillo 2 in Tiny Core Linux

by xentalion＠gmail.com

Hello, Just wanted to let you that I've built a package of Dillo 2 for Tiny Core Linux. http://www.tinycorelinux.com/ It is now in the repositories for Tiny Core. :D Dillo 2 doesn't use any OpenGL does it? I compiled FLTK 2 without OpenGL support, and I didn't know if that would be a problem. Thanks, Colin

Jan. 15, 2009

patch: focus URL opened from command line

by corvid＠lavabit.com

I see there's a new entry in the bug tracker reporting that after opening multiple URLs from the command line, shift-right and shift-left do not work immediately. What do you think of something like the attached patch? The downside is that it wastes cycles when you click on a link, but I was reluctant to let dillo.cc know about this UI stuff.

Jan. 14, 2009

CSS speed

by corvid＠lavabit.com

Johannes wrote: > On Tue, Jan 13, 2009 at 08:00:37PM +0000, corvid wrote: > > Johannes wrote: > > > pages with complex CSS feel a bit slow with the current css-prototype > > > and gprof shows a huge number of CssSelector::match() calls. > > > Attached is a patch that tries to improve that by: > > > > > > * putting CssSelectors into hashtables so that we only need to match > > > against a small subset of CssSelectors. > > > > > > * avoiding repeated matches of CssSimpleSelectors against the same > > > part of the doctree. > > > > > > Please test and report if there is a real world speedup. > > > > Wow! > > > > In the past, my best example had been pages on reddit.com that had > > at least maybe 300 comments. They had been unusably slow--although > > this would encourage a person not to waste time looking at reddit. > > > > Quite usable now. > > Great. reddit.com is looking strange though. There is this weird > blue circle... I think it's an iframe's bullet hypertrophied by #ad-frame { border: 0px; overflow: hidden; width: 300px; height: 300px; } <iframe id="ad-frame" frameborder="0" scrolling="no" name="ad-frame" src="/static/ad_default.html"></iframe>

Jan. 14, 2009

CSS speed

by Johannes.Hofmann＠gmx.de

On Tue, Jan 13, 2009 at 08:00:37PM +0000, corvid wrote: > Johannes wrote: > > pages with complex CSS feel a bit slow with the current css-prototype > > and gprof shows a huge number of CssSelector::match() calls. > > Attached is a patch that tries to improve that by: > > > > * putting CssSelectors into hashtables so that we only need to match > > against a small subset of CssSelectors. > > > > * avoiding repeated matches of CssSimpleSelectors against the same > > part of the doctree. > > > > Please test and report if there is a real world speedup. > > Wow! > > In the past, my best example had been pages on reddit.com that had > at least maybe 300 comments. They had been unusably slow--although > this would encourage a person not to waste time looking at reddit. > > Quite usable now. Great. reddit.com is looking strange though. There is this weird blue circle...

Jan. 14, 2009

CSS freeze

by jcid＠dillo.org

On Mon, Jan 12, 2009 at 01:25:40PM +0100, Hofmann Johannes wrote: > On Fri, Jan 09, 2009 at 04:32:33PM -0300, Jorge Arellano Cid wrote: > > Hi, > > > > Current and former CSS protos freeze on this page: > > > > http://www.instantfundas.com/2007/12/5-opera-tricks-you-did-not-know-about.… > > I've made some adjustments to the CSS parser that fix the problem > for me. Please retest. Good! Multiple return points within a function is asking for trouble. Good you removed them with the patch. It works OK here. -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

Jan. 13, 2009

CSS speed

by corvid＠lavabit.com

Johannes wrote: > pages with complex CSS feel a bit slow with the current css-prototype > and gprof shows a huge number of CssSelector::match() calls. > Attached is a patch that tries to improve that by: > > * putting CssSelectors into hashtables so that we only need to match > against a small subset of CssSelectors. > > * avoiding repeated matches of CssSimpleSelectors against the same > part of the doctree. > > Please test and report if there is a real world speedup. Wow! In the past, my best example had been pages on reddit.com that had at least maybe 300 comments. They had been unusably slow--although this would encourage a person not to waste time looking at reddit. Quite usable now.

Jan. 13, 2009

focus after closing tab

by Johannes.Hofmann＠gmx.de

Hi, sometimes when closing a tab it feels that dillo focuses the "wrong" tab. Therefore I made a patch that puts the focus back to the tab from which a tab was opened. That way I always get back to the "base page" when closing a tab. Howerver I'm not sure that this is always right, e.g. when opening multiple tabs from one base page, one might want to read one after the other without going back to the base page. What do you think, which page should be focused when closing a tab: * the tab from which the closed one was opened? * the tab to the left of the closed one? * the most recently opened one? Cheers, Johannes

Jan. 13, 2009

CSS speed

by Johannes.Hofmann＠gmx.de

Hi, pages with complex CSS feel a bit slow with the current css-prototype and gprof shows a huge number of CssSelector::match() calls. Attached is a patch that tries to improve that by: * putting CssSelectors into hashtables so that we only need to match against a small subset of CssSelectors. * avoiding repeated matches of CssSimpleSelectors against the same part of the doctree. Please test and report if there is a real world speedup. Cheers, Johannes

Jan. 13, 2009

CSS freeze

by Johannes.Hofmann＠gmx.de

On Fri, Jan 09, 2009 at 04:32:33PM -0300, Jorge Arellano Cid wrote: > Hi, > > Current and former CSS protos freeze on this page: > > http://www.instantfundas.com/2007/12/5-opera-tricks-you-did-not-know-about.… I've made some adjustments to the CSS parser that fix the problem for me. Please retest. Cheers, Johannes

Jan. 12, 2009