Hi Dscho,<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>I wonder whether it'd make sense to merge the tutorials into a<br>
subdirectory of our main repository? That way, we could share code between<br>tutorials and regression tests more easily...</blockquote><div><br></div><div>There are pros and cons. The reason I made a separate repository is to prove that you do not need to check out the ImageJ2 source code in order to easily work with ImageJ2. This more closely models what external developers will do: create a new project with dependencies on ImageJ2 artifacts and go from there.</div>
<div><br></div><div>That said, I am not necessarily against merging the tutorials back in, if it would make our lives a lot easier. Could you give an example of such code sharing in action?</div><div><br></div><div>Regards,</div>
<div>Curtis</div><div><br><br><div class="gmail_quote">On Tue, Aug 7, 2012 at 12:01 PM, Johannes Schindelin <span dir="ltr"><<a href="mailto:Johannes.Schindelin@gmx.de" target="_blank">Johannes.Schindelin@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Curtis,<br>
<br>
I wonder whether it'd make sense to merge the tutorials into a<br>
subdirectory of our main repository? That way, we could share code between<br>
tutorials and regression tests more easily...<br>
<br>
This comes from my experience of the Script Editor where the Templates<br>
were compiled all the time so we caught API breakages that way...<br>
<br>
Ciao,<br>
Dscho<br>
</blockquote></div><br></div>