• Micke (2/2) Dec 19 2007 fltk4d is a wrapper for the FLTK gui library.
• Kenny B (4/6) Dec 19 2007 dude, that's really cool. Major props to the fltk guys too for making
• Dejan Lekic (3/4) Dec 19 2007 Thanks, AFAIK two FLTK developers are also great D believers - me and
• John Reimer (4/10) Dec 19 2007 Is the D port of FLTK still active? I believe Matthias was working on
• Dejan Lekic (3/3) Dec 20 2007 No, but I am planning to begin working on a D port of FLTK2 in the
• Graham St Jack (3/6) Dec 20 2007 That's great news - D really needs a native GUI library. Bindings just
• Micke (6/10) Dec 20 2007 Its lot of work and you would have to keep track of all changes to the
• Dejan Lekic (7/9) Dec 21 2007 That is not a problem because I do those C++ changes in FLTK2 tree as
• Bill Baxter (8/19) Dec 21 2007 I will! wxWidgets wxWidgets wxWidgets!
• Micke (10/16) Dec 22 2007 I have never used FLTK2 so I cant do any comments about it.
• Dejan Lekic (2/2) Dec 19 2007 As i said previously - great work!
• Micke (4/7) Dec 20 2007 Cheers!
• Georg Wrede (35/37) Dec 30 2007 Nice!!

Micke <dronten gmail.com> writes:

fltk4d is a wrapper for the FLTK gui library.
http://dronten.googlepages.com/fltk4d

Kenny B <funisher gmail.com> writes:

Micke wrote:
 fltk4d is a wrapper for the FLTK gui library.
 http://dronten.googlepages.com/fltk4d

dude, that's really cool. Major props to the fltk guys too for making
the GUI so easy. This makes me want to program gui apps now :P

I need to start thinking of something... hmm

Dejan Lekic <dejan.lekic gmail.com> writes:

 dude, that's really cool. Major props to the fltk guys too for making

Thanks, AFAIK two FLTK developers are also great D believers - me and 
Matthias.

Btw. Mike, great work!

John Reimer <terminal.node gmail.com> writes:

Dejan Lekic wrote:
 dude, that's really cool. Major props to the fltk guys too for making

 
 Thanks, AFAIK two FLTK developers are also great D believers - me and 
 Matthias.
 
 Btw. Mike, great work!


Is the D port of FLTK still active?  I believe Matthias was working on 
it for awhile.

-JJR

Dejan Lekic <dejan.lekic gmail.com> writes:

No, but I am planning to begin working on a D port of FLTK2 in the 
middle of January 2008. I estimate it will take 2 weeks for the first
release to come out.

Graham St Jack <Graham.StJack internode.on.net> writes:

On Thu, 20 Dec 2007 17:30:21 +0000, Dejan Lekic wrote:

 No, but I am planning to begin working on a D port of FLTK2 in the
 middle of January 2008. I estimate it will take 2 weeks for the first
 release to come out.

That's great news - D really needs a native GUI library. Bindings just 
aren't the same.

Micke <dronten gmail.com> writes:

Dejan Lekic wrote:
 
 No, but I am planning to begin working on a D port of FLTK2 in the 
 middle of January 2008. I estimate it will take 2 weeks for the first
 release to come out.

Its lot of work and you would have to keep track of all changes to the 
2.0 (C++) tree. One thing I did think about was to rip out all the low 
level platform code, clean it up and convert it to D and then create new 
widgets in D from scratch. I'm not that found of the FLTK C++ code, it 
is a little bit messy.

Dejan Lekic <dejan.lekic gmail.com> writes:

 Its lot of work and you would have to keep track of all changes to the 
 2.0 (C++) tree.

That is not a problem because I do those C++ changes in FLTK2 tree as 
well (as said earlier, I am one of people who work on the FLTK project).

Speaking of messy FLTK code... I have seen much more messy code in some 
more popular GUI toolkits, I do not want to name them here because I 
have some respect for what they did.

At the end, I know couple of very bright people from D community who use 
FLTK, and I expect their help with this.

Bill Baxter <dnewsgroup billbaxter.com> writes:

Dejan Lekic wrote:
 
 Its lot of work and you would have to keep track of all changes to the 
 2.0 (C++) tree.

 That is not a problem because I do those C++ changes in FLTK2 tree as 
 well (as said earlier, I am one of people who work on the FLTK project).
 
 Speaking of messy FLTK code... I have seen much more messy code in some 
 more popular GUI toolkits, I do not want to name them here because I 
 have some respect for what they did.

I will!  wxWidgets wxWidgets wxWidgets!
Still a great piece of software, but it has definitely accumulated a lot 
of crazy crufty incomprehensible code over the years.

 At the end, I know couple of very bright people from D community who use 
 FLTK, and I expect their help with this.

My gripes with FLTK were always 1) ugly and 2) callbacks suck in C++.  I 
think 1) is addressed by FLTK2 with theming support and hopefully 2) 
will be addressed by using something like std.signal in the D port.

--bb

Micke <dronten gmail.com> writes:

Dejan Lekic wrote:

 That is not a problem because I do those C++ changes in FLTK2 tree as 
 well (as said earlier, I am one of people who work on the FLTK project).

Yes I know, I have been following fltk list for years.

 
 Speaking of messy FLTK code... I have seen much more messy code in some 
 more popular GUI toolkits, I do not want to name them here because I 
 have some respect for what they did.

I have never used FLTK2 so I cant do any comments about it.
A couple of issues I have with FLTK1 is that I have found class code 
splitted into more then one file. And the box drawing styles for 
example, some are enums and some are functions. And there are more. So 
there are some strange code in there.

And I really really dont like how the code is formatted. But this is a 
personal issue I have and as such quite meaningless to discuss.

But it is small, portable, stable and fast, and that I do like :)

Dejan Lekic <dejan.lekic gmail.com> writes:

As i said previously - great work!
Btw. are you going to do a wrapper for the FLTK2 perhaps?

Micke <dronten gmail.com> writes:

Dejan Lekic wrote:
 
 As i said previously - great work!
 Btw. are you going to do a wrapper for the FLTK2 perhaps?

Cheers!
Duh, perhaps some day.
I wont think about until it is 100% stable.

Georg Wrede <georg nospam.org> writes:

Micke wrote:
 fltk4d is a wrapper for the FLTK gui library.
 http://dronten.googlepages.com/fltk4d

Nice!!

Any /actual/ user experiences?
Preferably from "unrelated users"? Anybody?

Like, was it easy to "get running", was it easy to try it out with your 
own test case, would you recommend it to others (and if so, for 
tinkering or for serious corporate programming, as in skipping Java or 
.NET)?

The FLTK pages on Lua are awesome, and give an impression of trivially 
easy usage and next to none overhead (as measured in programmer hours 
wasted both to the learning curve and at actual work). How does this 
compare to them?

---

Why am I asking? Well, recently I sold the possibly first serious 
factory automation solution in D, and now I have been approached by a 
party who want me to make a similar GUI app, but more complex.

I'd love to do it in D, but seeing this is a long-term project with a 
(well)paying customer with long-term commitment in mind, I'm hard put to 
not recommend me doing it in Delphi. (Comprehensive GUI library 
(actually multi platform), RAD tools, long-term (historically proven!!) 
commitment from the language vendor, obvious commitment to backwards 
compatibility in new versions, amazing productivity with their source 
editor, advanced debugging, two-way UML support, unit testing, and last 
but not least: serious and long term commitment to programmers who've 
invested in learning Their Way. In other words, (as opposed to Windows 
or C(++), you don't have to forget half of what you know at each major 
release) respect for the customer.

Sure, I could test fltk4d right now, (and all the other alternatives 
too) for a coulpe of weeks each, but I'm on a tight schedule here for 
the answer, and I trust other folks may have better insight than I could 
gather in the given time.  :-(

---

PS, /technically/ this is the wrong forum for this kind of questions. My 
appologies. OTOH, serious answers to this post would be more in the 
spirit of this NG than d.D (or d.D.learn).