> > I more worried about how we embrace the future of GUI design -
> > touchscreens, gestures, multi-touch, etc.
>
> Yes, I'm sure the day will come when I'll need
> "pinch to zoom" and two-finger-scroll in my apps..
I got the touchpad thing for my new Mac (rather than the Wacom tab
On 07/12/11 05:49, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>
> FWIW, for future versions, I am much less worried about whether fltk
> should use STL and C++0x extensions internally (you can of course use
> any extensions you like in your own code already...)
>
> I am worried about how we embra
On 12.07.2011, at 14:49, MacArthur, Ian (SELEX GALILEO, UK) wrote:
> So for now, let's get 1.3 stable, get fltk3 baselined so we have
> something to work on, then worry about what we *really* need to fix
> next.
;-)
Yes, well said!
___
fltk mailing li
My conservative view:
On 12/07/2011 12:29, Piotr Beling [qwak] wrote:
>
> We will also have new C++ (0x) standard which gives in my opinion new
> possibilities in constructing API.
-1 Please don't. It will take years when all/most compilers will support that
new features properly.
>
> That i
FWIW, for future versions, I am much less worried about whether fltk
should use STL and C++0x extensions internally (you can of course use
any extensions you like in your own code already...)
I am worried about how we embrace the future of GUI design -
touchscreens, gestures, multi-touch, etc.
I have read thread about FLTK 3.0 (I no answer in that thread because
most of my mail includes completely new proposition).
I agree that one API for FLTK1/2 would be a great product at this moment
but I also think that in longer time perspective it is not the best idea
to invest time to develop
6 matches
Mail list logo
