<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi HongKee, no worries on the delayed replies. It kinda matches the pace at which I’m able to get to these things anyway.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I found the section on the GUI, and I’ll take a look at those details as things progress.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If you happen to draw or create and graphical representations of the code on your travels through its overhaul I’d be very interested in seeing those. I think
a block diagram of the basic steps needed to perform an acquisition might help us to implement the different and varying aspects of the MMCore for multiple hardware setups. Just a thought, if that’s something that might help for you.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’ll keep you posted. Thanks for your time and your help.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Neil<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> HongKee Moon [mailto:moon@mpi-cbg.de]
<br>
<b>Sent:</b> Monday, February 29, 2016 8:15 AM<br>
<b>To:</b> Anthony, Neil<br>
<b>Cc:</b> openspim@openspim.org<br>
<b>Subject:</b> Re: SPIM Acquisition Java plugin<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear Neil,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">First of all, I have to say that I am so sorry for the late reply.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am trying to explain as possible as I can.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Feb 18, 2016, at 6:31 PM, Anthony, Neil <<a href="mailto:nantho2@emory.edu">nantho2@emory.edu</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi HongKee, I hope the code is treating you well.<br>
<br>
Sorry for the delay; I've been pulled in a couple of different directions recently, but have been coming back to the plugin code a little more now. For completeness, I've cc'd the openspim list, and for reference our last conversation was part of a thread
called "Why do SPIM and Micro-Manager use different TIFF packages?" that I hijacked at the start of the year.<o:p></o:p></p>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><br>
Thanks for the details on SPIMTestDrive section of the code. It's great to now have the option to step through and figure things out. One thing that I'm not sure about is the location of the code that builds the GUI form. In other code I see the option to
show the design of the form in Netbeans, but I don't see that here. Is the GUI programmatically created without IDE assistance? If so, how hard would it be to pull that into a form design type file in Netbeans? It really speeds up my understanding of the
code if I can quickly reference the buttons and sliders etc. in the exploration and debug stages.<o:p></o:p></p>
</div>
</div>
</blockquote>
<p class="MsoNormal">Unfortunately, SPIMAcquisition builds GUI programmatically and lack of comments on this part. Personally, I would like to remove all the unnecessary GUI parts except “Acquisition”. However, I cannot check whether all those things are still
being used by users or not, and there are differently associated tasks(video recording, etc) depending on which tab selected. My idea to handle your case is that you can build your own Tab including your controls or add “Customize” button to open your customized
panel by “clicking” event. Then, you can manage to implement your logics there.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
You had previously asked about my direction in the plugin, and a large part of it would be to make the interface more user friendly and graphical. My setup will be part of our core facility and I hope to have researchers here using the software once things
are up and rolling. If the GUI it is more programmatic, could you point me to that structure/code/... and maybe I could start from there.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">The first thing for you to look at is "spim.SPIMAcquisition#initUI()” part, which contains long lines of codes for initializing GUI controls. I tried to make it little bit readable by “//“ and following short description for only small
parts. Let me know if you have complicated codes in the file. I will explain it.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><br>
My second direction would be to add the option of different hardware to the plugin. Would it be possible to bring some sort of modularity to the GUI, that draws from the MM hardware settings and available core options? Alternatively, might it be easier to
add to the multidimensional acquisition panel in MM by including a rotation section? You could then call that panel from the SPIM Acquisition plugin.<o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal">That would be a really good idea if we can bring the modularity from the implemented MM parts and reuse them inside the plugin context. Actually, I have not investigated MM codes enough to be able to judge. However, it would be much nicer
and compact if we can reuse the components from the MM packages. It will involve that I need study MM codes more. It is hard to tell you how much time it could be expected.<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
Sorry for the my somewhat fragmented questions/suggestions. I'm sure it'll make more sense once I get into the details, and I appreciate any pointers you can offer as I get started.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">No problem! I will be always on your side. Please, let me know whenever you have questions/feedbacks regarding SPIMAcquisition plugin. I try to do my best to answer you as much as I can.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">HongKee<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
Thanks in advance for your time.<br>
<br>
Neil<br>
<br>
<br>
________________________________<br>
<br>
This e-mail message (including any attachments) is for the sole use of<br>
the intended recipient(s) and may contain confidential and privileged<br>
information. If the reader of this message is not the intended<br>
recipient, you are hereby notified that any dissemination, distribution<br>
or copying of this message (including any attachments) is strictly<br>
prohibited.<br>
<br>
If you have received this message in error, please contact<br>
the sender by reply e-mail message and destroy all copies of the<br>
original message (including attachments).<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black"><br>
--<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">HongKee Moon<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">Software Engineer<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">Scientific Computing Facility<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">Max Planck Institute of Molecular Cell Biology and Genetics<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">Pfotenhauerstr. 108<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">01307 Dresden<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">Germany<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">fon: +49 351 210 2740<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black">fax: +49 351 210 1689<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black"><a href="http://www.mpi-cbg.de">www.mpi-cbg.de</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>