Posted by
Joachim Wesner on
Mar 16, 2006; 7:20pm
URL: http://imagej.273.s1.nabble.com/diameter-automatic-calculation-tp3703389p3703392.html
Bob,
I think you are right.
As I'm still mostly a "procedural" programmer and not an OO one, it seems
best/fastest to me for getting to a working version of a more complex
plugin: Extract the needed FHT routines (that directly work with arrays
etc.) from the sources and base the plugin on that code, instead of
immediately dealing with image processors whose intermediate images won´t
be displayed anyhow!
Later one could cleanup the code and convert it to use straight IPs and
FHTs.
Joachim
Robert Dougherty
<
[hidden email] An:
[hidden email]
> Kopie: (Blindkopie: Joachim Wesner/DEWET/LMSCentral/Leica)
Gesendet von: Thema: Re: "Unclean code" in FFT class
ImageJ Interest
Group
<
[hidden email]
.GOV>
16.03.2006 19:23
Bitte antworten
an ImageJ
Interest Group
Jochim,
One way to deal with FHTs in ImageJ plugins is illustrated in FHT 3D. My
solution was to hack some source code from ImageJ. Not very OO, but
effective. It does seem like it might be useful if FHT.rc2DFHT and
FHT.dfht3 were available as public static methods.
Bob
Robert P. Dougherty, Ph.D.
President, OptiNav, Inc.
Phone (425) 467-1118
Fax (425) 467-1119
www.optinav.com
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit
http://www.messagelabs.com/email
______________________________________________________________________