[vtkusers] KWWidgets & VTK

[David Cole]

Whatever you're best at. You'll find some tasks are easier when you have
your own C++ class overrides. You can even do *everything* from C++ if you
want, but you'll still need to learn some tcl/tk to understand what's going
on with widget layout and arrangement. 'packing' in tk terminology.
If you build it, check out the KWWidgetsTour example. It's a sampling of all
the different widgets available and how to use them from C++, tcl or python.


On Fri, Aug 29, 2008 at 10:19 AM, Randall Hand <randall.hand at gmail.com>wrote:

> ick.. In that case what's the best way to go when working with VTK &
> KWWidgets?
> * Tcl?
> * Python?
> * Straight C?
>
> ----------------------------------------
> Randall Hand
> Visualization Scientist
> ERDC MSRC-ITL
>
>
> On Fri, Aug 29, 2008 at 9:04 AM, David Cole <david.cole at kitware.com>wrote:
>
>> Yes. It absolutely is. If you glance through the source code for
>> KWWidgets, you will see "Script" calls all over the place that evaluate
>> strings as tcl code. Without that functionality, KWWidgets would not work at
>> all.
>>
>>
>> On Fri, Aug 29, 2008 at 9:43 AM, Randall Hand <randall.hand at gmail.com>wrote:
>>
>>> I've just had a new project handed to me that I think would be ideally
>>> suited for VTK & a very simple GUI, so I thought KWWidgets.  In the
>>> requirements I see Tcl/Tk listed.  Is Tcl/Tk really a _requirement_ for
>>> KWWidgets?  I'll be doing all my development exclusively in C.
>>> ----------------------------------------
>>> Randall Hand
>>> Visualization Scientist
>>> ERDC MSRC-ITL
>>>
>>> _______________________________________________
>>> This is the private VTK discussion list.
>>> Please keep messages on-topic. Check the FAQ at:
>>> http://www.vtk.org/Wiki/VTK_FAQ
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.vtk.org/mailman/listinfo/vtkusers
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20080829/46f2bec4/attachment.htm>