- Dillo-dev - lists.mailman3.com

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

by jcid＠dillo.org

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. -- Cheers Jorge.-

March 31, 2010

Re: experiment feedback

by spell_gooder_now＠spellingbeewinnars.org

Hi Alan I had actually read quite a bit about seed and I had downloaded some sample code and played with it in the past. However your idea never occurred to me. I think it would be a fantastic idea to make the JavaScript within the layout engine talk to the "enclosing" GUI that is also written in JavaScript. I read through your blog, thanks for the link and your writings. I have been going around in circles for an amount of time I am too ashamed to confess. I have decided to write the back end and post pone the front end till I sort this out in my head. I would however still like to be a part of any project you might start related to this. I hope this won't come across the wrong way, I really like Dillo but I am wondering what is it's main niche it is planning to fill? Certainly it is fast and certainly it is small but is the target audience just people looking for a general purpose browser? Would it's speed and small size not make it ideal for being embedded in another application? Would this not be something that Gecko and Webkit cannot easily offer? I only have limited resources and time but I bet a corporate sponsor might fund this. Alan, I hope your studying goes well, sounds like someone else is sleep deprived too-Patrick

March 31, 2010

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

by Johannes.Hofmann＠gmx.de

On Tue, Mar 30, 2010 at 08:12:34PM +0000, corvid wrote: > Johannes 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! > > > > > > > > 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. > > I've read that it's in CSS 2.1 and 3, but not 1 or 2. > 2 is a "recommendation", but 2.1 is a "candidate recommendation". > > Are we aiming more in the direction of 2 or 2.1 (or their intersection)? I think we should go with 2.1. 2.1 fixes some shortcomings of 2, and 3 is still experimental - as far as I know.

March 30, 2010

HTML 2.0 DTDs

by corvid＠lavabit.com

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

March 30, 2010

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

by corvid＠lavabit.com

Johannes 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! > > > > > 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. I've read that it's in CSS 2.1 and 3, but not 1 or 2. 2 is a "recommendation", but 2.1 is a "candidate recommendation". Are we aiming more in the direction of 2 or 2.1 (or their intersection)?

March 30, 2010

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

by Johannes.Hofmann＠gmx.de

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! > > > > > 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. In any case we could add an id like this: <body id="dillo_sv"> to the source view page, so people can adjust it in style.css, e.g: body#dillo_sv pre {white-space: pre-wrap}

March 30, 2010

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

by Johannes.Hofmann＠gmx.de

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! > > 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. Cheers, Johannes

March 30, 2010

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

by corvid＠lavabit.com

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. I would commit it in two pieces, of course.

March 30, 2010

Problem using "Textblock" Class.

by Johannes.Hofmann＠gmx.de

On Fri, Mar 26, 2010 at 02:03:08AM +0000, corvid wrote: > Johannes wrote: <snip> > > > > Ok, I made a very rough patch to demonstrate the concept (see > > attachment). > > The main problem - apart from code style - is how to restore the > > original color of the link once anotherone has been selected. This > > is not working properly with this patch, but it's a start. > > Maybe the focused link can use a highlighting layer in Textblock > to show it in inverse video rather than dealing with html and link colors. That would be an easy alternative, but I'm investigating how much effort it would be to properly implement the CSS dynmic pseudo classes (:hover, :active, :focus). :focus basically defines how a selected element should look like. E.g: <html> <head> <style type="text/css"> :focus {border: 1px solid green} </style> </head> <body> <a href="foo">foo</a> <a href="bar">bar</a> </body> works in firefox and shows a green border around the currently selected link. With :active anything in the style can be changed, not just the colors.

March 26, 2010

Problem using "Textblock" Class.

by corvid＠lavabit.com

Johannes wrote: > On Thu, Mar 25, 2010 at 05:28:04PM +0100, Johannes Hofmann wrote: > > On Thu, Mar 25, 2010 at 03:56:31PM +0000, corvid wrote: > > > Johannes wrote: > > > > On Wed, Mar 24, 2010 at 04:49:09PM +0000, corvid wrote: > > > > > Johannes wrote: > > > > > > On Wed, Mar 24, 2010 at 02:34:13PM +0530, Rajesh Marathe wrote: > > > > > > > Hello Corvid, > > > > > > > > > > > > > > You hit the nail on its head. > > > > > > > I will definitely use iterators to iterate on the words on a page. I do have > > > > > > > the code with me which is based on findtext.cc as mentioned by Johannes. > > > > > > > But, using iterators I can move to a word on a page. But to get its style, I > > > > > > > still need to access the "x_link" variable which is in the class Textblock. > > > > > > > Therefore, my understanding was to use both iterator class and the Textblock > > > > > > > class as well. > > > > > > > > > > > > > > However, after seeing your email I get a feeling that my understanding might > > > > > > > be incorrect. > > > > > > > So, right now, my problem is not in using iterators (Which I intend to do > > > > > > > anyways) but getting the x_link variable which is in Textblock class. Please > > > > > > > let me know where am I wrong. > > > > > > > > > > > > Ah, I think I see your problem now. Iterators have the getContent() > > > > > > method, but Content does not include the style and therefore not the > > > > > > x_link. > > > > > > I'd say we should enhance the Iterator interface to make it possible > > > > > > to get the style somehow. However I don't know yet what would be the > > > > > > best way to do it. > > > > > > corvid, what do you think? > > > > > > > > > > Ah, in my earlier mail, I was imagining there being a getFocusable() in our > > > > > new iterator that gave back a Widget and a linkNo in the same way that the char > > > > > iterator has getChar(), but now I see that the base iterator already has a > > > > > getWidget(), so I guess we would just need a getLinkNo(). > > > > > > > > Right, either that, or a bit more general a getStyle() method, that > > > > would return the style at the current position (including x_link). > > > > > > Maybe. I don't think I have a strong opinion on 'general' vs. > > > 'unnecessary exposure' on this issue yet. > > > > Good point. Let's start with getLinkNo() and switch to getStyle() > > once we actually need another style member. > > Ok, I made a very rough patch to demonstrate the concept (see > attachment). > The main problem - apart from code style - is how to restore the > original color of the link once anotherone has been selected. This > is not working properly with this patch, but it's a start. Maybe the focused link can use a highlighting layer in Textblock to show it in inverse video rather than dealing with html and link colors.

March 26, 2010