<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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@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.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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>Hi Curtis,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Great to hear from you, feel free to reply just to the list as I am already subscribed. I made a page here: <a href="http://wiki.imagej.net/Android"><span style='color:windowtext'>http://wiki.imagej.net/Android</span></a> where I will populate it in the future with some details. Let me mention your specific good ideas:<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>>Did you try to build the code as-is<o:p></o:p></p><p class=MsoNormal>Yes, I’m down from an original 8000 compilation errors in basic ImageJ to 3000 by writing wrappers to map Java AWT components to basic Android ones. They are very similar, but some incompatibilities makes totally as-is ImageJ difficult, and ImgLib impossible, so I have:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>(or minimally modified) for use with Dalvik?<o:p></o:p></p><p class=MsoNormal>Yes, to a limited extent it is working with ImgLib, making Maven very appealing because the extensive dependency use makes it easy to see what I have working. So I have also tried: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> Did you try the Maven Android plugin (<a href="https://github.com/jayway/maven-android-plugin" target="_blank">https://github.com/jayway/maven-android-plugin</a>)?<o:p></o:p></p><p class=MsoNormal>Yes, but I actually found that I had to substantially un-mavenize ImgLib to do the actual programming. This is mostly because I like to use the Eclipse debugger, frequently going across dependencies in figuring out bugs. Understanding how to get this to work better with Maven is probably a point where I would be interested in showing you what I’m doing and seeing ideas for improvement in workflow on my end. Maybe we will have this chance at the conference.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> Did you think about creating an HTML5/Javascript frontend to an ImageJ server, for cross-platform mobile support?<o:p></o:p></p><p class=MsoNormal>This is something I saw a lot of people doing at a recent medical imaging conference, but not specifically for mobile support (but that is a reasonable next step). Do you know of any examples of just general-purpose applications that have done this for cross-platform mobile use?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>Or compile from .class to .dex? <o:p></o:p></p><p class=MsoNormal>That is the goal, but I don’t think there is a way around it without resolving the problems I’ve mentioned above. I’m happy to hear any ideas you have (off-list or on).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-Justin<o:p></o:p></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 style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><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"'> ctrueden.wisc@gmail.com [mailto:ctrueden.wisc@gmail.com] <b>On Behalf Of </b>Curtis Rueden<br><b>Sent:</b> Friday, September 21, 2012 12:44 PM<br><b>To:</b> Senseney, Justin (NIH/CIT) [E]<br><b>Cc:</b> ImageJ Developers<br><b>Subject:</b> ImageJ on Android talk<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Justin,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I hope things are going well with you. I am writing regarding your talk on porting ImageJ to the Android platform for the ImageJ conference next month. It is something I regret not having time to investigate more, so I am happy that you explored it.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>From your abstract (<a href="http://imagejconf.tudor.lu/program/doku.php?id=:program:presentations:justin_senseney1804285318">http://imagejconf.tudor.lu/program/doku.php?id=:program:presentations:justin_senseney1804285318</a>), it sounds like you encountered quite a few difficulties. Anything you would care to discuss prior to the conference? Leaving the door open for mobile support has been a major design goal of ImageJ2, so if there are roadblocks it would be good to hear about them, to make any corrections in the architecture sooner rather than later.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Moreover, in general, we would be very interested to hear details of your approach. Did you try to build the code as-is (or minimally modified) for use with Dalvik? Or compile from .class to .dex? Did you try the Maven Android plugin (<a href="https://github.com/jayway/maven-android-plugin" target="_blank">https://github.com/jayway/maven-android-plugin</a>)? Did you think about creating an HTML5/Javascript frontend to an ImageJ server, for cross-platform mobile support?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>These are all directions we would love to see explored. You are more than welcome to discuss your findings on this mailing list, and/or post technical details on the ImageJ2 wiki (<a href="http://wiki.imagej.net/ImageJ2">http://wiki.imagej.net/ImageJ2</a>).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Curtis<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>