<br><br><div class="gmail_quote">2009/3/28 Tim Nash <span dir="ltr"><<a href="mailto:thedagdae@gmail.com">thedagdae@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I get your point, I just don't agree with it. It is often easier to just install plone than it is to:<div><br><div>1. search and discover LocalFS</div><div>2. decide if it is too old or if it can be satisfactorily patched.</div>
<div>3. patch it (thank you Robert)</div><div>4. test, test and test it.</div><div>5. Hope that it still works in the next version of zope that comes out.</div><div>6. plan to test, test and test it in the next version of zope. And the next, and on and on.</div>
<div><br></div><div>Or you can install plone and know that it has been well tested, it is well maintained and has a large community. One click and you are done. The next version of plone will also be well tested.</div><div>
<br></div><div>Look, you can do it anyway you want but if you want to imply that my suggestion to use Plone is 'insane' you need to come up with a better alternative than LocalFS.</div><div><br></div><div>But of course this is all moot. For most installs the best way to use large javascript libraries is to put it into an apache folder.<div>
<div></div></div></div></div></blockquote><div><br>Installing Plone in such a case is only the solution if one has no better idea about doing things. The Filesystem Directory View functionality<br>is available out-of-the-box through CMF (which is much smaller than Plone). There was also something like SkinnedFolder (I think) implementing<br>
are similar functionality.<br><br>-aj <br></div></div><br>