fltk4D is a binding to the FLTK gui library. http://dronten.googlepages.com/fltk4d

Micke wrote:

> fltk4D is a binding to the FLTK gui library.
> http://dronten.googlepages.com/fltk4d

If you make a few adjustments* to it, it will also
work with GDC/rebuild - and with Mac OS X (Carbon):
http://www.algonet.se/~afb/d/fltk4d_helloworld_mac.png
http://www.algonet.se/~afb/d/fltk4d_table_mac.png

* A minor change to give the full module name for
"FLTK.eventKey", plus avoid linking to X11 on Mac.

You also want to avoid including "fltk4d.cxx" in
the FLTK libraries, but put them in a separate lib.
That way users can use the standard fltk libraries,
and just add two fltk4d libraries (one C++, one D)

Otherwise FLTK is looking "as lovely as ever" ;-)
And as opposed to FOX, it _is_ native on the Mac.
I'll send you a patch, that will build Universal
binaries and use `fltk-config` for the libraries...

--anders


PS: You know there is a native D port of FLTK, yes ?
http://svn.easysw.com/public/fltk/fltk/branches/branch-D-1.1/

PPS: As you suspected, it requires the 1.1.8 fltk -
recommend making it work with the stable version ?

Micke wrote:
> fltk4D is a binding to the FLTK gui library.
> http://dronten.googlepages.com/fltk4d

Any thoughts about adding a more D-ish callback system?  Having delegates in the language but requiring static function callbacks is unfortunate.

--bb

Micke wrote:
> fltk4D is a binding to the FLTK gui library.
> http://dronten.googlepages.com/fltk4d

You should add your library to the Wiki4D gui libs page:
http://www.prowiki.org/wiki4d/wiki.cgi?GuiLibraries

And if you have any advice on writing wrappers, put it here:
http://www.prowiki.org/wiki4d/wiki.cgi?WrappingCxx
(I just added a link to your project, but a detailed advice of how to go about implementing the "3-step" plan for wrapping is what I'm after.)

--bb

Nice!

There was a lot of talk about making FLTK 2.0 compatible with D, but that fizzled out ... glad to see this instead. FLTK is a great package

- Kris

"Micke" <dronten@gmail.com> wrote in message news:fdou3k$7a0$1@digitalmars.com...
> fltk4D is a binding to the FLTK gui library. http://dronten.googlepages.com/fltk4d

Anders F Björklund wrote:
> You also want to avoid including "fltk4d.cxx" in
> the FLTK libraries, but put them in a separate lib.
> That way users can use the standard fltk libraries,
> and just add two fltk4d libraries (one C++, one D)
Yeah, I had thought about it but maybee later on.

> PS: You know there is a native D port of FLTK, yes ?
> http://svn.easysw.com/public/fltk/fltk/branches/branch-D-1.1/
Yes but I think it have slowed down considerably.

> 
> PPS: As you suspected, it requires the 1.1.8 fltk -
> recommend making it work with the stable version ?
No, as they have been talking about getting 1.1.8 out of the door for a long time. Anyway, it should be more stable than 1.1.7.

Bill Baxter wrote:

> Any thoughts about adding a more D-ish callback system?  Having delegates in the language but requiring static function callbacks is unfortunate.
I'm not sure I'm following you here. The static callbacks are for c++ to connect to D. I haven't found out a way to do it any other way.

Bill Baxter wrote:
> You should add your library to the Wiki4D gui libs page:
> http://www.prowiki.org/wiki4d/wiki.cgi?GuiLibraries
Done.

Micke wrote:
> Bill Baxter wrote:
> 
>> Any thoughts about adding a more D-ish callback system?  Having delegates in the language but requiring static function callbacks is unfortunate.
> I'm not sure I'm following you here. The static callbacks are for c++ to connect to D. I haven't found out a way to do it any other way.

Ok, maybe I'm just confused then.  In your examples page I see the Valuator demo uses a non-static callback.  So the D callbacks *don't* have to be static then?

--bb

Micke wrote:

>> PPS: As you suspected, it requires the 1.1.8 fltk -
>> recommend making it work with the stable version ?
> No, as they have been talking about getting 1.1.8 out of the door for a long time. Anyway, it should be more stable than 1.1.7.

I was sorta thinking making it work with *both*, using conditionals.
But as long as you're using your own static copy, it doesn't matter.

It's just when you're trying to use the system version of the fltk
packages, you are more likely to find "1.1.7" than "1.1.x-r5940" ?

--anders