I vote for -- based on experience from both sides, and having used both (1) and (2) -- submodules in subfolders, root module in root folder.<br><br>Said another way, any module(s) in the module download that depends on the core module gets put in a subfolder.
<br><br>And any module that depends on another module should (of course) list that root module as its &#39;package.&#39;<br><br>- Ken RIckard<br>agentrickard<br><br><div><span class="gmail_quote">On 10/12/07, <b class="gmail_sendername">
Moshe Weitzman</b> &lt;<a href="mailto:weitzman@tejasa.com">weitzman@tejasa.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Gabor has started a discussion on a subtle point and I think it is<br>best not to introduce &quot;related problems&quot; into the same thread. Lets<br>get back on topic.<br><br>&gt; I want to throw-in a related problem to be taken into account. It is
<br>&gt; about the &quot;human readable names&quot; of the modules. I am looking at the<br></blockquote></div><br>