- Dillo-dev - lists.mailman3.com

[PATCH] initialise Layout::scrollIdleNotInterrupted

by jcid＠dillo.org

On Tue, Jan 01, 2008 at 02:10:54PM +0000, Jeremy Henty wrote: > > This is another valgrind pacifier; it squashes an error "Conditional > jump or move depends on uninitialised value(s)" at > "dw::core::Layout::updateAnchor() (layout.cc:474)" from "valgrind > dw2-cur/test/dw-lists". Committed. -- Cheers Jorge.-

Jan. 2, 2008

Re: "de-exporting" prefs stuff

by jcid＠dillo.org

On Tue, Jan 01, 2008 at 01:25:01AM +0000, place wrote: > Inspired by the 'de-exporting' of all of the gunk that had been in html.hh > a couple of months ago. (plus a few new defines and a 'static const') Committed. -- Cheers Jorge.-

Jan. 2, 2008

patch: color shading

by jcid＠dillo.org

On Sun, Dec 30, 2007 at 05:37:14AM +0000, place wrote: > This should make shading better... > Committed. BTW, would you mind looking at this case? <table border=90> <tr> <td>1 2 3 4 <td>5 6 7 8 9 10 <td>A <tr> <td colspan="2" bgcolor=teal>cs=2 <td>B </table> It may use a bevel like firefox. On to another topic: Have you kept on working on the code to suport charset decoding when specified in the HEAD section? -- Cheers Jorge.-

Jan. 2, 2008

[patch] fix hanging stop button

by jcid＠dillo.org

On Sat, Dec 29, 2007 at 10:37:30AM +0100, Johannes Hofmann wrote: > Hello, > > when pressing the stop button, it get's deactivated properly, but > seems to get stuck in the pressed position. > The patch below fixes the problem here. For the back- and forward- > buttons it's not really necessary, because the url change seems to > cause the necessary redraw anyway. However I added it there too for > consistency. Committed. -- Cheers Jorge.-

Jan. 2, 2008

patch: start_page and fullwindow_start prefs

by place＠gobigwest.com

Jan. 2, 2008

patch: the position part of the geometry pref.

by place＠gobigwest.com

(That is, the X and Y of "geometry=WxH+X+Y") It appears that fltk just _guesses_ what the border size might be rather than actually determining the value. So when I run this with no window mgr, it puts the window where it would be if there were a 4-pixel-wide border and 21-pixel-high title bar. Same with twm, which is suboptimal because twm doesn't use those dimensions. As for fvwm2, which is the one I actually use -- and does appear to have those dimensions -- somehow the window ends up eight pixels too far down. But I'm regarding this as Not My Problem.

Jan. 2, 2008

[patch] make TopGroup a PackedGroup

by jcid＠dillo.org

On Tue, Jan 01, 2008 at 04:41:49PM +0100, Johannes Hofmann wrote: > Hi Jorge, > > On Tue, Jan 01, 2008 at 11:26:59AM -0300, Jorge Arellano Cid wrote: > > Hi Johannes, > > > > On Fri, Dec 28, 2007 at 05:26:19PM +0100, Johannes Hofmann wrote: > > > Hello, > > > > > > as I didn't get any feedback from Sebastian yet on my proposal > > > to make the scrollbars part of UI instead of FltkViewport, I > > > decided to split my initial patch. > > > Below is a version that still uses a PackedGroup in UI, but leaves > > > the scrollbars in FltkViewport. > > > Here comes the details: > > > > > > * Make scrollbars really children of FltkViewport, as it was > > > probabely intended. > > > * Use widget local coordinates in FltkViewport::adjustScrollbarsAndGadgets. > > > * Adjust draw() and handle() so that scrollbars work properly. > > > * As a consequence replace() now works properly, so remove the > > > workaround. > > > * Make TopGroup a PackedGroup and let it do the layout. > > > * Simplify fullscreen mode. > > > > > > This also fixes annoying problems with the statusbar when new windows > > > are created in fullscreen mode. > > > > Reviewing the patch made me remember the struggle I had, to > > develop those workarounds to have the UI working. As you may > > intuit I'm more than willing to commit. ;-) > > > > The question is: Do you agree with commiting now or do you > > prefer to hold them for comment as the former patch? > > I think it can be commited, as this new patch does not include the > reorganization of my initial patch that makes the scrollbars part of > the UI and thereby obsoletes all the ScrollbarThickness stuff in dw. Committed! -- Cheers Jorge.-

Jan. 2, 2008

[PATCH] image load graphics improvements

by onepoint＠starurchin.org

This patch tweaks the image load graphics: the spacing is nicer and the 'G' in "IMG" is more legible. You can preview the changes at http://starurchin.org/dillo/image_load/ . Regards, Jeremy Henty

Jan. 1, 2008

Best wishes for this year 2008

by onepoint＠starurchin.org

On Tue, Jan 01, 2008 at 10:38:17AM -0300, Jorge Arellano Cid wrote: > I want to start the year expressing my gratitude to all of you who > have contributed your time and effort to make the Dillo project > continue forward. Likewise I am grateful to you for opening up Dillo development so that we can contribute! > The working atmosphere is very nice and that's a very important > asset! I agree. I have been very encouraged by the good-natured and constructive responses my suggestions have received. I hope everyone else feels the same. Regards, Jeremy Henty

Jan. 1, 2008

[patch] make TopGroup a PackedGroup

by Johannes.Hofmann＠gmx.de

Hi Jorge, On Tue, Jan 01, 2008 at 11:26:59AM -0300, Jorge Arellano Cid wrote: > Hi Johannes, > > On Fri, Dec 28, 2007 at 05:26:19PM +0100, Johannes Hofmann wrote: > > Hello, > > > > as I didn't get any feedback from Sebastian yet on my proposal > > to make the scrollbars part of UI instead of FltkViewport, I > > decided to split my initial patch. > > Below is a version that still uses a PackedGroup in UI, but leaves > > the scrollbars in FltkViewport. > > Here comes the details: > > > > * Make scrollbars really children of FltkViewport, as it was > > probabely intended. > > * Use widget local coordinates in FltkViewport::adjustScrollbarsAndGadgets. > > * Adjust draw() and handle() so that scrollbars work properly. > > * As a consequence replace() now works properly, so remove the > > workaround. > > * Make TopGroup a PackedGroup and let it do the layout. > > * Simplify fullscreen mode. > > > > This also fixes annoying problems with the statusbar when new windows > > are created in fullscreen mode. > > Reviewing the patch made me remember the struggle I had, to > develop those workarounds to have the UI working. As you may > intuit I'm more than willing to commit. ;-) > > The question is: Do you agree with commiting now or do you > prefer to hold them for comment as the former patch? I think it can be commited, as this new patch does not include the reorganization of my initial patch that makes the scrollbars part of the UI and thereby obsoletes all the ScrollbarThickness stuff in dw. Cheers, Johannes > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

Jan. 1, 2008