| new iTools [message #36113] |
Fri, 15 August 2003 06:24 |
btt
Messages: 345
Registered: December 2000
|
Senior Member |
|
|
Hello All,
I have been tinkering with the new iTools. I am impressed (maybe overwhelmed is
a better word for it) by all I see. I have been able to add a simple data
operation tool to the operation menu without out too much trouble. But the
whole shebang raises a couple of questions for me. I am interested in knowing
what some of the experts and/or beta-testers (who have had a head start) are
thinking...
(1) It appears that each data operation object performs just one task - that is,
it can only have one EXECUTE method. I think this means that if I wanted to add
two similar operations(edge detectors SOBEL and ROBERTS for example), I would
build two different data operation objects (ala myToolitOPSOBEL__Define and
myToolitOPROBERTS__Define) each with its own EXECUTE method. Am I interpreting
this properly? If not, how does one bundle similar functionality in one object?
(2) I have been in the habit of building a data processing object and then
creating a companion GUI-based object that inherits from the data processor.
This arrangement permits me to interactively setup parameters for data
processing - but later do the data processing in a non-interactive fashion
(command line, batch file, etc.) Does the iTool paradigm fit this model? Will
I be able to access the underlying data processing hierarchy in an objecty-way
without the interactive GUI? If so, how do I access it?
Thanks,
Ben
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
