On Wed, Oct 08, 2008 at 05:04:29PM +0200, Joerg Sonnenberger wrote:
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.
OK, just checked Debian and Ubuntu and both have the dillo viewer plugin for sylpheed with a dependency on the plain "dillo" package. Looking around in the FLTK docs, there's this function: CreatedWindow::set_xid() It looks promising. Unfortunately I haven't found a full code example to make it work. If somebody knows how to use it, it'd be simple to make a "drop in" replacement for dillo1, and avoid the problems discussed in this thread. BTW, I'm inclined to using dillorc/dillo/2.0 in the release. -- Cheers Jorge.-