Me:
>> Not quite what you had in mind, you might want to consider looking at
>>
>> Programming: Principles and Practice using C++ by Bjarne Stroustrup
>> (Addison Wesley, 2008, ISBN 978-0321543721)
>>
>> in which he explains how to write GUI applications in C++ and FLTK-1.
>>
>> Obviously he descri
>> Not quite what you had in mind, you might want to consider looking at
>>
>> Programming: Principles and Practice using C++ by Bjarne Stroustrup
>> (Addison Wesley, 2008, ISBN 978-0321543721)
>>
>> in which he explains how to write GUI applications in C++ and FLTK-1.
>>
>> Obviously he describes
Patrick Mc(avery schrieb:
>
>> Maybe it's a better idea, to use a search engine for "c++ for c
>> programmers". FLTK<- C++<- C, so it doesn't make sense, to jump from C
>> to FLTK, but learning C++ makes FLTK very easy.
>
> Perhaps I should have said "introducing FLTK's C++ subset to C
> programmer
On 21.07.2011 08:53, Duncan Gibson wrote:
>> Perhaps I should have said "introducing FLTK's C++ subset to C
>> programmers". If FLTK is using let's say half of C++, then could someone
>> new to C++ start writing FLTK apps sooner by only sticking to the FLTK
>> C++ subset? They could always learn th
> Perhaps I should have said "introducing FLTK's C++ subset to C
> programmers". If FLTK is using let's say half of C++, then could someone
> new to C++ start writing FLTK apps sooner by only sticking to the FLTK
> C++ subset? They could always learn the other have of C++ later, no?
Not quite wha
> Maybe it's a better idea, to use a search engine for "c++ for c
> programmers". FLTK<- C++<- C, so it doesn't make sense, to jump from C
> to FLTK, but learning C++ makes FLTK very easy.
> ___
> fltk mailing list
> fltk@easysw.com
> http://lists.easysw
Patrick Mc(avery schrieb:
> Maybe once I get up to speed I could write a tutorial, "FLTK for C
> programmers", does that sound like a good idea?
Maybe it's a better idea, to use a search engine for "c++ for c
programmers". FLTK <- C++ <- C, so it doesn't make sense, to jump from C
to FLTK, but l
Hi Ian, Hi List
Indeed I should have referred to functions of a class as methods.
It looks to me that someone coming from ANSI C needs to learn classes
with inheritence and overloading. Actually the class stuff is not going
to be so hard as I have experience with some dynamic languages, so it
> FLTK is tiny(and fast) I am hoping that if I stick to the smallest
> possible subset of C++ then I will be able to handle it's
> native API and
> if I want to "look under the hood" then the small code base
> would make
> this a reasonable thing to do.
>
> Could anyone please correct or add
Thanks Matthias! Thanks Greg!
Greg, you have a lot of tutorial information on the net, thanks very much.
I have fooled around with glade a bit, fluid seems really nice. I like
that it generates C++ code rather then XML.
I hope I can catch up and one day do some tutorials of my own :)
-Patrick
On 07/19/11 14:04, Patrick Mc(avery wrote:
> I don't really know much about the standard library, friend functions,
> overloading and exceptions but should I care? If I understand the C++
> subset that deals with the above code am I pretty much ready good to go?
Many folks in your positi
On 19.07.2011, at 23:04, Patrick Mc(avery
wrote:
> Some C++ features are already not used:
> templates, exceptions, RTTI, namespaces
That is correct. None of these are used in FLTK. This makes it possible to
compile FLTK on broken compilers and small embedded systems. This does not mean
tha
Hi Everyone
I am just an enthusiast programmer. I have been using dynamic languages
for years now and recently I have started to write reasonable C
programs. I would like to be able to create GUIs as well. I know I could
use GTK and just stick with C but if I ever wanted to "look under the
hoo
13 matches
Mail list logo
