- Dillo-dev - lists.mailman3.com

Copy and paste from page content area

by Johannes.Hofmann＠gmx.de

On Wed, Dec 29, 2010 at 03:13:02PM -0500, Benjamin Johnson wrote: > On Wed, 29 Dec 2010 14:56:43 -0500, corvid <corvid(a)lavabit.com> wrote: > > >It has that mechanism where you highlight text with the left mouse button > >to select it and middle button to paste somewhere, but it doesn't do the > >one that uses control keys (which I've never understood the value of). > > Non-X11 systems don't have the select-and-middle-click mechanism, > and with most X11 toolkits (Qt, GTK+, etc.), the control key > mechanism is more persistent. > > Anyway, thanks for the answer. That's one of the next things I was > planning to implement. Hm, I would have thought that copy/paste just works on Windows via the fltk::copy() call in FltkPlatform::copySelection(). Does copy/paste work for fltk2/test programs on Windows? Cheers, Johannes

Jan. 7, 2011

[patch]: more spring cleaning of configure.in

by corvid＠lavabit.com

Jeremy wrote: > Time to retire some more obsolete autoconf macros. See [1] for > details. > > 1: Replace AC_CANONICAL_SYSTEM with AC_CANONICAL_TARGET . > > 2: Replace AC_ERROR with AC_MSG_ERROR . > > 3: Replace AC_TRY_COMPILE with AC_COMPILE_IFELSE / AC_LANG_PROGRAM . > > This doesn't break for me, but it affects some host-dependent > parts of configure.in . It would be good to know that this works > on hosts with unusual socket / iconv library routines. > > 4: Replace AC_TRY_LINK_FUNC with AC_LINK_IFELSE / AC_LANG_CALL . > > This only affects target OSes *other* than linux, solaris, osf1 > and minix. Can anyone test on such a thing? > > 5: Indentation tweak for consistency. Works without giving me any problems...

Jan. 6, 2011

configure.in

by corvid＠lavabit.com

Jorge wrote: > On Wed, Jan 05, 2011 at 09:46:29PM +0000, corvid wrote: > > In configure.in, why is it > > LIBFLTK_LIBS=`fltk2-config --use-images --ldflags` > > if we use the system png/jpeg/etc. libraries and not > > the fltk ones? I just tried removing the --use-images > > argument, and everything still works for me. > > Probably because that way it worked with an older version. > Does the generated binary size change? Or is there a change > with ldd? No difference. (I was hoping it might make it a bit smaller.) > If the button icons load OK, and the file chooser works, there > should be no problems. Those widgets *may* need the internal > image handling (but I don't know for sure).

Jan. 6, 2011

configure.in

by jcid＠dillo.org

On Wed, Jan 05, 2011 at 09:46:29PM +0000, corvid wrote: > In configure.in, why is it > LIBFLTK_LIBS=`fltk2-config --use-images --ldflags` > if we use the system png/jpeg/etc. libraries and not > the fltk ones? I just tried removing the --use-images > argument, and everything still works for me. Probably because that way it worked with an older version. Does the generated binary size change? Or is there a change with ldd? If the button icons load OK, and the file chooser works, there should be no problems. Those widgets *may* need the internal image handling (but I don't know for sure). -- Cheers Jorge.-

Jan. 6, 2011

[patch]: more spring cleaning of configure.in

by onepoint＠starurchin.org

Time to retire some more obsolete autoconf macros. See [1] for details. 1: Replace AC_CANONICAL_SYSTEM with AC_CANONICAL_TARGET . 2: Replace AC_ERROR with AC_MSG_ERROR . 3: Replace AC_TRY_COMPILE with AC_COMPILE_IFELSE / AC_LANG_PROGRAM . This doesn't break for me, but it affects some host-dependent parts of configure.in . It would be good to know that this works on hosts with unusual socket / iconv library routines. 4: Replace AC_TRY_LINK_FUNC with AC_LINK_IFELSE / AC_LANG_CALL . This only affects target OSes *other* than linux, solaris, osf1 and minix. Can anyone test on such a thing? 5: Indentation tweak for consistency. Regards, Jeremy Henty [1] http://www.gnu.org/software/autoconf/manual/html_node/Obsolete-Macros.html#…

Jan. 5, 2011

configure.in

by corvid＠lavabit.com

In configure.in, why is it LIBFLTK_LIBS=`fltk2-config --use-images --ldflags` if we use the system png/jpeg/etc. libraries and not the fltk ones? I just tried removing the --use-images argument, and everything still works for me.

Jan. 5, 2011

[patch]: more configure.in cleanups

by jcid＠dillo.org

On Wed, Jan 05, 2011 at 08:24:58AM +0000, Jeremy Henty wrote: > On Tue, Jan 04, 2011 at 07:12:34PM -0300, Jorge Arellano Cid wrote: > > On Tue, Jan 04, 2011 at 07:01:24PM +0000, Jeremy Henty wrote: > > > On Sat, Jan 01, 2011 at 11:13:10AM +0000, Jeremy Henty wrote: > > > > > > Bump? I have one upvote from corvid, what do the other devs think? > > > (If nothing else I'd like to fix the "AC_ARG_PROGRAM was called before > > > AC_CANONICAL_TARGET" warning, since it was my fault!) > > > > When a simple patch doesn't work as expected, there's an > > excellent excuse for a cleanup around it. ;-) > > > > My vote is: go ahead quickly! > > OK, done! It works for me. Now let's see what the list says. -- Cheers Jorge.-

Jan. 5, 2011

[patch]: more configure.in cleanups

by onepoint＠starurchin.org

On Tue, Jan 04, 2011 at 07:12:34PM -0300, Jorge Arellano Cid wrote: > On Tue, Jan 04, 2011 at 07:01:24PM +0000, Jeremy Henty wrote: > > On Sat, Jan 01, 2011 at 11:13:10AM +0000, Jeremy Henty wrote: > > > > Bump? I have one upvote from corvid, what do the other devs think? > > (If nothing else I'd like to fix the "AC_ARG_PROGRAM was called before > > AC_CANONICAL_TARGET" warning, since it was my fault!) > > When a simple patch doesn't work as expected, there's an > excellent excuse for a cleanup around it. ;-) > > My vote is: go ahead quickly! OK, done! Regards, Jeremy Henty

Jan. 5, 2011

Not to name dillo 1.3 & not to drop fltk 2.0 support

by rogerx.oss＠gmail.com

On Wed, Jan 05, 2011 at 12:30:22AM +0000, corvid wrote: >Roger wrote: >> fltk-3.0 is the next, hopefully very soon to be released stable version. > >Is anything still going on with 3.0? It seems like I haven't heard anything >about it for some time now... OOPS! My bag. I meant fltk-1.3 is the next version. (... dumb typos... wish God would make them disappear.) But, while we're on the topic of fltk-3.0 version, from what I read on the fltk website, 3.0 is the future version planned to incorporate 2.0 changes from the earlier 1.0 branch, if they aren't already incorporated to 1.* versions. (I'm no expert on fltk/dillo, just trying to correctly relay what I read.) -- Roger http://rogerx.freeshell.org/

Jan. 5, 2011

Not to name dillo 1.3 & not to drop fltk 2.0 support

by corvid＠lavabit.com

Roger wrote: > fltk-3.0 is the next, hopefully very soon to be released stable version. Is anything still going on with 3.0? It seems like I haven't heard anything about it for some time now...

Jan. 5, 2011