- Dillo-dev - lists.mailman3.com

dillo 2.1]

by jcid＠dillo.org

On Mon, Jun 22, 2009 at 11:01:12PM +0300, Tomas Rimkus wrote: > > Accidentally sent to corvid only. Forwarding to dillo-dev. > > > > > It seems whoever designed the new website theme has no idea what > > > > READABILITY means... It looks like someone just used some stupid online > > > > color picker, which just picks some similar colors to the one user > > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > > regression... > > > > > > Hm I like the new design, but I agree that readability might be a problem. > > > Let's see what other say. > > > > I still find visited text to be hard to read, but I know I should > > break down and get a new display... > > > > I wonder if you are the only dillo user with old display... BTW, I am using > pretty new LCD display and still find it hard to read. OK, we also had readability concerns but we agreed that it was enough. OTOH some people bashed the old design as prehistoric! After all it's a matter of taste. Usability is a different thing. Maybe you need higher contrast to see clearly (I suffer with white backgrounds). Do you find this one better to read [1]? What do other people think about the new web design? Aesthetically and from a readability point of view. Please comment. [1] http://www.dillo.org/test/website/dillo2.2.html -- Cheers Jorge.-

June 24, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Thu, Jun 18, 2009 at 10:27:20AM +0200, Michal Nowak wrote: > On Wed, Jun 17, 2009 at 9:02 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > > [...] > > ?In a nutshell (from my point of view): > > > > ? * fltk2 is not officially released, and maybe never will. > > ? * dillo2 uses fltk2, and this creates pressure to package it. > > ? * Distros have a policy against statically-linked binaries. > > Definitely agree. The first and the second one can be somehow > sorted out and fltk2 pushed to distribution, the last one is blocker. > > [...] > You greatly outlined the problems with having Dillo-2 in distribution; > the problem is FLTK2. While watching at "changes" in FLTK2 snapshots > I can't thing that the development is stalled or even stopped. You surely refer to the 1.3 series because FLTK2 is quite stalled. e.g. (nov 2008 version against current) diff -pru fltk-2.0.x-r6525 fltk-2.0.x-r6786|less /* Only whitespace and an email address change here! */ FLTK-1.3 is the active one (a fact recognized by Bill Spitzak). > > I understand that my proposal won't be popular but switching from > FLTK2 is necessary - we hardly have FLTK2 in distributions (read: no > Dillo-2 in distribution) and that's shortening our user base. I agree on the shortened user base, but the proposal to switch to FLTK-1.3 is the probable course of action. > How hard it would be to rewrite/port Dillo-2 to FLTK-1.3? > > (I see that the speed of v1.3 development is nothing exciting, but > from what I read months ago they at least plan to have a release > ever.) This branch has advanced a lot. It has less open bugs than FLTK-2.0 [1], an active set of developers, and they've devoted plenty of time to good documentation. > While looking at the devel cycle of Dillo - two releases per year - > I believe this porting should be mid-term goal. Unless we wanna > spend another year out of mainstream distributions. (And frankly: > even with Dillo-2 based on FLTK-1.3 we are quite far from Dillo-2 > in distribution...) Some months ago I had long emails with FLTK developers regarding this point. FLTK-1.3 may have a release in the middle of 2009 and they may even consider a compatibility layer for FLTK-2.0 apps (for them, it would be a most appealing assset to have FLTK-2.0 apps. compile with FLTK-1.3 painlessly). Now, given the effort estimation by corvid, I'd go with a native port as soon as FLTK-1.3 is released (unless the compatibility layer is there, or porting turns out to be a major endeavour). If they succeed in an official release, chances are we'll have FLTK-1.3 in distros when we finish our port. BTW, their advice is to wait for the first release and then decide what to do. [1] http://fltk.org/roadmap.php -- Cheers Jorge.-

June 23, 2009

dillo 2.1

by jcid＠dillo.org

On Mon, Jun 22, 2009 at 05:24:28PM +0000, corvid wrote: > Johannes wrote: > > On Mon, Jun 22, 2009 at 05:12:07PM +0300, Tomas R wrote: > > > [...] > > > 6) http://www.binaryworld.skynet.lt/DUK.html > > > If we use one link with fragment identifier in the page, all the others > > > are marked as visited too. > > > > Not sure how this should be handled correctly. Someone will have to > > check the specs. > > I'm not aware of anything in the HTML spec on it, at least. Dillo shows pages already in memory in visited color. That way you can easily tell an in-memory link from one that's yet to be downloaded. This is very useful when switching from online to offline mode (e.g. dialup). IOW those links are rendered as visited because they're cached. In the same page (answers section), unvisited links are rendered as such. -- Cheers Jorge.-

June 23, 2009

Re: Dillo 2.1 questions

by jcid＠dillo.org

Hi, On Mon, Jun 22, 2009 at 02:33:51PM +0200, Donjan Rodic wrote: > Hello Jorge > > First off, Dillo 2.1 is awesome. It got exactly the features I hoped for Good! > and isn't noticably more resource hungry. In fact it has half the memory footprint of the dillo1 series. http://www.dillo.org/memory.html > Too bad it doesn't support column layouts in CSS yet... can we expect > this in the next release? I hope! The column layout problem is mainly a lack of implementation of floating elements in the textblock. it is one of the top priorities for the next release (if not the topmost). We'll work on it and try to fix it. We're yet to find out how much work it will be. > One thing I can't figure out are the available keybinding commands. For > example, how would I call "scroll-one-screen-up", which I'd like to bind > to <Shift>Space. Similar to how Space scrolls one screen down. > Also "open-link-in-new-tab" to <Ctrl>"left-mouse-click"... > I couldn't find any documentation on such commands, except for the keys > listed in .dillo/keysrc. You should have an installation-wide keysrc file along with dillorc. If not, just read http://www.dillo.org/keysrc. AFAIS, we haven't included that keybinding, but will probably exist in the source repository soon. Maybe: coarse-scroll-down, coarse-scroll-up, fine-scroll-down, fine-scroll-up > Another topic: is the adblock.txt in the .dillo folder supposed to work? > Is there any recent documentation on this? No, AFAIK it isn't in the release. I'd really like to have it in the next release though. -- Cheers Jorge.-

June 23, 2009

css font-size and nested tables

by Johannes.Hofmann＠gmx.de

On Tue, Jun 23, 2009 at 05:13:29PM +0300, Tomas R wrote: > On Tue, 23 Jun 2009 13:37:11 +0200 > Johannes Hofmann <Johannes.Hofmann(a)gmx.de> wrote: > > > Oh well. Just found this here: > > > > http://developer.mozilla.org/En/Fixing_Table_Inheritance_in_Quirks_Mode > > > > Not sure whether I want to do anything about it. > > Adding quirks in browsers just causes web developers to add quirks to > > fix them and so on... > > > > For now, as a workaround font_min_size could be set to 10-12 by > default (anything lower than 10 is unreadable), but not sure how this > will effect some websites, where text is intentionally hidden by > setting its size to negative or very low value. To simulate the behaviour of other browsers, you can add table, caption {font-size: medium} to your ~/.dillo/style.css for now. Maybe we should add this to the FAQ? Cheers, Johannes

June 23, 2009

css font-size and nested tables

by jcid＠dillo.org

On Tue, Jun 23, 2009 at 01:37:11PM +0200, Johannes Hofmann wrote: > Oh well. Just found this here: > > http://developer.mozilla.org/En/Fixing_Table_Inheritance_in_Quirks_Mode > > Not sure whether I want to do anything about it. > Adding quirks in browsers just causes web developers to add quirks to > fix them and so on... Well, it's a quirk... and we already have the font_min_size to tackle the problem. I'd prefer to focus our scarce development time into issues deemed high priority (e.g. the column rendering in textblock). -- Cheers Jorge.-

June 23, 2009

dillo 2.1

by sandshrew＠gmail.com

One more thing that I forgot to mention in the first message is text wrapping in textareas. By default unlike all the popular browsers dillo does not wrap text in textareas. Actually discussion about this was started in this mailing list some time ago but unexpectedly finished after corvid pointed out that according to the standards it's up to the browser to decide whether to wrap text or not. Maybe, if someone thinks it's better when text is not wrapped, this could be made optional? Would it be easy to implement this setting with fltk?

June 23, 2009

css font-size and nested tables

by sandshrew＠gmail.com

On Tue, 23 Jun 2009 13:37:11 +0200 Johannes Hofmann <Johannes.Hofmann(a)gmx.de> wrote: > Oh well. Just found this here: > > http://developer.mozilla.org/En/Fixing_Table_Inheritance_in_Quirks_Mode > > Not sure whether I want to do anything about it. > Adding quirks in browsers just causes web developers to add quirks to > fix them and so on... > For now, as a workaround font_min_size could be set to 10-12 by default (anything lower than 10 is unreadable), but not sure how this will effect some websites, where text is intentionally hidden by setting its size to negative or very low value.

June 23, 2009

css font-size and nested tables

by Johannes.Hofmann＠gmx.de

Oh well. Just found this here: http://developer.mozilla.org/En/Fixing_Table_Inheritance_in_Quirks_Mode Not sure whether I want to do anything about it. Adding quirks in browsers just causes web developers to add quirks to fix them and so on... Cheers, Johannes On Tue, Jun 23, 2009 at 01:16:05PM +0200, Johannes Hofmann wrote: > Hi, > > trying to find the reason for the tiny fonts in gmail, I found the > following: > > <html> > <head> > <style type="text/css"> > td {font-family: arial; font-size:50%} > </style> > </head> > <body> > > <table> > <tr> <td> foo bar </td> </tr> > <tr> <td> <table> <tr> <td>foo bar</td> </tr> </table> </td> </tr> > </table> > > </body> > </html> > > is rendered with the same font size in both lines in firefox, > konqueror, and opera. > Can someone enlighten me why the nested <td> does not decrease the > font size again in the second line? > > If I change the CSS to act on <table> instead of <td> it works as > expected. > > Cheers, > Johannes > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

June 23, 2009

css font-size and nested tables

by Johannes.Hofmann＠gmx.de

Hi, trying to find the reason for the tiny fonts in gmail, I found the following: <html> <head> <style type="text/css"> td {font-family: arial; font-size:50%} </style> </head> <body> <table> <tr> <td> foo bar </td> </tr> <tr> <td> <table> <tr> <td>foo bar</td> </tr> </table> </td> </tr> </table> </body> </html> is rendered with the same font size in both lines in firefox, konqueror, and opera. Can someone enlighten me why the nested <td> does not decrease the font size again in the second line? If I change the CSS to act on <table> instead of <td> it works as expected. Cheers, Johannes

June 23, 2009

dillo 2.1]

by sandshrew＠gmail.com

Accidentally sent to corvid only. Forwarding to dillo-dev. > > > It seems whoever designed the new website theme has no idea what > > > READABILITY means... It looks like someone just used some stupid online > > > color picker, which just picks some similar colors to the one user > > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > > regression... > > > > Hm I like the new design, but I agree that readability might be a problem. > > Let's see what other say. > > I still find visited text to be hard to read, but I know I should > break down and get a new display... > I wonder if you are the only dillo user with old display... BTW, I am using pretty new LCD display and still find it hard to read.

June 22, 2009

dillo 2.1

by Johannes.Hofmann＠gmx.de

On Mon, Jun 22, 2009 at 10:49:05PM +0300, Tomas Rimkus wrote: > > > UI > > > 1) Positioning the tab close button on the top RIGHT corner of the > > > browser isn't a good thing because: > > > a) The distance between the most commonly used buttons and the tab > > > close button is pretty big (especially when widescreen monitors are > > > pretty common nowadays); > > > b) It only allows closing the active tab; > > > I think it would be much better if all tabs had close buttons or at > > > least the button was placed near the last tab. > > > > Agreed. Patch welcome :) > > > > It seems this requires patching fltk -> http://www.mail-archive.com/fltk@easysw.com/msg05658.html This just means, that fltk does not support that out of the box. It would certainly be possible to implement it in dillo by overriding the default fltk tab drawing code. Cheers, Johannes

June 22, 2009

dillo 2.1

by sandshrew＠gmail.com

> > UI > > 1) Positioning the tab close button on the top RIGHT corner of the > > browser isn't a good thing because: > > a) The distance between the most commonly used buttons and the tab > > close button is pretty big (especially when widescreen monitors are > > pretty common nowadays); > > b) It only allows closing the active tab; > > I think it would be much better if all tabs had close buttons or at > > least the button was placed near the last tab. > > Agreed. Patch welcome :) > It seems this requires patching fltk -> http://www.mail-archive.com/fltk@easysw.com/msg05658.html

June 22, 2009

dillo 2.1

by corvid＠lavabit.com

I wrote: > Johannes wrote: > > On Mon, Jun 22, 2009 at 05:12:07PM +0300, Tomas R wrote: > > > 3) UPPERCASE letters should be used in the File menu to define keyboard > > > shortcuts, because now L looks like I (Open url... ctrl+l) > > I'll look into this. Hmm, I thought you were saying that this was new behaviour, but I see the old code worked that way as well. You give the shortcut to fltk and it draws it however it wants to draw it. Oh, maybe your UI font used to be a serif font... It is currently hardcoded to use font_sans_serif (the reason being that whatever default UI font fltk picked out for us was reasonably likely to have worse unicode coverage than the fonts we set in dillorc), but there has been talk of adding prefs for UI font and fontsize -- which I'd be willing to do.

June 22, 2009

dillo 2.1

by sandshrew＠gmail.com

On Mon, Jun 22, 2009 at 06:49:06PM +0200, Johannes Hofmann wrote: > Hi Tomas, > > On Mon, Jun 22, 2009 at 05:12:07PM +0300, Tomas R wrote: > > Been testing dillo 2.1 for some time and would like to share my > > experience. > > > > It's really great to see some basic css support (appearance of most if > > not all websites has improved alot), properly resized images, > > redirection and basic authentication working now :) > > > > Anyway, even dillo improved alot recently there still seems to be some > > issues. Here are some I've noticed after testing this release for few > > days: > > Rendering > > 1) ubuntu.lt > > Not sure if it's dillo fault or website's malformed stylesheet, but > > with default dillo settings some of the lithuanian characters are not > > displayed. This can be fixed by just adding "* {font-family: > > serif !important}" to the style.css. Here is a pic with some of the > > places where letters are missing marked in red: > > http://img4.imageshack.us/img4/2227/ubuntult.png > > I guess the problem is that the font simply does not contain those > glyphs. There are some rules how this case should be handled, but > dillo does not implement them currently. > I see. > > 2) gmail > > It's nice that login works now, but with default dillo settings the > > size of most of the text is 1px. This can be partially fixed by adding > > font_min_size to dillorc, but it's obviously a dillo bug as this > > doesn't happen with links-hacked. > > I don't have a gmail account, so I can't reproduce it, but > there seems to be a general bug in the CSS code that makes fonts > smaller than in other browsers. The account is just few clicks away ;) > > 3) google > > What's with the textarea in the top left corner of the page? And just > > for information: signing out doesn't work because it requires basic > > javascript support (works with links-hacked). > > That textarea is in the google page. It's just hidden due to a > "display: none" CSS directive which is not supported yet by dillo. > Actually I'd like to know the reason why it is there before > hiding it. > I guess, that's a honeypot for spambots. > > 4) Black on black, white on white... > > http://www.nma-fallout.com/forum/viewtopic.php?t=42776&start=2660&sid=a5712… > > For some reason black font color is used here and we get black text on > > black background in some posts (doesn't happen with links-hacked). > > Oh. This is just horrible HTML / CSS, it's full of bugs! > The reason for black on black is: > <body bgcolor="#000000" text="#C0C0C0" link="#33CC00" vlink="#33CC00" /> > > I.e. body is immediately closed. But there is tons of other bugs on > this page. I see. I'll try to contact the admin and see if I can fix some of the bugs. > > http://www.acetoneteam.org/ > > Background color is not set here and if we have "body > > {background-color: white}" rule in our style.css file, we get white > > text on white background. > > dillo does not handle color definitions of the form rgb(255,255,255) > yet. I guess we can fix that. > Sounds good :) > > 5) http://ubuntuforums.org/showthread.php?p=6592005 > > What's with the PINK blocks? If that's more of a "feature" then a bug, > > can the color be changed by using some css rule? > > I can't find pink blocks on that page. Where exactly do you see > them? Maybe post a screenshot. > Sure. Some of the blocks marked in red: http://img20.imageshack.us/img20/2749/ubuntuforums.png http://img20.imageshack.us/img20/6066/ubuntuforums1.png > > 6) http://www.binaryworld.skynet.lt/DUK.html > > If we use one link with fragment identifier in the page, all the others > > are marked as visited too. > > Not sure how this should be handled correctly. Someone will have to > check the specs. > I've checked opera, firefox, midori and chromium (aka google chrome under BSD license) browsers. None of them act like that. > > 7) Authentication > > Basic authentication does work now, but at first the server displays a > > message saying "wrong credentials or browser doesn't > > understand how to supply the credentials" and only then a window > > pops up asking for the credentials... > > > > UI > > 1) Positioning the tab close button on the top RIGHT corner of the > > browser isn't a good thing because: > > a) The distance between the most commonly used buttons and the tab > > close button is pretty big (especially when widescreen monitors are > > pretty common nowadays); > > b) It only allows closing the active tab; > > I think it would be much better if all tabs had close buttons or at > > least the button was placed near the last tab. > > Agreed. Patch welcome :) > > > 2) Trivial but... because the setting to enable/disable image loading > > now is in the wrench menu it is two clicks away instead of one as it > > used to be in dillo 2.0. Maybe css settings could be left where they are > > now, but the setting for enabling/disabling images could be moved where > > it was in dillo 2.0? > > 3) UPPERCASE letters should be used in the File menu to define keyboard > > shortcuts, because now L looks like I (Open url... ctrl+l) > > 4) Don't you think "Are you sure you want to close the browser?" > > message is pretty annoying? > > Which one exactly? When exiting dillo with multiple tabs/windows > open? > I don't think dillo asks a lot for confirmation, but I normally use > multiple Ctrl-q's to close all tabs and windows and quit. > Yup, the one with multiple tabs. I just use my WM's shortcut for closing the window. > > > > Other: > > It seems whoever designed the new website theme has no idea what > > READABILITY means... It looks like someone just used some stupid online > > color picker, which just picks some similar colors to the one user > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > regression... > > Hm I like the new design, but I agree that readability might be a problem. > Let's see what other say. > > > > > PS: how to install dillo 2.1 claws-mail plugin? > > Just install claws and the dillo plugin from source or packages > depending on your distribution. > Then make sure that dillo-2.1 is the dillo binary in your PATH. Ok, I'll try.

June 22, 2009

dillo 2.1

by corvid＠lavabit.com

Johannes wrote: > On Mon, Jun 22, 2009 at 05:12:07PM +0300, Tomas R wrote: > > 1) ubuntu.lt > > Not sure if it's dillo fault or website's malformed stylesheet, but > > with default dillo settings some of the lithuanian characters are not > > displayed. This can be fixed by just adding "* {font-family: > > serif !important}" to the style.css. Here is a pic with some of the > > places where letters are missing marked in red: > > http://img4.imageshack.us/img4/2227/ubuntult.png > > I guess the problem is that the font simply does not contain those > glyphs. There are some rules how this case should be handled, but > dillo does not implement them currently. Yeah, everything works for me because I have a real shortage of fonts, so 99.9999% of text is shown in DejaVu fonts. > > 6) http://www.binaryworld.skynet.lt/DUK.html > > If we use one link with fragment identifier in the page, all the others > > are marked as visited too. > > Not sure how this should be handled correctly. Someone will have to > check the specs. I'm not aware of anything in the HTML spec on it, at least. > > 3) UPPERCASE letters should be used in the File menu to define keyboard > > shortcuts, because now L looks like I (Open url... ctrl+l) I'll look into this. > > It seems whoever designed the new website theme has no idea what > > READABILITY means... It looks like someone just used some stupid online > > color picker, which just picks some similar colors to the one user > > chooses. The old website looked MUCH MUCH better. Imho, it's a > > regression... > > Hm I like the new design, but I agree that readability might be a problem. > Let's see what other say. I still find visited text to be hard to read, but I know I should break down and get a new display...

June 22, 2009

dillo 2.1

by Johannes.Hofmann＠gmx.de

Hi Tomas, On Mon, Jun 22, 2009 at 05:12:07PM +0300, Tomas R wrote: > Been testing dillo 2.1 for some time and would like to share my > experience. > > It's really great to see some basic css support (appearance of most if > not all websites has improved alot), properly resized images, > redirection and basic authentication working now :) > > Anyway, even dillo improved alot recently there still seems to be some > issues. Here are some I've noticed after testing this release for few > days: > Rendering > 1) ubuntu.lt > Not sure if it's dillo fault or website's malformed stylesheet, but > with default dillo settings some of the lithuanian characters are not > displayed. This can be fixed by just adding "* {font-family: > serif !important}" to the style.css. Here is a pic with some of the > places where letters are missing marked in red: > http://img4.imageshack.us/img4/2227/ubuntult.png I guess the problem is that the font simply does not contain those glyphs. There are some rules how this case should be handled, but dillo does not implement them currently. > 2) gmail > It's nice that login works now, but with default dillo settings the > size of most of the text is 1px. This can be partially fixed by adding > font_min_size to dillorc, but it's obviously a dillo bug as this > doesn't happen with links-hacked. I don't have a gmail account, so I can't reproduce it, but there seems to be a general bug in the CSS code that makes fonts smaller than in other browsers. > 3) google > What's with the textarea in the top left corner of the page? And just > for information: signing out doesn't work because it requires basic > javascript support (works with links-hacked). That textarea is in the google page. It's just hidden due to a "display: none" CSS directive which is not supported yet by dillo. Actually I'd like to know the reason why it is there before hiding it. > 4) Black on black, white on white... > http://www.nma-fallout.com/forum/viewtopic.php?t=42776&start=2660&sid=a5712… > For some reason black font color is used here and we get black text on > black background in some posts (doesn't happen with links-hacked). Oh. This is just horrible HTML / CSS, it's full of bugs! The reason for black on black is: <body bgcolor="#000000" text="#C0C0C0" link="#33CC00" vlink="#33CC00" /> I.e. body is immediately closed. But there is tons of other bugs on this page. > http://www.acetoneteam.org/ > Background color is not set here and if we have "body > {background-color: white}" rule in our style.css file, we get white > text on white background. dillo does not handle color definitions of the form rgb(255,255,255) yet. I guess we can fix that. > 5) http://ubuntuforums.org/showthread.php?p=6592005 > What's with the PINK blocks? If that's more of a "feature" then a bug, > can the color be changed by using some css rule? I can't find pink blocks on that page. Where exactly do you see them? Maybe post a screenshot. > 6) http://www.binaryworld.skynet.lt/DUK.html > If we use one link with fragment identifier in the page, all the others > are marked as visited too. Not sure how this should be handled correctly. Someone will have to check the specs. > 7) Authentication > Basic authentication does work now, but at first the server displays a > message saying "wrong credentials or browser doesn't > understand how to supply the credentials" and only then a window > pops up asking for the credentials... > > UI > 1) Positioning the tab close button on the top RIGHT corner of the > browser isn't a good thing because: > a) The distance between the most commonly used buttons and the tab > close button is pretty big (especially when widescreen monitors are > pretty common nowadays); > b) It only allows closing the active tab; > I think it would be much better if all tabs had close buttons or at > least the button was placed near the last tab. Agreed. Patch welcome :) > 2) Trivial but... because the setting to enable/disable image loading > now is in the wrench menu it is two clicks away instead of one as it > used to be in dillo 2.0. Maybe css settings could be left where they are > now, but the setting for enabling/disabling images could be moved where > it was in dillo 2.0? > 3) UPPERCASE letters should be used in the File menu to define keyboard > shortcuts, because now L looks like I (Open url... ctrl+l) > 4) Don't you think "Are you sure you want to close the browser?" > message is pretty annoying? Which one exactly? When exiting dillo with multiple tabs/windows open? I don't think dillo asks a lot for confirmation, but I normally use multiple Ctrl-q's to close all tabs and windows and quit. > > Other: > It seems whoever designed the new website theme has no idea what > READABILITY means... It looks like someone just used some stupid online > color picker, which just picks some similar colors to the one user > chooses. The old website looked MUCH MUCH better. Imho, it's a > regression... Hm I like the new design, but I agree that readability might be a problem. Let's see what other say. > > PS: how to install dillo 2.1 claws-mail plugin? Just install claws and the dillo plugin from source or packages depending on your distribution. Then make sure that dillo-2.1 is the dillo binary in your PATH. Cheers, Johannes

June 22, 2009

form widgets, ascent/descent

by jcid＠dillo.org

On Sun, Jun 21, 2009 at 08:36:48PM +0200, Johannes Hofmann wrote: > On Sun, Jun 21, 2009 at 05:47:34PM +0000, corvid wrote: > > Jorge wrote: > > > On Thu, Jun 04, 2009 at 06:11:43PM +0000, corvid wrote: > > > > I was playing around in dw, and noticed that, > > > > whereas form widgets normally like to put > > > > much of their height into descent, when style > > > > sets the height, Textblock::calcWidgetSize() > > > > puts it all into ascent. > > > > > > > > I checked firefox and saw that their form widgets ascend. > > > > > > > > If we made everything ascend and just put font->descent > > > > into the descent, it would make life simpler. > > > > Or, nearly. I guess there is RELIEF_Y_THICKNESS, but I > > > > could almost ignore that... > > > > > > Not knowing exactly about the details, I'd be very careful > > > in changing ascents, descents and friends because the may > > > interfere with correct handling of CSS. > > > > > > If you're sure it's OK to do it, even considering the "details" > > > (e.g. reliefs, spacings, paddings), then why not. > > > > Our details when it comes to form controls don't seem to be > > exactly right to begin with, so I'm not making anything worse. > > Little patch: > > > diff -r 9a913c474271 dw/fltkui.cc > > --- a/dw/fltkui.cc Sun Jun 21 12:19:13 2009 -0400 > > +++ b/dw/fltkui.cc Sun Jun 21 17:22:14 2009 +0000 > > @@ -697,10 +697,10 @@ void FltkMultiLineTextResource::sizeRequ > > (int)::fltk::getwidth ("n", 1) * numCols + > > 2 * RELIEF_X_THICKNESS; > > requisition->ascent = > > - font->ascent + RELIEF_Y_THICKNESS; > > + RELIEF_Y_THICKNESS + font->ascent + > > + (font->ascent + font->descent) * (numRows - 1); > > requisition->descent = > > font->descent + > > - (font->ascent + font->descent) * (numRows - 1) + > > RELIEF_Y_THICKNESS; > > } else { > > requisition->width = 1; > > @@ -1310,9 +1310,9 @@ void FltkListResource::sizeRequest (core > > * options, at the cost of showing too much whitespace at times. > > */ > > requisition->width = getMaxStringWidth() + 24; > > - requisition->ascent = font->ascent + 2; > > - requisition->descent = font->descent + 3 + > > - (rows - 1) * (font->ascent + font->descent + 1); > > + requisition->ascent = font->ascent + 2 + > > + (rows - 1) * (font->ascent + font->descent + 1); > > + requisition->descent = font->descent + 3; > > } else { > > requisition->width = 1; > > requisition->ascent = 1; > > +1 from me. > I can't see why this was handled different before. > OK, please commit. -- Cheers Jorge.-

June 22, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Mon, Jun 22, 2009 at 02:32:11PM +0200, Michal Nowak wrote: > On Sat, Jun 20, 2009 at 3:51 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > > On Fri, Jun 19, 2009 at 07:20:35PM -0400, Jorge Arellano Cid wrote: > >> On Fri, Jun 19, 2009 at 01:44:52PM -0400, Jorge Arellano Cid wrote: > >> > On Thu, Jun 18, 2009 at 10:29:06PM -0400, Jorge Arellano Cid wrote: > >> > > [...] > >> > > ? WARNING: Please don't make the packages yet, I've got a last minute > >> > > security vulnerability email, so maybe the tarball will change > >> > > once more (the last). I'll try to have this solved tomorrow in the > >> > > morning. > >> > > >> > ? OK, the last tarball was just uploaded (rc3) and it will > >> > be announced tomorrow in the morning. It has a patch > >> > for malformed PNG images. > >> > > >> > ? Please make the respective packages and let me know > >> > when ready to link them from the downloads page. > >> > >> ? BTW, the announcement will be on Saturday 20's morning > >> (UTC - 4). So there's still some time to finish the packages. > >> Please make sure you have the last tarball by checking the > >> signature, and let me know to update the linking page. > > > > > > ?OK, the dillo-2.1 release announcement was submitted > > to freshmeat and the download page updated with the URLs > > of the latest packages. > > > > ?AFAIS everything is OK. Now I have to go out so if there's > > something missing in the website, please let Corvid or Johannes > > know here in dillo-dev. > > > > ?Great, let's hope for a good reception! > > > > -- > > ?Cheers > > ?Jorge.- > > > > _______________________________________________ > > Dillo-dev mailing list > > Dillo-dev(a)dillo.org > > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > > > > FYI > > Static Fedora-11 i586 & x86-64 packages: > > http://mnowak.fedorapeople.org/dillo2/static/F-11/ Good. It's linked from the downloads page. -- Cheers Jorge.-

June 22, 2009

trimming system includes

by jcid＠dillo.org

On Mon, Jun 22, 2009 at 02:02:28PM +0000, corvid wrote: > Johannes wrote: > > On Mon, Jun 22, 2009 at 02:08:01AM +0000, corvid wrote: > > > Johannes wrote: > > > > I'm all for it and will be happy to test it on DragonFly BSD. > > > > > > Does this come reasonably close to compiling? > > > > Works just fine here. > > Well, if it works for Johannes... :) Good. Please commit so people can test from the repo. > Anyway, I looked through the cvs archive a little, and it was interesting > to see the prehistoric origins of some of this stuff, dating as far back > as gzilla presumably. One is unavoidably reminded of how a living thing > today bears the mark of billions of years of evolutionary past. Maybe the original designers didn't have enough time to remove or polish the rough edges, henceforth leaving the hybrid creature on its own to do the job! :-) -- Cheers Jorge.-

June 22, 2009

dillo 2.1

by sandshrew＠gmail.com

Been testing dillo 2.1 for some time and would like to share my experience. It's really great to see some basic css support (appearance of most if not all websites has improved alot), properly resized images, redirection and basic authentication working now :) Anyway, even dillo improved alot recently there still seems to be some issues. Here are some I've noticed after testing this release for few days: Rendering 1) ubuntu.lt Not sure if it's dillo fault or website's malformed stylesheet, but with default dillo settings some of the lithuanian characters are not displayed. This can be fixed by just adding "* {font-family: serif !important}" to the style.css. Here is a pic with some of the places where letters are missing marked in red: http://img4.imageshack.us/img4/2227/ubuntult.png 2) gmail It's nice that login works now, but with default dillo settings the size of most of the text is 1px. This can be partially fixed by adding font_min_size to dillorc, but it's obviously a dillo bug as this doesn't happen with links-hacked. 3) google What's with the textarea in the top left corner of the page? And just for information: signing out doesn't work because it requires basic javascript support (works with links-hacked). 4) Black on black, white on white... http://www.nma-fallout.com/forum/viewtopic.php?t=42776&start=2660&sid=a5712… For some reason black font color is used here and we get black text on black background in some posts (doesn't happen with links-hacked). http://www.acetoneteam.org/ Background color is not set here and if we have "body {background-color: white}" rule in our style.css file, we get white text on white background. 5) http://ubuntuforums.org/showthread.php?p=6592005 What's with the PINK blocks? If that's more of a "feature" then a bug, can the color be changed by using some css rule? 6) http://www.binaryworld.skynet.lt/DUK.html If we use one link with fragment identifier in the page, all the others are marked as visited too. 7) Authentication Basic authentication does work now, but at first the server displays a message saying "wrong credentials or browser doesn't understand how to supply the credentials" and only then a window pops up asking for the credentials... UI 1) Positioning the tab close button on the top RIGHT corner of the browser isn't a good thing because: a) The distance between the most commonly used buttons and the tab close button is pretty big (especially when widescreen monitors are pretty common nowadays); b) It only allows closing the active tab; I think it would be much better if all tabs had close buttons or at least the button was placed near the last tab. 2) Trivial but... because the setting to enable/disable image loading now is in the wrench menu it is two clicks away instead of one as it used to be in dillo 2.0. Maybe css settings could be left where they are now, but the setting for enabling/disabling images could be moved where it was in dillo 2.0? 3) UPPERCASE letters should be used in the File menu to define keyboard shortcuts, because now L looks like I (Open url... ctrl+l) 4) Don't you think "Are you sure you want to close the browser?" message is pretty annoying? Other: It seems whoever designed the new website theme has no idea what READABILITY means... It looks like someone just used some stupid online color picker, which just picks some similar colors to the one user chooses. The old website looked MUCH MUCH better. Imho, it's a regression... PS: how to install dillo 2.1 claws-mail plugin? -- Brain: an apparatus with which we think we think. - A. Bierce

June 22, 2009

trimming system includes

by corvid＠lavabit.com

Johannes wrote: > On Mon, Jun 22, 2009 at 02:08:01AM +0000, corvid wrote: > > Johannes wrote: > > > I'm all for it and will be happy to test it on DragonFly BSD. > > > > Does this come reasonably close to compiling? > > Works just fine here. Well, if it works for Johannes... :) Anyway, I looked through the cvs archive a little, and it was interesting to see the prehistoric origins of some of this stuff, dating as far back as gzilla presumably. One is unavoidably reminded of how a living thing today bears the mark of billions of years of evolutionary past.

June 22, 2009

dillo-2.1.tar.bz2

by newman.x＠gmail.com

On Sat, Jun 20, 2009 at 3:51 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > On Fri, Jun 19, 2009 at 07:20:35PM -0400, Jorge Arellano Cid wrote: >> On Fri, Jun 19, 2009 at 01:44:52PM -0400, Jorge Arellano Cid wrote: >> > On Thu, Jun 18, 2009 at 10:29:06PM -0400, Jorge Arellano Cid wrote: >> > > [...] >> > > ? WARNING: Please don't make the packages yet, I've got a last minute >> > > security vulnerability email, so maybe the tarball will change >> > > once more (the last). I'll try to have this solved tomorrow in the >> > > morning. >> > >> > ? OK, the last tarball was just uploaded (rc3) and it will >> > be announced tomorrow in the morning. It has a patch >> > for malformed PNG images. >> > >> > ? Please make the respective packages and let me know >> > when ready to link them from the downloads page. >> >> ? BTW, the announcement will be on Saturday 20's morning >> (UTC - 4). So there's still some time to finish the packages. >> Please make sure you have the last tarball by checking the >> signature, and let me know to update the linking page. > > > ?OK, the dillo-2.1 release announcement was submitted > to freshmeat and the download page updated with the URLs > of the latest packages. > > ?AFAIS everything is OK. Now I have to go out so if there's > something missing in the website, please let Corvid or Johannes > know here in dillo-dev. > > ?Great, let's hope for a good reception! > > -- > ?Cheers > ?Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > FYI Static Fedora-11 i586 & x86-64 packages: http://mnowak.fedorapeople.org/dillo2/static/F-11/ Michal

June 22, 2009

form widgets, ascent/descent

by Johannes.Hofmann＠gmx.de

On Sun, Jun 21, 2009 at 05:47:34PM +0000, corvid wrote: > Jorge wrote: > > On Thu, Jun 04, 2009 at 06:11:43PM +0000, corvid wrote: > > > I was playing around in dw, and noticed that, > > > whereas form widgets normally like to put > > > much of their height into descent, when style > > > sets the height, Textblock::calcWidgetSize() > > > puts it all into ascent. > > > > > > I checked firefox and saw that their form widgets ascend. > > > > > > If we made everything ascend and just put font->descent > > > into the descent, it would make life simpler. > > > Or, nearly. I guess there is RELIEF_Y_THICKNESS, but I > > > could almost ignore that... > > > > Not knowing exactly about the details, I'd be very careful > > in changing ascents, descents and friends because the may > > interfere with correct handling of CSS. > > > > If you're sure it's OK to do it, even considering the "details" > > (e.g. reliefs, spacings, paddings), then why not. > > Our details when it comes to form controls don't seem to be > exactly right to begin with, so I'm not making anything worse. > Little patch: > diff -r 9a913c474271 dw/fltkui.cc > --- a/dw/fltkui.cc Sun Jun 21 12:19:13 2009 -0400 > +++ b/dw/fltkui.cc Sun Jun 21 17:22:14 2009 +0000 > @@ -697,10 +697,10 @@ void FltkMultiLineTextResource::sizeRequ > (int)::fltk::getwidth ("n", 1) * numCols + > 2 * RELIEF_X_THICKNESS; > requisition->ascent = > - font->ascent + RELIEF_Y_THICKNESS; > + RELIEF_Y_THICKNESS + font->ascent + > + (font->ascent + font->descent) * (numRows - 1); > requisition->descent = > font->descent + > - (font->ascent + font->descent) * (numRows - 1) + > RELIEF_Y_THICKNESS; > } else { > requisition->width = 1; > @@ -1310,9 +1310,9 @@ void FltkListResource::sizeRequest (core > * options, at the cost of showing too much whitespace at times. > */ > requisition->width = getMaxStringWidth() + 24; > - requisition->ascent = font->ascent + 2; > - requisition->descent = font->descent + 3 + > - (rows - 1) * (font->ascent + font->descent + 1); > + requisition->ascent = font->ascent + 2 + > + (rows - 1) * (font->ascent + font->descent + 1); > + requisition->descent = font->descent + 3; > } else { > requisition->width = 1; > requisition->ascent = 1; +1 from me. I can't see why this was handled different before. Cheers, Johannes

June 21, 2009

trimming system includes

by corvid＠lavabit.com

Johannes wrote: > On Sun, Jun 21, 2009 at 12:08:06PM -0400, Jorge Arellano Cid wrote: > > On Sat, Jun 20, 2009 at 03:39:56PM +0000, corvid wrote: > > > Would anyone have strong objections if I go through > > > and make some patches to remove system includes where > > > I can't see any evidence that any code now in that file > > > still needs that header? > > > > OK, but please test is still works on the different > > platforms. > > I'm all for it and will be happy to test it on DragonFly BSD. Oh, good, because I was looking around at my extensive collection of...one computer...that I can't easily put OSes on, thinking, "Well, so much for that idea..."

June 21, 2009

form widgets, ascent/descent

by corvid＠lavabit.com

Jorge wrote: > On Thu, Jun 04, 2009 at 06:11:43PM +0000, corvid wrote: > > I was playing around in dw, and noticed that, > > whereas form widgets normally like to put > > much of their height into descent, when style > > sets the height, Textblock::calcWidgetSize() > > puts it all into ascent. > > > > I checked firefox and saw that their form widgets ascend. > > > > If we made everything ascend and just put font->descent > > into the descent, it would make life simpler. > > Or, nearly. I guess there is RELIEF_Y_THICKNESS, but I > > could almost ignore that... > > Not knowing exactly about the details, I'd be very careful > in changing ascents, descents and friends because the may > interfere with correct handling of CSS. > > If you're sure it's OK to do it, even considering the "details" > (e.g. reliefs, spacings, paddings), then why not. Our details when it comes to form controls don't seem to be exactly right to begin with, so I'm not making anything worse. Little patch:

June 21, 2009

trimming system includes

by Johannes.Hofmann＠gmx.de

On Sun, Jun 21, 2009 at 12:08:06PM -0400, Jorge Arellano Cid wrote: > On Sat, Jun 20, 2009 at 03:39:56PM +0000, corvid wrote: > > Would anyone have strong objections if I go through > > and make some patches to remove system includes where > > I can't see any evidence that any code now in that file > > still needs that header? > > OK, but please test is still works on the different > platforms. I'm all for it and will be happy to test it on DragonFly BSD. Cheers, Johannes

June 21, 2009

trimming system includes

by jcid＠dillo.org

On Sat, Jun 20, 2009 at 03:39:56PM +0000, corvid wrote: > Would anyone have strong objections if I go through > and make some patches to remove system includes where > I can't see any evidence that any code now in that file > still needs that header? OK, but please test is still works on the different platforms. -- Cheers Jorge.-

June 21, 2009

trimming system includes

by corvid＠lavabit.com

Would anyone have strong objections if I go through and make some patches to remove system includes where I can't see any evidence that any code now in that file still needs that header?

June 20, 2009

experimental patch: nowrap

by corvid＠lavabit.com

Currently dillo does not handle the case where certain regions of a line can be wrapped and other regions cannot. A prominent example is the list of browsers at the bottom of http://en.wikipedia.org/wiki/Dillo Here is a patch that minimizes memory use (adds one int per textblock) at some cost of recalculating things http://www.dillo.org/test/nowrap.patch When whitespace isn't WHITE_SPACE_NORMAL, Textblock::add* functions still add words to the word list, but postpone wrapping until the entire nowrap/pre chunk has been added or a break has been seen. This is so that we know whether to put it all on a new line. Some possibilities: Putting some kind of spanWidth in each Word, calculating it in addNowrapWords and sticking this nonzero value into the beginning word. We'd have to remember to deal with it if things in the span changed size, or if dillo got on-the-fly display:none someday or whatever. Taking the time to stick the whole chunk into one word when the style is all the same. (Similar difficulties as the above.) I'm not sure whether that would make life more difficult if dillo got bidirectional text someday. Putting the nowrap Words into a Something, so that what is now a Word list would contain Word Word Word Something Word Something Word... That sounds complicated. Let the add* functions put the nowrap Words through wordWrap, and keep track of shifts between normal/nowrap in a line. When a line is completed, set up rewrap to do it over. This would be in an effort to "push down the bubble" of ickiness around add*/addNowrapWords/rewrap, although the resulting new bubble of ickiness that would pop up next to it would perhaps be similar. Small things that might or might not be improvements: make breaks have normal whitespace, and make lines with only one word have normal whitespace (text/plain).

June 20, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Fri, Jun 19, 2009 at 07:20:35PM -0400, Jorge Arellano Cid wrote: > On Fri, Jun 19, 2009 at 01:44:52PM -0400, Jorge Arellano Cid wrote: > > On Thu, Jun 18, 2009 at 10:29:06PM -0400, Jorge Arellano Cid wrote: > > > [...] > > > WARNING: Please don't make the packages yet, I've got a last minute > > > security vulnerability email, so maybe the tarball will change > > > once more (the last). I'll try to have this solved tomorrow in the > > > morning. > > > > OK, the last tarball was just uploaded (rc3) and it will > > be announced tomorrow in the morning. It has a patch > > for malformed PNG images. > > > > Please make the respective packages and let me know > > when ready to link them from the downloads page. > > BTW, the announcement will be on Saturday 20's morning > (UTC - 4). So there's still some time to finish the packages. > Please make sure you have the last tarball by checking the > signature, and let me know to update the linking page. OK, the dillo-2.1 release announcement was submitted to freshmeat and the download page updated with the URLs of the latest packages. AFAIS everything is OK. Now I have to go out so if there's something missing in the website, please let Corvid or Johannes know here in dillo-dev. Great, let's hope for a good reception! -- Cheers Jorge.-

June 20, 2009

dillo-2.1.tar.bz2

by sas＠321.hu

On Sat, Jun 20, 2009 at 2:56 PM, Devid Antonio Filoni <devidfil(a)gmail.com>wrote: > find the Debian packages at the following links: > Dillo: https://launchpad.net/~d.filoni/+archive/dillo<https://launchpad.net/%7Ed.filoni/+archive/dillo> > Dillo+SSL: https://launchpad.net/~d.filoni/+archive/dillo+ssl<https://launchpad.net/%7Ed.filoni/+archive/dillo+ssl> just for sid, not lenny/squeeze: depends on libxi6 1.2 http://packages.debian.org/search?keywords=libxi6 -- SZERV?C Attila - zeneszerz? http://google.com/search?q=szerv?c <http://google.com/search?q=szerv%C3%A1c>

June 20, 2009

dillo-2.1.tar.bz2

by devidfil＠gmail.com

On Sat, Jun 20, 2009 at 8:03 AM, Kelson Vibber<kelson(a)pobox.com> wrote: >> ?BTW, the announcement will be on Saturday 20's morning >> (UTC - 4). So there's still some time to finish the packages. >> Please make sure you have the last tarball by checking the >> signature, and let me know to update the linking page. > > Sorry, I got mixed up over the timezone, or I would have posted the packages > that were ready earlier instead of waiting until they were all done. > > I have RPMS for both Fedora 10 (both 32 and 64-bit), RHEL 3 (32bit), RHEL4 > (64bit) and RHEL5 (32 and 64 bit), with and without SSL except for RHEL3. > > Location: > http://www.hyperborea.org/software/dillo/ Sorry for the delay, my internet connection sucks, however you can find the Debian packages at the following links: Dillo: https://launchpad.net/~d.filoni/+archive/dillo Dillo+SSL: https://launchpad.net/~d.filoni/+archive/dillo+ssl Devid > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

June 20, 2009

dillo-2.1.tar.bz2

by kelson＠pobox.com

> BTW, the announcement will be on Saturday 20's morning > (UTC - 4). So there's still some time to finish the packages. > Please make sure you have the last tarball by checking the > signature, and let me know to update the linking page. Sorry, I got mixed up over the timezone, or I would have posted the packages that were ready earlier instead of waiting until they were all done. I have RPMS for both Fedora 10 (both 32 and 64-bit), RHEL 3 (32bit), RHEL4 (64bit) and RHEL5 (32 and 64 bit), with and without SSL except for RHEL3. Location: http://www.hyperborea.org/software/dillo/

June 20, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Fri, Jun 19, 2009 at 01:44:52PM -0400, Jorge Arellano Cid wrote: > On Thu, Jun 18, 2009 at 10:29:06PM -0400, Jorge Arellano Cid wrote: > > [...] > > WARNING: Please don't make the packages yet, I've got a last minute > > security vulnerability email, so maybe the tarball will change > > once more (the last). I'll try to have this solved tomorrow in the > > morning. > > OK, the last tarball was just uploaded (rc3) and it will > be announced tomorrow in the morning. It has a patch > for malformed PNG images. > > Please make the respective packages and let me know > when ready to link them from the downloads page. BTW, the announcement will be on Saturday 20's morning (UTC - 4). So there's still some time to finish the packages. Please make sure you have the last tarball by checking the signature, and let me know to update the linking page. TIA. -- Cheers Jorge.-

June 20, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Thu, Jun 18, 2009 at 10:29:06PM -0400, Jorge Arellano Cid wrote: > [...] > WARNING: Please don't make the packages yet, I've got a last minute > security vulnerability email, so maybe the tarball will change > once more (the last). I'll try to have this solved tomorrow in the > morning. OK, the last tarball was just uploaded (rc3) and it will be announced tomorrow in the morning. It has a patch for malformed PNG images. Please make the respective packages and let me know when ready to link them from the downloads page. Here we go! -- Cheers Jorge.-

June 19, 2009

dillo-2.1.tar.bz2

by newman.x＠gmail.com

On Fri, Jun 19, 2009 at 4:29 AM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > On Thu, Jun 18, 2009 at 11:20:51PM +0200, Michal Nowak wrote: >> On Thu, Jun 18, 2009 at 9:56 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: >> > Hi, >> > >> > ?Working on >> > >> > ? ?2.- To enable-ssl or not enable-ssl (define what to do). >> > >> > >> > On Thu, Jun 18, 2009 at 10:36:39AM +0200, Michal Nowak wrote: >> >> [...] >> >> Generally speaking for Fedora, we won't turn on options which are not >> >> turned on by default in upstream - it usually brings divergence from >> >> upstream and comments in upstream mailing lists (not this one :) ) >> >> like: "That poor distroX turned on --enable-coolness so we are not >> >> supporting users of this distro at all." >> >> >> >> Turning on SSL in upstream means more pressure for fixing it, usually >> >> :). But I am reading dillo-dev long enough to know it's not that easy. >> >> [snip] >> >> > >> > ?Obviously the safe option is not to offer ssl-enabled packages, >> > but that will mainly have the effect of no https-dpi at all. >> > >> > ?I'm not quite sure which one would be best. >> > ?Comments? >> >> http://mnowak.fedorapeople.org/dillo2/static/ > > ?Good! > >> Looks like Kelson's having some problems with building, so I >> patched-rebuilt-installed Kelson's static FLTK2 SRPM and rebuilt >> Dillo2. Now there are present i586 pkgs for F-11, both SSL on/off, > > ?BTW, is there a special instruction to install them on RPM > systems? I mean something like adding a line to /etc/apt/sources.list > in Debian. > > >> tomorrow I can build x86-64 pkgs for F-11 at work. And i386 >> packs for F-10 (hopefully there's still the F-10 beast in KVM). > > > ?WARNING: Please don't make the packages yet, I've got a last minute > security vulnerability email, so maybe the tarball will change > once more (the last). I'll try to have this solved tomorrow in the > morning. > > >> (But treat them as third party ones, don't trust them :). ) > > ?What do you mean? The point was that the packages are not signed, nor verified by independent authority [1]: just wanna to ask you *not* have the packages in the dillo.org web page directly but only as a separate link to third party directory/repository. -- [1] Just created by me with the best effort. > > -- > ?Cheers > ?Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

June 19, 2009

dillo-2.1.tar.bz2

by newman.x＠gmail.com

On Fri, Jun 19, 2009 at 4:43 AM, Kelson Vibber<kelson(a)pobox.com> wrote: > On Jun 18, 2009, at 7:23 PM, Jorge Arellano Cid wrote: >> >> I'd prefer to have both and to offer as an option from the >> download page (as with Fedora). > > So just to confirm, two dillo packages per OS version / architecture > combination, one compiled with SSL, one compiled without? > >> ?WARNING: Please don't make the packages yet, I've got a last minute >> security vulnerability email, so maybe the tarball will change >> once more (the last). I'll try to have this solved tomorrow in the >> morning. > > Okay, I'll wait until tomorrow before building anything else. > > The good news is I finally got Fedora 10 i686 running from a USB key, and > was able to build the current package! > > So tomorrow I'll be able to build: > Fedora 10 i686 and x86_64 > RHEL 3 i386 > RHEL 4 x86_64 > RHEL 5 i686 and x86_64 Just a comment: I'll be out for the whole weekend, if there's demand for Fedora 11 packages I'll create them Sunday evening or Monday morning. > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

June 19, 2009

dillo-2.1.tar.bz2

by newman.x＠gmail.com

On Fri, Jun 19, 2009 at 4:55 AM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > On Thu, Jun 18, 2009 at 07:43:15PM -0700, Kelson Vibber wrote: >> On Jun 18, 2009, at 7:23 PM, Jorge Arellano Cid wrote: >>> I'd prefer to have both and to offer as an option from the >>> download page (as with Fedora). >> >> So just to confirm, two dillo packages per OS version / architecture >> combination, one compiled with SSL, one compiled without? > > ?That's the idea. Starting with the most used ones. > > >>> ?WARNING: Please don't make the packages yet, I've got a last minute >>> security vulnerability email, so maybe the tarball will change >>> once more (the last). I'll try to have this solved tomorrow in the >>> morning. >> >> Okay, I'll wait until tomorrow before building anything else. >> >> The good news is I finally got Fedora 10 i686 running from a USB key, >> and was able to build the current package! >> >> So tomorrow I'll be able to build: >> Fedora 10 i686 and x86_64 >> RHEL 3 i386 >> RHEL 4 x86_64 >> RHEL 5 i686 and x86_64 > > ?BTW, which is the easier way to install an rpm? > Just download and "rpm -ivh <PKG>" or is there a ppa-like thing? > It's not that hard to create a repository with RPM packages but as I said it's generally bad thing to encourage users to use this as "repository", they would expect the same service like from general distribution distro (e.g. security fixes), which we don't wanna provide - because we believe Dillo2 in official distribution is The way. The `rpm -ivh <pkg>` is easy enough, I believe. > -- > ?Cheers > ?Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

June 19, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Thu, Jun 18, 2009 at 07:43:15PM -0700, Kelson Vibber wrote: > On Jun 18, 2009, at 7:23 PM, Jorge Arellano Cid wrote: >> I'd prefer to have both and to offer as an option from the >> download page (as with Fedora). > > So just to confirm, two dillo packages per OS version / architecture > combination, one compiled with SSL, one compiled without? That's the idea. Starting with the most used ones. >> WARNING: Please don't make the packages yet, I've got a last minute >> security vulnerability email, so maybe the tarball will change >> once more (the last). I'll try to have this solved tomorrow in the >> morning. > > Okay, I'll wait until tomorrow before building anything else. > > The good news is I finally got Fedora 10 i686 running from a USB key, > and was able to build the current package! > > So tomorrow I'll be able to build: > Fedora 10 i686 and x86_64 > RHEL 3 i386 > RHEL 4 x86_64 > RHEL 5 i686 and x86_64 BTW, which is the easier way to install an rpm? Just download and "rpm -ivh <PKG>" or is there a ppa-like thing? -- Cheers Jorge.-

June 19, 2009

dillo-2.1.tar.bz2

by kelson＠pobox.com

On Jun 18, 2009, at 7:23 PM, Jorge Arellano Cid wrote: > I'd prefer to have both and to offer as an option from the > download page (as with Fedora). So just to confirm, two dillo packages per OS version / architecture combination, one compiled with SSL, one compiled without? > WARNING: Please don't make the packages yet, I've got a last minute > security vulnerability email, so maybe the tarball will change > once more (the last). I'll try to have this solved tomorrow in the > morning. Okay, I'll wait until tomorrow before building anything else. The good news is I finally got Fedora 10 i686 running from a USB key, and was able to build the current package! So tomorrow I'll be able to build: Fedora 10 i686 and x86_64 RHEL 3 i386 RHEL 4 x86_64 RHEL 5 i686 and x86_64

June 19, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Thu, Jun 18, 2009 at 11:20:51PM +0200, Michal Nowak wrote: > On Thu, Jun 18, 2009 at 9:56 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > > Hi, > > > > ?Working on > > > > ? ?2.- To enable-ssl or not enable-ssl (define what to do). > > > > > > On Thu, Jun 18, 2009 at 10:36:39AM +0200, Michal Nowak wrote: > >> [...] > >> Generally speaking for Fedora, we won't turn on options which are not > >> turned on by default in upstream - it usually brings divergence from > >> upstream and comments in upstream mailing lists (not this one :) ) > >> like: "That poor distroX turned on --enable-coolness so we are not > >> supporting users of this distro at all." > >> > >> Turning on SSL in upstream means more pressure for fixing it, usually > >> :). But I am reading dillo-dev long enough to know it's not that easy. > > [snip] > > > > > ?Obviously the safe option is not to offer ssl-enabled packages, > > but that will mainly have the effect of no https-dpi at all. > > > > ?I'm not quite sure which one would be best. > > ?Comments? > > http://mnowak.fedorapeople.org/dillo2/static/ Good! > Looks like Kelson's having some problems with building, so I > patched-rebuilt-installed Kelson's static FLTK2 SRPM and rebuilt > Dillo2. Now there are present i586 pkgs for F-11, both SSL on/off, BTW, is there a special instruction to install them on RPM systems? I mean something like adding a line to /etc/apt/sources.list in Debian. > tomorrow I can build x86-64 pkgs for F-11 at work. And i386 > packs for F-10 (hopefully there's still the F-10 beast in KVM). WARNING: Please don't make the packages yet, I've got a last minute security vulnerability email, so maybe the tarball will change once more (the last). I'll try to have this solved tomorrow in the morning. > (But treat them as third party ones, don't trust them :). ) What do you mean? -- Cheers Jorge.-

June 19, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Thu, Jun 18, 2009 at 11:12:12PM +0200, Devid Antonio Filoni wrote: > In Debian, the package in the repo is built with ssl enabled, I prefer > to have the new package with ssl too. Is possible to just show a > warning opening dillo? Yes it is. You can add a warning in the splash page with HTML. Just try making some changes in IO/about.c See the attached page as an example. I'd prefer to have both and to offer as an option from the download page (as with Fedora). WARNING: Please don't make the packages yet, I've got a last minute security vulnerability email, so maybe the tarball will change once more (the last). I'll try to have this solved tomorrow in the morning. -- Cheers Jorge.-

June 19, 2009

dillo-2.1.tar.bz2

by newman.x＠gmail.com

On Thu, Jun 18, 2009 at 9:56 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > Hi, > > ?Working on > > ? ?2.- To enable-ssl or not enable-ssl (define what to do). > > > On Thu, Jun 18, 2009 at 10:36:39AM +0200, Michal Nowak wrote: >> [...] >> Generally speaking for Fedora, we won't turn on options which are not >> turned on by default in upstream - it usually brings divergence from >> upstream and comments in upstream mailing lists (not this one :) ) >> like: "That poor distroX turned on --enable-coolness so we are not >> supporting users of this distro at all." >> >> Turning on SSL in upstream means more pressure for fixing it, usually >> :). But I am reading dillo-dev long enough to know it's not that easy. [snip] > > ?Obviously the safe option is not to offer ssl-enabled packages, > but that will mainly have the effect of no https-dpi at all. > > ?I'm not quite sure which one would be best. > ?Comments? http://mnowak.fedorapeople.org/dillo2/static/ Looks like Kelson's having some problems with building, so I patched-rebuilt-installed Kelson's static FLTK2 SRPM and rebuilt Dillo2. Now there are present i586 pkgs for F-11, both SSL on/off, tomorrow I can build x86-64 pkgs for F-11 at work. And i386 packs for F-10 (hopefully there's still the F-10 beast in KVM). (But treat them as third party ones, don't trust them :). ) > > > -- > ?Cheers > ?Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

June 18, 2009

dillo-2.1.tar.bz2

by devidfil＠gmail.com

In Debian, the package in the repo is built with ssl enabled, I prefer to have the new package with ssl too. Is possible to just show a warning opening dillo? Devid On 6/18/09, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > Hi, > > Working on > > 2.- To enable-ssl or not enable-ssl (define what to do). > > > On Thu, Jun 18, 2009 at 10:36:39AM +0200, Michal Nowak wrote: >> [...] >> Generally speaking for Fedora, we won't turn on options which are not >> turned on by default in upstream - it usually brings divergence from >> upstream and comments in upstream mailing lists (not this one :) ) >> like: "That poor distroX turned on --enable-coolness so we are not >> supporting users of this distro at all." >> >> Turning on SSL in upstream means more pressure for fixing it, usually >> :). But I am reading dillo-dev long enough to know it's not that easy. > > Reading forums served on https is handy, so I understand if a > user wants to have it enabled. > > Considering that making a user compile dillo is currently a > complex operation (the apparently simple --enable-ssl switch is > complex because of FLTK2 installation issues), I'd try to provide > the packaged option as an alternative to the main package (not > SSL-enabled). > > Something like: > > --------------------------------------------------------------- > Debian: > > Jaunty, Karmic (click here) > > Fedora: > > F11, F12 (click here) > > --------------------------------------------------------------- > With alpha HTTPS support: > * Note that this is NOT checking certificates, may get stuck > in asking dialogs, but will let you read https forums. > > USE AT YOUR OWN RISK > > Debian: > > Jaunty, Karmic (click here) > > Fedora: > > F11, F12 (click here) > --------------------------------------------------------------- > > > > Obviously the safe option is not to offer ssl-enabled packages, > but that will mainly have the effect of no https-dpi at all. > > I'm not quite sure which one would be best. > Comments? > > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

June 18, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

Hi, Working on 2.- To enable-ssl or not enable-ssl (define what to do). On Thu, Jun 18, 2009 at 10:36:39AM +0200, Michal Nowak wrote: > [...] > Generally speaking for Fedora, we won't turn on options which are not > turned on by default in upstream - it usually brings divergence from > upstream and comments in upstream mailing lists (not this one :) ) > like: "That poor distroX turned on --enable-coolness so we are not > supporting users of this distro at all." > > Turning on SSL in upstream means more pressure for fixing it, usually > :). But I am reading dillo-dev long enough to know it's not that easy. Reading forums served on https is handy, so I understand if a user wants to have it enabled. Considering that making a user compile dillo is currently a complex operation (the apparently simple --enable-ssl switch is complex because of FLTK2 installation issues), I'd try to provide the packaged option as an alternative to the main package (not SSL-enabled). Something like: --------------------------------------------------------------- Debian: Jaunty, Karmic (click here) Fedora: F11, F12 (click here) --------------------------------------------------------------- With alpha HTTPS support: * Note that this is NOT checking certificates, may get stuck in asking dialogs, but will let you read https forums. USE AT YOUR OWN RISK Debian: Jaunty, Karmic (click here) Fedora: F11, F12 (click here) --------------------------------------------------------------- Obviously the safe option is not to offer ssl-enabled packages, but that will mainly have the effect of no https-dpi at all. I'm not quite sure which one would be best. Comments? -- Cheers Jorge.-

June 18, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

On Thu, Jun 18, 2009 at 09:01:39PM +0200, Devid Antonio Filoni wrote: > On Thu, Jun 18, 2009 at 6:57 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > > Hi, > > > > ?Working on: > > > > ? ? 1.- Solve the OpenSSL license issue and upload rc3. > > > > > > On Thu, Jun 18, 2009 at 05:24:25PM +0200, Devid Antonio Filoni wrote: > >> On Wed, Jun 17, 2009 at 11:45 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > >> > On Wed, Jun 17, 2009 at 10:01:12PM +0200, Devid Antonio Filoni wrote: > >> > [...] > >> > ?Devid: please send me the .deb and its directions when done. > >> DONE! You can find it at https://launchpad.net/~d.filoni/+archive/ppa > >> . However I found an error checking my package using lintian: > >> > >> E: dillo: possible-gpl-code-linked-with-openssl > >> N: > >> N: ? ?This package appears to be covered by the GNU GPL but depends on the > >> N: ? ?OpenSSL libssl package and does not mention a license exemption or > >> N: ? ?exception for OpenSSL in its copyright file. The GPL (including version > >> N: ? ?3) is incompatible with some terms of the OpenSSL license, and therefore > >> N: ? ?Debian does not allow GPL-licensed code linked with OpenSSL libraries > >> N: ? ?unless there is a license exception explicitly permitting this. > >> N: > >> N: ? ?If only the Debian packaging, or some other part of the package not > >> N: ? ?linked with OpenSSL, is covered by the GNU GPL, please add a lintian > >> N: ? ?override for this tag. Lintian currently has no good way of > >> N: ? ?distinguishing between that case and problematic packages. > >> N: > >> N: ? ?Severity: serious, Certainty: wild-guess > >> > >> Can you please fix it? > > > > ?AFAIS, the only program that links to OpenSSL is the https dpi. > > i.e. The ssl-enabled dillo binary doesn't link to it. > > ? ? https.filter.dpi links to it. > > > > ?IANAL, but it looks like giving permission for this dpi is enough, > > and it's already done in its sources (dpi/https.c): > > > > ?* [...] > > ?* As a special exception permission is granted to link the code of > > ?* the https dillo plugin with the OpenSSL project's "OpenSSL" > > ?* library, and distribute the linked executables, without including > > ?* the source code for OpenSSL in the source distribution. You must > > ?* obey the GNU General Public License, version 3, in all respects > > ?* for all of the code used other than "OpenSSL". > > ?* > > ?*/ > > > > > > ?Please let me know if this is _really_ enough or if some extra > > legal formula must be added somewhere else. > It should be enough, at least this is what I see for example at > http://lists.octality.com/pipermail/cherokee/2008-November/009408.html > (take a look in that page for more infos) Good! After reading it and the suggested URLs, especially [1], it looks like our current tarball (rc2) is enough. No new tarball is needed! I consider this point solved, so let's move to the second one... [1] http://www.openssl.org/support/faq.html#LEGAL2 -- Cheers Jorge.-

June 18, 2009

dillo-2.1.tar.bz2

by devidfil＠gmail.com

On Thu, Jun 18, 2009 at 6:57 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > Hi, > > ?Working on: > > ? ? 1.- Solve the OpenSSL license issue and upload rc3. > > > On Thu, Jun 18, 2009 at 05:24:25PM +0200, Devid Antonio Filoni wrote: >> On Wed, Jun 17, 2009 at 11:45 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: >> > On Wed, Jun 17, 2009 at 10:01:12PM +0200, Devid Antonio Filoni wrote: >> > [...] >> > ?Devid: please send me the .deb and its directions when done. >> DONE! You can find it at https://launchpad.net/~d.filoni/+archive/ppa >> . However I found an error checking my package using lintian: >> >> E: dillo: possible-gpl-code-linked-with-openssl >> N: >> N: ? ?This package appears to be covered by the GNU GPL but depends on the >> N: ? ?OpenSSL libssl package and does not mention a license exemption or >> N: ? ?exception for OpenSSL in its copyright file. The GPL (including version >> N: ? ?3) is incompatible with some terms of the OpenSSL license, and therefore >> N: ? ?Debian does not allow GPL-licensed code linked with OpenSSL libraries >> N: ? ?unless there is a license exception explicitly permitting this. >> N: >> N: ? ?If only the Debian packaging, or some other part of the package not >> N: ? ?linked with OpenSSL, is covered by the GNU GPL, please add a lintian >> N: ? ?override for this tag. Lintian currently has no good way of >> N: ? ?distinguishing between that case and problematic packages. >> N: >> N: ? ?Severity: serious, Certainty: wild-guess >> >> Can you please fix it? > > ?AFAIS, the only program that links to OpenSSL is the https dpi. > i.e. The ssl-enabled dillo binary doesn't link to it. > ? ? https.filter.dpi links to it. > > ?IANAL, but it looks like giving permission for this dpi is enough, > and it's already done in its sources (dpi/https.c): > > ?* [...] > ?* As a special exception permission is granted to link the code of > ?* the https dillo plugin with the OpenSSL project's "OpenSSL" > ?* library, and distribute the linked executables, without including > ?* the source code for OpenSSL in the source distribution. You must > ?* obey the GNU General Public License, version 3, in all respects > ?* for all of the code used other than "OpenSSL". > ?* > ?*/ > > > ?Please let me know if this is _really_ enough or if some extra > legal formula must be added somewhere else. It should be enough, at least this is what I see for example at http://lists.octality.com/pipermail/cherokee/2008-November/009408.html (take a look in that page for more infos) > ?TIA. > > -- > ?Cheers > ?Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev > Devid

June 18, 2009

dillo-2.1.tar.bz2

by kelson＠pobox.com

corvid wrote: > Kelson wrote: >> http://www.hyperborea.org/software/dillo/rpms/fltk2-2.0.x.r6403-0.2.src.rpm > > We should use >= 6525 Oops! Wrong link! That's what I used to build the 2.0 packages last October. I meant this one: http://www.hyperborea.org/software/dillo/rpms/fltk2-2.0.x.r6786-0.1.src.rpm -- Kelson Vibber Hyperborea.org - SpeedForce.org

June 18, 2009

dillo-2.1.tar.bz2

by jcid＠dillo.org

Hi, Working on: 1.- Solve the OpenSSL license issue and upload rc3. On Thu, Jun 18, 2009 at 05:24:25PM +0200, Devid Antonio Filoni wrote: > On Wed, Jun 17, 2009 at 11:45 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > > On Wed, Jun 17, 2009 at 10:01:12PM +0200, Devid Antonio Filoni wrote: > > [...] > > ?Devid: please send me the .deb and its directions when done. > DONE! You can find it at https://launchpad.net/~d.filoni/+archive/ppa > . However I found an error checking my package using lintian: > > E: dillo: possible-gpl-code-linked-with-openssl > N: > N: This package appears to be covered by the GNU GPL but depends on the > N: OpenSSL libssl package and does not mention a license exemption or > N: exception for OpenSSL in its copyright file. The GPL (including version > N: 3) is incompatible with some terms of the OpenSSL license, and therefore > N: Debian does not allow GPL-licensed code linked with OpenSSL libraries > N: unless there is a license exception explicitly permitting this. > N: > N: If only the Debian packaging, or some other part of the package not > N: linked with OpenSSL, is covered by the GNU GPL, please add a lintian > N: override for this tag. Lintian currently has no good way of > N: distinguishing between that case and problematic packages. > N: > N: Severity: serious, Certainty: wild-guess > > Can you please fix it? AFAIS, the only program that links to OpenSSL is the https dpi. i.e. The ssl-enabled dillo binary doesn't link to it. https.filter.dpi links to it. IANAL, but it looks like giving permission for this dpi is enough, and it's already done in its sources (dpi/https.c): * [...] * As a special exception permission is granted to link the code of * the https dillo plugin with the OpenSSL project's "OpenSSL" * library, and distribute the linked executables, without including * the source code for OpenSSL in the source distribution. You must * obey the GNU General Public License, version 3, in all respects * for all of the code used other than "OpenSSL". * */ Please let me know if this is _really_ enough or if some extra legal formula must be added somewhere else. TIA. -- Cheers Jorge.-

June 18, 2009