- Dillo-dev - lists.mailman3.com

Who among you values standard_widget_colors? (was Re: [Dillo-dev] cut off word ends with italic fonts)

by Johannes.Hofmann＠gmx.de

On Wed, Sep 24, 2008 at 06:18:02PM +0100, Jeremy Henty wrote: > On Wed, Sep 24, 2008 at 04:36:48PM +0200, Johannes Hofmann wrote: > > > I'm running with standard_widget_colors=NO all the time and like it. > > I've been surfing with the default so I just tried switching to > standard_widget_colors=YES and... I don't see much difference. What > does it affect? So far I'm indifferent to it. > Check the form inputs at the top of www.freshmeat.net for example. They should have the current background color with standard_widget_colors=NO. Regards, Johannes

Sept. 24, 2008

Who among you values standard_widget_colors? (was Re: [Dillo-dev] cut off word ends with italic fonts)

by onepoint＠starurchin.org

On Wed, Sep 24, 2008 at 04:36:48PM +0200, Johannes Hofmann wrote: > I'm running with standard_widget_colors=NO all the time and like it. I've been surfing with the default so I just tried switching to standard_widget_colors=YES and... I don't see much difference. What does it affect? So far I'm indifferent to it. Regards, Jeremy Henty

Sept. 24, 2008

release packaging

by Johannes.Hofmann＠gmx.de

On Tue, Sep 23, 2008 at 07:11:03PM -0400, Jorge Arellano Cid wrote: > On Tue, Sep 23, 2008 at 02:54:10PM +0100, Jeremy Henty wrote: > > On Tue, Sep 23, 2008 at 07:52:07AM +0200, Andreas Kemnade wrote: > > > > > Currently you need to download three tarballs to compile dillo > > > (fltk,dw,dillo). I doubt that any linux distribution has fltk2 > > > packages at the moment. (and also not openembedded) What's the plan > > > about that? > > > > FLTK2's API is still not frozen, and its ABI does change quite often > > so we will have to supply the tarball ourselves. It would be simplest > > just to keep a copy of the right FLTK2 snapshot on the dillo site > > under a link saying "use *this* version". The problem is not that > > distros won't supply packages, the problem is that they *will* and it > > might be the wrong version. (Expect "I upgraded FLTK2 and Dillo > > crashed" reports!) > > > > The dw package is an awkward case. I think we should bite the bullet > > and either move it inside dillo2 or make it an independent package > > that the user installs and have dillo2 find and use the installed dw > > (and lose the dw-testbed symbolic link). > > > > Thoughts? > > I'd move dw2 inside dillo2's tree (as it was before), > and have a recommended FLTK2 tarball in our site. That sounds good! Cheers, Johannes

Sept. 24, 2008

Who among you values standard_widget_colors? (was Re: [Dillo-dev] cut off word ends with italic fonts)

by jcid＠dillo.org

On Wed, Sep 24, 2008 at 04:36:48PM +0200, Johannes Hofmann wrote: > On Tue, Sep 23, 2008 at 09:17:28PM +0000, corvid wrote: > > Jorge encouraged me to add that preference in case anyone wanted it > > back when the, ahh, 'nonstandard' widget colors came along some months ago, > > but I have no idea whether anyone uses it. > > I'm running with standard_widget_colors=NO all the time and like it. Me too! -- Cheers Jorge.-

Sept. 24, 2008

Who among you values standard_widget_colors? (was Re: [Dillo-dev] cut off word ends with italic fonts)

by Johannes.Hofmann＠gmx.de

On Tue, Sep 23, 2008 at 09:17:28PM +0000, corvid wrote: > Jorge encouraged me to add that preference in case anyone wanted it > back when the, ahh, 'nonstandard' widget colors came along some months ago, > but I have no idea whether anyone uses it. I'm running with standard_widget_colors=NO all the time and like it. Cheers, Johannes

Sept. 24, 2008

patch: Re: [Dillo-dev] release packaging

by jcid＠dillo.org

On Wed, Sep 24, 2008 at 06:09:44AM +0000, corvid wrote: > bf wrote: > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-toolkits/fltk2/ > > > > (but unfortunately you won't be able to view that with dillo2: > > "HTTP warning: Content-Type 'text/html' doesn't match the real data." -- fixes?) > > "gzip" has been registered with the IANA since...since trilobites stalked > the seas, and I explicitly said "gzip" for Accept-Encoding, not "x-gzip", > but rfc2616 does state: > For compatibility with previous implementations of HTTP, > applications SHOULD consider "x-gzip" and "x-compress" to be > equivalent to "gzip" and "compress" respectively. > Committed. -- Cheers Jorge.-

Sept. 24, 2008

patch: Re: [Dillo-dev] release packaging

by corvid＠lavabit.com

bf wrote: > http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-toolkits/fltk2/ > > (but unfortunately you won't be able to view that with dillo2: > "HTTP warning: Content-Type 'text/html' doesn't match the real data." -- fixes?) "gzip" has been registered with the IANA since...since trilobites stalked the seas, and I explicitly said "gzip" for Accept-Encoding, not "x-gzip", but rfc2616 does state: For compatibility with previous implementations of HTTP, applications SHOULD consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively.

Sept. 24, 2008

release packaging

by corvid＠lavabit.com

Jorge wrote: > On Tue, Sep 23, 2008 at 02:54:10PM +0100, Jeremy Henty wrote: > > On Tue, Sep 23, 2008 at 07:52:07AM +0200, Andreas Kemnade wrote: > > > > > Currently you need to download three tarballs to compile dillo > > > (fltk,dw,dillo). I doubt that any linux distribution has fltk2 > > > packages at the moment. (and also not openembedded) What's the plan > > > about that? > > > > FLTK2's API is still not frozen, and its ABI does change quite often > > so we will have to supply the tarball ourselves. It would be simplest > > just to keep a copy of the right FLTK2 snapshot on the dillo site > > under a link saying "use *this* version". The problem is not that > > distros won't supply packages, the problem is that they *will* and it > > might be the wrong version. (Expect "I upgraded FLTK2 and Dillo > > crashed" reports!) > > > > The dw package is an awkward case. I think we should bite the bullet > > and either move it inside dillo2 or make it an independent package > > that the user installs and have dillo2 find and use the installed dw > > (and lose the dw-testbed symbolic link). > > > > Thoughts? > > I'd move dw2 inside dillo2's tree (as it was before), > and have a recommended FLTK2 tarball in our site. > > Please somebody send me a patch with this code move. > That way I can focus on Tabs... I will.

Sept. 24, 2008

release packaging

by jcid＠dillo.org

On Tue, Sep 23, 2008 at 04:15:01PM +0200, Christian Kellermann wrote: > * Jeremy Henty <onepoint(a)starurchin.org> [080923 15:57]: > > On Tue, Sep 23, 2008 at 07:52:07AM +0200, Andreas Kemnade wrote: > > > > The dw package is an awkward case. I think we should bite the bullet > > and either move it inside dillo2 or make it an independent package > > that the user installs and have dillo2 find and use the installed dw > > (and lose the dw-testbed symbolic link). > > > > Sorry for this interruption but what is the reason dw exists? > I never understood that. Dw2 can also be used for other projects. Sometime ago, having independent trees allowed Sebastian and me to work comfortably. but now, AFAIS, dw2 fits better inside dillo2's tree. -- Cheers Jorge.-

Sept. 24, 2008

release packaging

by jcid＠dillo.org

On Tue, Sep 23, 2008 at 02:54:10PM +0100, Jeremy Henty wrote: > On Tue, Sep 23, 2008 at 07:52:07AM +0200, Andreas Kemnade wrote: > > > Currently you need to download three tarballs to compile dillo > > (fltk,dw,dillo). I doubt that any linux distribution has fltk2 > > packages at the moment. (and also not openembedded) What's the plan > > about that? > > FLTK2's API is still not frozen, and its ABI does change quite often > so we will have to supply the tarball ourselves. It would be simplest > just to keep a copy of the right FLTK2 snapshot on the dillo site > under a link saying "use *this* version". The problem is not that > distros won't supply packages, the problem is that they *will* and it > might be the wrong version. (Expect "I upgraded FLTK2 and Dillo > crashed" reports!) > > The dw package is an awkward case. I think we should bite the bullet > and either move it inside dillo2 or make it an independent package > that the user installs and have dillo2 find and use the installed dw > (and lose the dw-testbed symbolic link). > > Thoughts? I'd move dw2 inside dillo2's tree (as it was before), and have a recommended FLTK2 tarball in our site. Please somebody send me a patch with this code move. That way I can focus on Tabs... -- Cheers Jorge.-

Sept. 24, 2008