Hi Tiago,<br><br>Thanks very much for pushing the documentation issue, and sorry for the long delay in my reply.<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
- Which plans do you have for the IJ2 documentation?<br></blockquote>
<br>There will be an increasing focus on documentation during the three-month beta period later this fall. For now we are still pushing to make everything work as it should.<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
- Could the guide be extended to ImageJ2? (A new chapter?) Or should it cease<br>
with 1.45 and a new one be written for IJ2? In which modality then?<br></blockquote>
<br>I agree with Gabriel that perhaps many parts of the guide will be directly applicable to IJ2, at least temporarily, but it will definitely need major updates.<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
_ I think self-contained user documentation is very important. I know some of<br>
you would prefer a wiki-like user guide. My experience however tells me<br>
that average lay users don't. My opinion is that self-contained documents<br>
are key to non-power users and wikis best suitable for advance usage and<br>
How-Tos.<br></blockquote>
<br>I think this is an important observation. What I would like to see is the best of both worlds: exposing the online wiki documentation from within the software itself, as built-in help. I also agree with your goal of creating a system that can generate a self-contained document such as a PDF. We will be in touch with you more later about deploying that system for IJ2. And we will certainly be able to help you with the actual documentation effort, when the time comes.<br>
<br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
- It would be great if IJ2 users had more visible access to documentation.<br>
Something like Fiji's "Help on Menu Item" would be great.<br></blockquote>
<br>Right. Except that we will need to be more diligent about documenting every command.<br><br>Another possibility is for the plugins themselves to allow for self-documentation. We have this a bit already with a "description" field for every input parameter, as well as for the plugin itself, but it could perhaps be fleshed out more. Also might be good to add a URL link field.<br>
<br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">
- BTW, from a strictly usage point of view, IJ has some big flaws (e.g., the<br>
notorious interpretation of binary images via the blackBackground option).<br>
It would be great if IJ2 featured more user-friendliness.<br></blockquote>
<br>Well, we will do what we can, but people tend to disagree on what is "friendly." In the case of the black background option, we plan to eliminate that option. If you want things to look inverted, you can just invert the LUT. But maybe there will be some complaints about it—we'll see. Another example is RGB color vs. 3-channel 8-bit unsigned integer composite images: they display the same and are fairly redundant, so we are eliminating the RGB color mode, except for legacy purposes.<br>
<br>-Curtis<br><br><div class="gmail_quote">On Sun, Jun 5, 2011 at 9:57 PM, Tiago Ferreira <span dir="ltr"><<a href="mailto:tiago.ferreira@mail.mcgill.ca">tiago.ferreira@mail.mcgill.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
I'm also very excited to see the 3rd alpha released.<br>
I imagine that with so much to do, user documentation is probably the last<br>
thing you want to think about right now but nevertheless I would like to<br>
raise this issue here.<br>
<br>
I've been working on a new revision of the ImageJ Guide. I've been struggling<br>
to create a "publishing system" that could output simultaneously PDF, HTML<br>
and booklet versions. It is far from perfect but its getting there.<br>
A working draft is here (it is rather slow on dropbox):<br>
<br>
<<a href="http://dl.dropbox.com/u/136719/guide/index.html" target="_blank">http://dl.dropbox.com/u/136719/guide/index.html</a>><br>
<br>
It would great if it could be extended to ImageJ2, but I would need guidance.<br>
I've just compiled IJ2 on my laptop and felt overwhelmed only by skimming<br>
some source files. Documenting IJ1 was hard, documenting IJ2 seems already<br>
impossible, but Johannes seems to think it is doable :)<br>
<br>
Questions:<br>
- Which plans do you have for the IJ2 documentation?<br>
- Could the guide be extended to ImageJ2? (A new chapter?) Or should it cease<br>
with 1.45 and a new one be written for IJ2? In which modality then?<br>
<br>
Suggestions/Comments:<br>
_ I think self-contained user documentation is very important. I know some of<br>
you would prefer a wiki-like user guide. My experience however tells me<br>
that average lay users don't. My opinion is that self-contained documents<br>
are key to non-power users and wikis best suitable for advance usage and<br>
How-Tos.<br>
<br>
- It would be great if IJ2 users had more visible access to documentation.<br>
Something like Fiji's "Help on Menu Item" would be great.<br>
<br>
- BTW, from a strictly usage point of view, IJ has some big flaws (e.g., the<br>
notorious interpretation of binary images via the blackBackground option).<br>
It would be great if IJ2 featured more user-friendliness.<br>
<br>
Best,<br>
<br>
-tiago<br>
_______________________________________________<br>
ImageJ-devel mailing list<br>
<a href="mailto:ImageJ-devel@imagejdev.org">ImageJ-devel@imagejdev.org</a><br>
<a href="http://imagejdev.org/mailman/listinfo/imagej-devel" target="_blank">http://imagejdev.org/mailman/listinfo/imagej-devel</a><br>
</blockquote></div><br>