October 2008 - Dillo-dev - lists.mailman3.com

panel_size=tiny have no menu

by jcid＠dillo.org

On Wed, Oct 08, 2008 at 04:54:14PM +0100, Jeremy Henty wrote: > On Wed, Oct 08, 2008 at 09:50:43AM -0400, Jorge Arellano Cid wrote: > > > Please test this long patch: > > > > http://www.dillo.org/test/file_popup.OK1 > > It works very nicely, at least after a minute's use! I'd really like > to see this go in at some time. Yes, it is intended for commit! Considering that we may release this Saturday, we have three days to test it, which is not much. Heavy testing and good reports may make me add it in though... -- Cheers Jorge.-

Oct. 8, 2008

panel_size=tiny have no menu

by onepoint＠starurchin.org

On Wed, Oct 08, 2008 at 09:50:43AM -0400, Jorge Arellano Cid wrote: > Please test this long patch: > > http://www.dillo.org/test/file_popup.OK1 It works very nicely, at least after a minute's use! I'd really like to see this go in at some time. Jeremy Henty

Oct. 8, 2008

patch: close windows from menubar

by corvid＠lavabit.com

Johannes wrote: > On Tue, Oct 07, 2008 at 10:54:47PM +0000, corvid wrote: > > Johannes wrote: > > > On Tue, Oct 07, 2008 at 06:12:47PM +0000, corvid wrote: > > > > Johannes wrote: > > > > > Excellent. From previous announcements I'd expect the next weekly > > > > > fltk2 snapshot by friday. > > > > > Is there anything left we need for the release? > > > > > What about the binary and config file name? > > > > > > > > We have to remember to take clear_double_buffer out before releasing. > > > > > > > > > > I thought we would keep it. > > > Without it things get awfully slow here with more than 5 windows. > > > Also all the backBuffer stuff in FltkViewBase would be unnecessary > > > then. > > > Are you seeing any problems with clear_double_buffer()? > > > > In the course of this thread: > > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-April/004022.html > > we learned that drawing with antialiased fonts is exceedingly slow > > for me for some reason with clear_double_buffer. > > I thought that had been resolved by changing the color depth. 16-bit is amazingly slow and 24-bit is less slow, but 24-bit made other things like rxvt quite slow. Turning off antialiasing made it very fast, but then if I want good unicode coverage... > Anyway, what about a runtime option to choose the buffering scheme Perhaps.

Oct. 8, 2008

patch: close windows from menubar

by corvid＠lavabit.com

Francis wrote: > If a distribution is to package it, unless the new program is a drop-in > replacement for the old program, the new program should probably have > a different name. If history is any judge, they will modify it to remove security and add in buggy features. (Some people even think of dillo as having a reputation for being _crashy_, of all things...) If they rename it, all the better.

Oct. 8, 2008

patch: close windows from menubar

by Johannes.Hofmann＠gmx.de

On Tue, Oct 07, 2008 at 10:54:47PM +0000, corvid wrote: > Johannes wrote: > > On Tue, Oct 07, 2008 at 06:12:47PM +0000, corvid wrote: > > > Johannes wrote: > > > > Excellent. From previous announcements I'd expect the next weekly > > > > fltk2 snapshot by friday. > > > > Is there anything left we need for the release? > > > > What about the binary and config file name? > > > > > > We have to remember to take clear_double_buffer out before releasing. > > > > > > > I thought we would keep it. > > Without it things get awfully slow here with more than 5 windows. > > Also all the backBuffer stuff in FltkViewBase would be unnecessary > > then. > > Are you seeing any problems with clear_double_buffer()? > > In the course of this thread: > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-April/004022.html > we learned that drawing with antialiased fonts is exceedingly slow > for me for some reason with clear_double_buffer. I thought that had been resolved by changing the color depth. Anyway, what about a runtime option to choose the buffering scheme (patch attached). Please review the wording especially in the dillo2rc comment. Cheers, Johannes

Oct. 8, 2008

patch: close windows from menubar

by joerg.sonnenberger＠web.de

On Wed, Oct 08, 2008 at 03:32:42PM +0100, Jeremy Henty wrote: > On Wed, Oct 08, 2008 at 01:09:48PM +0200, Joerg Sonnenberger wrote: > > > ... why would you want dillo1 and dillo2 at the same time. > > I don't know. But when you start saying "No-one could *possibly* want > to do that, so let's stop supporting it" then you are riding for a > fall. Why make ourselves hostages to fortune? Why not make *sure* we > avoid the problem rather than gambling that we've second-guessed our > entire user base? Murphy's law applies, so play it safe unless > there's a compelling reason not to. You are adding the overhead of changing user behavior though. The claws backend might be a good reason, frankly it is the only one I see so far. Personally I consider the old version without at least the Xft patches to be plainly useless and everyone I heared talk about using dillo so far had similiar impressions. So changing the binary name (it is still dillo after all) seems just artifical change. The comparisions with libraries doesn't apply. Joerg

Oct. 8, 2008

patch: close windows from menubar

by onepoint＠starurchin.org

On Wed, Oct 08, 2008 at 01:09:48PM +0200, Joerg Sonnenberger wrote: > ... why would you want dillo1 and dillo2 at the same time. I don't know. But when you start saying "No-one could *possibly* want to do that, so let's stop supporting it" then you are riding for a fall. Why make ourselves hostages to fortune? Why not make *sure* we avoid the problem rather than gambling that we've second-guessed our entire user base? Murphy's law applies, so play it safe unless there's a compelling reason not to. > ... If there is no such reason, it doesn't make sense to rename the > binary. But we're *not* renaming the binary! We're distributing a new and *different* binary that supports a *different* command line and links to *different* libraries. As far as the OS is concerned that makes them as unlike as chalk and cheese. Therefore we should play it safe by giving them different names. That is the conventional thing to do, and also the safest. Regards, Jeremy Henty

Oct. 8, 2008

patch: close windows from menubar

by francis＠daoine.org

On Wed, Oct 08, 2008 at 02:02:17PM +0000, corvid wrote: > Jorge wrote: > > On Wed, Oct 08, 2008 at 01:09:48PM +0200, Joerg Sonnenberger wrote: > > > On Wed, Oct 08, 2008 at 10:13:23AM +0100, Jeremy Henty wrote: > > > > Of course, dillo2 is not a library package, but I think it should > > > > follow the same convention on the grounds of least surprise. (Unless > > > > there is a compelling reason not to, but I don't think that there is.) > > Everybody: please add your comment in this thread, even if stated > > before. > > I would prefer "dillo". If anybody wants/needs both versions, mv and ln -s > are available to them. I would prefer "dillo2". If anybody builds their own version, it should be easy enough for them to change it to "dillo", "dillorc", etc. at compile time. If a distribution is to package it, unless the new program is a drop-in replacement for the old program, the new program should probably have a different name. I haven't looked at fltk-dillo much, but command-line switches acting differently isn't a sign of a drop-in replacement. Are there any incompatibilities with the content of the rc file? Just my haven't-coded-in-a-while opinion... f -- Francis Daly francis(a)daoine.org

Oct. 8, 2008

patch: close windows from menubar

by Johannes.Hofmann＠gmx.de

On Wed, Oct 08, 2008 at 02:02:17PM +0000, corvid wrote: > Jorge wrote: > > On Wed, Oct 08, 2008 at 01:09:48PM +0200, Joerg Sonnenberger wrote: > > > On Wed, Oct 08, 2008 at 10:13:23AM +0100, Jeremy Henty wrote: > > > > Of course, dillo2 is not a library package, but I think it should > > > > follow the same convention on the grounds of least surprise. (Unless > > > > there is a compelling reason not to, but I don't think that there is.) > > > > > > Does dillo1 offer *anything* over dillo2? E.g. why would you want dillo1 > > > and dillo2 at the same time. If there is no such reason, it doesn't make > > > sense to rename the binary. > > > > Dillo1 is used as an html viewer by sylpheed (claws). I don't > > know the name of the binary they distribute though. Dillo2 doesn't > > provide the required CLI switches yet. > > > > That's it AFAIR. Dillo2 doesn't have these switches: > > > > -x, --xid XID Open first Dillo window in an existing > > GtkSocket which window ID is XID (decimal). > > -v, --version Display version info and exit. > > -h, --help Display this help text and exit. > > -f, --fullwindow Start in full window mode: hide address bar, > > navigation buttons, menu, and status bar. > > -l, --local Don't follow links for this URL(s). > > -g, -geometry GEO Set initial window position where GEO is > > <width>x<height>{+-}<x>{+-}<y> > > -D, --debug-rendering Draw additionaly several lines in a web page, > > representing its structure. For debugging. > > > > Everybody: please add your comment in this thread, even if stated > > before. > > I would prefer "dillo". If anybody wants/needs both versions, mv and ln -s > are available to them. > Me too. Citing from the homepage: "Dillo is following an evolving software-model where every new version of it, should be better than the former one; there's no place for unstable releases, so just keep with the latest one" I would even use dillorc for consistency. Cheers, Johannes

Oct. 8, 2008

patch: close windows from menubar

by corvid＠lavabit.com

Jorge wrote: > On Wed, Oct 08, 2008 at 01:09:48PM +0200, Joerg Sonnenberger wrote: > > On Wed, Oct 08, 2008 at 10:13:23AM +0100, Jeremy Henty wrote: > > > Of course, dillo2 is not a library package, but I think it should > > > follow the same convention on the grounds of least surprise. (Unless > > > there is a compelling reason not to, but I don't think that there is.) > > > > Does dillo1 offer *anything* over dillo2? E.g. why would you want dillo1 > > and dillo2 at the same time. If there is no such reason, it doesn't make > > sense to rename the binary. > > Dillo1 is used as an html viewer by sylpheed (claws). I don't > know the name of the binary they distribute though. Dillo2 doesn't > provide the required CLI switches yet. > > That's it AFAIR. Dillo2 doesn't have these switches: > > -x, --xid XID Open first Dillo window in an existing > GtkSocket which window ID is XID (decimal). > -v, --version Display version info and exit. > -h, --help Display this help text and exit. > -f, --fullwindow Start in full window mode: hide address bar, > navigation buttons, menu, and status bar. > -l, --local Don't follow links for this URL(s). > -g, -geometry GEO Set initial window position where GEO is > <width>x<height>{+-}<x>{+-}<y> > -D, --debug-rendering Draw additionaly several lines in a web page, > representing its structure. For debugging. > > Everybody: please add your comment in this thread, even if stated > before. I would prefer "dillo". If anybody wants/needs both versions, mv and ln -s are available to them.

Oct. 8, 2008