- Dillo-dev - lists.mailman3.com

Another mention of Dillo-2

by onepoint＠starurchin.org

"Dillo 2.0 is fast, but limited" http://www.linux.com/feature/151983 Summary: "It's *fast*, even faster than Dillo-1, but too limited to be of use to much people.". It singles out lack of JavaScript, pointing out that most business sites need it (although I'd imagine most business sites would need full SSL support too). Jeremy Henty

Nov. 6, 2008

Repost: D_SUN_LEN cleanup (and a typo fix)

by jcid＠dillo.org

On Wed, Nov 05, 2008 at 02:26:48PM +0000, Jeremy Henty wrote: > > This is a repost of three tidy-up patches that have been left hanging > without resolution. Please comment. > > 1. Remove unused D_SUN_LEN declarations from DPIs. (The DPIs connect > to their sockets with accept() which doesn't use D_SUN_LEN.) > > 2. Use D_SUN_LEN whenever calling connect() on a struct sockaddr_un. > (Some of the calls already did this, this patch makes all of them > do so.) > > 3. Update a GPL reference in a comment from version 2 to version 3. Committed! -- Cheers Jorge.-

Nov. 5, 2008

Repost: D_SUN_LEN cleanup (and a typo fix)

by onepoint＠starurchin.org

This is a repost of three tidy-up patches that have been left hanging without resolution. Please comment. 1. Remove unused D_SUN_LEN declarations from DPIs. (The DPIs connect to their sockets with accept() which doesn't use D_SUN_LEN.) 2. Use D_SUN_LEN whenever calling connect() on a struct sockaddr_un. (Some of the calls already did this, this patch makes all of them do so.) 3. Update a GPL reference in a comment from version 2 to version 3. Regards, Jeremy Henty

Nov. 5, 2008

Re: Interested in joining dillo project

by jcid＠dillo.org

On Fri, Oct 31, 2008 at 11:43:35PM +0100, PHELIZOT Yvan wrote: > Hi, > > That me again. And i have a lot of questions: > About management: > * Does we have a functionnalities/features list? We had one inside the funding initiative in the past. It was purposedly removed from the web site because it was not updated (obsolete), and because the funding effort yielded no results. You can still find some info here: http://www.dillo.org/funding/funding.html (go to "Technical Overview"). > For example, i have > seen that png and jpeg are not supported, so does it included in the > file...? That's false. Where did you find that misinformation? > * Is there a task list? to know what to do and with which priority > > Dev : > * How many developpers, testers, ... work on the project? Please check the website. "Current Plans", "Authors", etc. > Software: > * Does the software has a "quirk" mode? Something akin, give read to dillorc. w3c_plus_heuristics=YES -- Cheers Jorge.-

Nov. 5, 2008

[patch]: fix the download GUI resize bug

by onepoint＠starurchin.org

On Thu, Oct 30, 2008 at 05:32:58PM -0300, Jorge Arellano Cid wrote: > On Thu, Oct 30, 2008 at 07:17:27PM +0000, Jeremy Henty wrote: > > ... if I write a FLTK2 app with a scrolled list of buttons that > > delete themselves when pressed then I *do* get redisplay problems: > > the deleted buttons don't disappear. And the fix is to tell the > > scroll to redraw itself. > > Committed. Good! I'm glad something useful came out of this. > Yes, the example program showed exactly what I was getting here. > This looks like a bug in FLTK2 (AFAIU, the scroll group should take > care of its background when an item is removed). IIRC I've sometimes had to manually tell a widget to update/redraw itself and I thought this was a deliberate policy from the FLTK devs. I'll send them my example and ask. Regards, Jeremy Henty

Oct. 30, 2008

[patch]: fix the download GUI resize bug

by jcid＠dillo.org

On Thu, Oct 30, 2008 at 07:17:27PM +0000, Jeremy Henty wrote: > On Thu, Oct 30, 2008 at 02:54:57PM -0300, Jorge Arellano Cid wrote: > > > The test that fails here is: > > > > - load the dillo downloads page > > - download a tarball > > - download another > > - resize the window to 1.25 the height of both download panels > > - Once both are done, press done in the lower panel > > > > then I get the panel drawn over the old one (like a shadow). > > I cannot reproduce this at all!!! But if I write a FLTK2 app with a > scrolled list of buttons that delete themselves when pressed then I > *do* get redisplay problems: the deleted buttons don't disappear. And > the fix is to tell the scroll to redraw itself. I guess that's > because the scroll is responsible for the blank space left behind when > the button disappears. It would be interesting to know if this patch > fails the test. (I've also attached the FLTK2 app. If you comment > out the redraw() call in the callback you'll see that the bottom > button does not disappear after clicking any button, even though the > list has actually shrunk.) Committed. Yes, the example program showed exactly what I was getting here. This looks like a bug in FLTK2 (AFAIU, the scroll group should take care of its background when an item is removed). -- Cheers Jorge.-

Oct. 30, 2008

reduce warnings with gcc-4.3 [PATCH]

by jcid＠dillo.org

On Thu, Oct 30, 2008 at 07:10:34PM +0100, Thomas Orgis wrote: > Am Thu, 30 Oct 2008 14:37:37 -0300 > schrieb Jorge Arellano Cid <jcid(a)dillo.org>: > > > Does this produce the same warning? > > > > assert (i >= 0 && this->num - i > 0); > > That seems to be silent with gcc-4.3.1 ... I won't guarantee anything for gcc-4.3.2, though. > But I'll upgrade to that one in the next weeks for sure and will let you know. > For now this looks like a fine fix to make dillo2 compiler warning free! Committed. -- Cheers Jorge.-

Oct. 30, 2008

[patch]: fix the download GUI resize bug

by onepoint＠starurchin.org

On Thu, Oct 30, 2008 at 02:54:57PM -0300, Jorge Arellano Cid wrote: > The test that fails here is: > > - load the dillo downloads page > - download a tarball > - download another > - resize the window to 1.25 the height of both download panels > - Once both are done, press done in the lower panel > > then I get the panel drawn over the old one (like a shadow). I cannot reproduce this at all!!! But if I write a FLTK2 app with a scrolled list of buttons that delete themselves when pressed then I *do* get redisplay problems: the deleted buttons don't disappear. And the fix is to tell the scroll to redraw itself. I guess that's because the scroll is responsible for the blank space left behind when the button disappears. It would be interesting to know if this patch fails the test. (I've also attached the FLTK2 app. If you comment out the redraw() call in the callback you'll see that the bottom button does not disappear after clicking any button, even though the list has actually shrunk.) Regards, Jeremy Henty

Oct. 30, 2008

css

by Johannes.Hofmann＠gmx.de

Hi, On Fri, Oct 24, 2008 at 03:09:53PM -0300, Jorge Arellano Cid wrote: ** snip ** > > I currently think about a class that looks more or less like StyleAttrs > > together with a map indicating which of it's values are actually set. > > One can then start with a basic style and apply any number of > > objects of this new class according to the order of precedence. > > Applying here means overriding those values that are set according > > to the map. > > Where/how would attribute values be stored? We will probabely need a new class that holds the attributes, but after looking at the dillo-0.8.0-css3 code I decided to go with just the "style", "id", and "class" attributes for now. Attached patch implements something between step 2 and 3 of my css proposal. There are a lot of loose ends (e.g. memory management) but it's a start. Check the end of css.cc. Here the user-agent style is filled. In html.cc Html_tag_open_a() shows how StyleEngine is intended to be used. Note that StyleEngine::apply() currently only supports a limited number of attributes. I think html.cc will become a lot simpler. Cheers, Johannes PS: I had attached the patch, but that was blocked by the list. So here is a link instead: http://www.ecademix.com/JohannesHofmann/tmp/css_prototype.dillo2

Oct. 30, 2008

reduce warnings with gcc-4.3 [PATCH]

by thomas-forum＠orgis.org

Am Thu, 30 Oct 2008 14:37:37 -0300 schrieb Jorge Arellano Cid <jcid(a)dillo.org>: > Does this produce the same warning? > > assert (i >= 0 && this->num - i > 0); That seems to be silent with gcc-4.3.1 ... I won't guarantee anything for gcc-4.3.2, though. But I'll upgrade to that one in the next weeks for sure and will let you know. For now this looks like a fine fix to make dillo2 compiler warning free! Alrighty then, Thomas.

Oct. 30, 2008