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

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