iTool Example [message #42032] |
Mon, 13 December 2004 09:41  |
p.sommer
Messages: 20 Registered: April 2004
|
Junior Member |
|
|
Group,
In a recent thread, there was some discussion about how I used the
iTool framework to build a data acquisition (DAQ) client. I was
expressing some positive experiences having used the iTools for this
project which was challenged by some. At the time, I offered to reform
the example so that the user community could take a look at a fully
featured, user defined iTool. It is now available for anyone
interested:
http://www.rsinc.com/codebank/search.asp?search=category& ;product=IDL&catid=43
Now, if I may put my sales hat on, in addition to providing an
excellent platform for rapid application development, I also made some
mention about making sure the problem fit the tool which was also
challenged. In short, what I meant by that statement was to try using
an existing iTool [iPlot, iContour, iSurface, iVolume, iImage or iMap]
on similar data that one needs to support to make sure the framework
can support it. For example, since the iTools are based on IDL's
Object Graphics, much of the data needs to reside in physical memory to
maintain interactivity. Without going into too much detail, I think
you power users know what I mean.
Someone also asked for more detail for why one would want to start
using the iTool framework at all for building new tools. My rational
is that the framework takes care of a lot of important details like
setting up views, operators, manipulators, file I/O, property sheets,
annotation, zoom control, undo/redo buffer and now with 6.1, macro
recording. It's just very nice to have all this taken care of so I can
focus on the elements that make the tool truly unique as apposed to
spending hours and hours building up the basic functionality end users
have come to expect from a nice piece of software. Okay...enough said.
Go easy on me as I am learning right along with you. Just hope the
example helps someone, somewhere.
-Paul
|
|
|