<br><br><div class="gmail_quote">On Mon, Sep 14, 2009 at 11:37 PM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@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 -<br>
<br>
In my ongoing quest to make MVC reloadable, I've now come to some more interesting dependencies. MorphicExtras-ST80 contains a bunch of classes that relate to running Morphic inside MVC projects. I'm not sure how to deal with this dependencies, here are some proposals for possible directions:<br>
<br>
1) Remove it. I'm not sure if anyone would care. Holler if you do.<br></blockquote><div><br></div><div>Surely this is the sensible option. Perhaps you could confirm by looking at method timestamps but my guess is that this code was used in the initial development of Morphic and now that it is stand-alone this stuff isn't necessary. But I'm talking from a position of deep ignorance. So caveat emptor...</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
2) Move it into a MorphicWIW package that contains both embedded Morphic worlds (currently in MorphicExtras-AdditionalWorlds; would become MorphicWIW-Core) as well as Morphic projects in MVC (would become MorphicWIW-ST80).<br>
<br>
3) Define a set of more generic "MorphicDemos-*" packages that would include MorphicDemos-ST80 and could be used to split out other packages that are obvious candidates (top of my list: the Fabrik remnants, Text-on-Curves, and GeeMail) all of which are fairly self-contained, do not provide a core functionality and are not used anywhere in sight.<br>
<br>
Any preferences? Alternatives?<br>
<br>
Cheers,<br><font color="#888888">
- Andreas<br>
<br>
</font></blockquote></div><br>