>On 6/23/05, Jose Manrique Lopez de la Fuente <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:jsmanrique@gmail.com">jsmanrique@gmail.com</a>> wrote:<br>
>> 2005/6/23, Kalle Vahlman <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:kalle.vahlman@gmail.com">kalle.vahlman@gmail.com</a>>:<br>
>> > I wonder why one would want to bolt a toolkit on top of another one?<br>
>> > Does FLTK have some overly fantastic widgets that Gtk is missing?<br>
>><br>
>> I think that main advantage of FLTK is the 'L? in its name: Light.<br>
><br>
>Yes, and as I pointed out, if it's ported to use gtk it won't be just that.<br>
>> Do we really need another GUI environment in such device? That's the<br>
>> question.<br>
>Well, you'd have to rewrite the whole UI if you want to take advantage<br>
>of FLTK, since the UI is all gtk.<br>
>So to use FLTK, install the rootstrap, remove any gtk-related packages<br>
>and start porting/coding :)<br>
<br>
FLTK has its own UI and the demo fltk apps that I tried looked pretty<br>
nice in the scatchbox environment. At a minimun it would really just need<br>
a way to integrate the application icon to be usable.<br>
Calling gtk routines from a fltk app would only increase the exe size if <br>
they were statically linked. <br>
Could someone please provide a link to the hildon code (is it available?)<br>
so I can investigate this further. <br>
Thanks<br>
Chris<br>
<br>
<br>
<br>
<br>