- Dillo-dev - lists.mailman3.com

line-height

by corvid＠lavabit.com

Just committed some line-height code that Johannes and I wrote. When line-height is less than the font's ascent+descent, unhighlighting gets confused. I think it has to do with using the line dimensions for 'area' for drawing the background. I'll dig into it a little more later on. PS I see that firefox puts more space between its paragraphs than we do. Their value seems to be related to the font size, or the default font size, or something. Is there anything deep behind our use of 9?

April 4, 2010

[matthew.t.craig@gmail.com: dillo question]

by Johannes.Hofmann＠gmx.de

> > hello .. started using dillo on a lemote yeeloong, which runs firefox slowly > dillo works great for me there! nice! > is there a way to use dillo with liferea feed reader, so links open > within dillo on a new tab? currently we don't have that feature, but it would definately be doable. There was a similar discussion some time ago: http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-October/006912.html Cheers, Johannes

April 2, 2010

[matthew.t.craig@gmail.com: dillo question]

by jcid＠dillo.org

Hi, -- Cheers Jorge.-

April 1, 2010

[jeffdewe@gmail.com: Dillo]

by jcid＠dillo.org

Hi, In a nutshell: * FLTK2 halves the memory footprint of GTK1 [1]. * GTK2 is bigger and can double GTK1 [2] (4x factor). This means the increased binary size of a FLTK2 dillo static binary is compensated after browsing a couple of pages. I hope FLTK stops being a problem when FLTK-1.3 is released and included in the distros repos. We'll switch to it as soon as the release is available. [1] http://www.dillo.org/memory.html [2] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2006-September/003097.ht… -- Cheers Jorge.-

April 1, 2010

[jeffdewe@gmail.com: Dillo]

by andreas＠kemnade.info

Hi, just one more practical explanation of the advances the more ressource friendly fltk2 has. BTW: fltk2 does not necessarily depend on GL. Imagine you have a device with limited ressources. Running a browser bigger than dillo might be possible. Perhaps even a bigger loading time might be ok in some situations. For example if you hve only gprs to connect to the internet, then loading of many pages takes ages anyway. But in case of multitasking there is really a harder limit. If you have multiple applications running which are a bit bigger, then you really have problems when you start a fat browser. Here is an example: Just some days after I got my freerunner I started a long bicycle trip and had not find time to install dillo. On one of the first evenings I visited one or two pages. That was not so nice but bearable with the default browser really because I was not surfing very much (of course having dillo is much better). Some days later, I was abroad and I found one wifi hotspot. I had more applications open (at least my mapping program (with a hotspot list loaded) Starting the default browser has frozen the system. That is completely unbearable. In that situation having a browser with a lower ressource usage is essential. Greetings Andreas Kemnade

March 31, 2010

[jeffdewe@gmail.com: Dillo]

by jcid＠dillo.org

-- Cheers Jorge.-

March 31, 2010

patch: implement white-space: pre-wrap for vsource

by Johannes.Hofmann＠gmx.de

On Wed, Mar 31, 2010 at 12:02:16AM +0000, corvid wrote: > Jorge wrote: > > On Tue, Mar 30, 2010 at 09:57:08PM +0200, Johannes Hofmann wrote: > > > On Tue, Mar 30, 2010 at 06:00:26AM +0000, corvid wrote: > > > > Just a thought I had. The web is filled with horrible generated html > > > > with lines a thousand characters long. With this (and parse_embedded_css), > > > > those lines become more tolerable. > > > > > > Very nice! > > > > +1 > > > > I really dislike when emails with paragraphs in one line get > > under PRE. If this fixes that, I'm all for it! :) > > > > > > I would commit it in two pieces, of course. > > > > > > Please go ahead - at least for the CSS / dw part. I don't know > > > whether it's ok to use it for source view. > > > > AFAIS, there's no problem for source view. > > Committed the CSS/dw part. > > For vsource, I have no opinion on whether to use my original solution > or to add an id like Johannes mentioned. As Jorge is also ok with it, I'd say make it the default for source view. Additionally I will add the id, for customization in style.css.

March 31, 2010

patch: white-space: pre-line as well

by corvid＠lavabit.com

I don't know whether it's of much use, exactly, but while I was in the conceptual area...

March 31, 2010

patch: implement white-space: pre-wrap for vsource

by corvid＠lavabit.com

Jorge wrote: > On Tue, Mar 30, 2010 at 09:57:08PM +0200, Johannes Hofmann wrote: > > On Tue, Mar 30, 2010 at 06:00:26AM +0000, corvid wrote: > > > Just a thought I had. The web is filled with horrible generated html > > > with lines a thousand characters long. With this (and parse_embedded_css), > > > those lines become more tolerable. > > > > Very nice! > > +1 > > I really dislike when emails with paragraphs in one line get > under PRE. If this fixes that, I'm all for it! :) > > > > I would commit it in two pieces, of course. > > > > Please go ahead - at least for the CSS / dw part. I don't know > > whether it's ok to use it for source view. > > AFAIS, there's no problem for source view. Committed the CSS/dw part. For vsource, I have no opinion on whether to use my original solution or to add an id like Johannes mentioned.

March 31, 2010

HTML 2.0 DTDs

by jcid＠dillo.org

On Tue, Mar 30, 2010 at 08:37:16PM +0000, corvid wrote: > I just mistyped an address on our site, got a 404, and noticed that > I get an HTML bug msg about the DTD. > > The 404 page has: > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > > Html_parse_doctype has: > > static const char HTML20 [] = "-//IETF//DTD HTML//EN"; > > RFC 1866 has: > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Level 2//EN"> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN"> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Strict//EN"> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 1//EN"> > > So I would rather strncmp for "-//IETF//DTD HTML 2.0". +1 -- Cheers Jorge.-

March 31, 2010