I disagree. I don't think the initial number of lines of code is a good indicator of anything (and also, it's not just 3 lines in this case, but rather 3 lines plus an entire file, right?). In my opinion, a better measure is whether or not the code is written in a way that is generically useful. If it can be meaningfully used by a variety of sites without them needing to edit the code, then posting it as a module makes sense. Modules are accessible to a much broader audience than PHP snippets are.<br>
<br>However, in this case, if I understand the description correctly, it sounds like it might have a lot in common with an existing project (<a href="http://drupal.org/project/compact_forms">http://drupal.org/project/compact_forms</a>)? If so, then you should contribute your work to that project rather than starting a new one.<br>
<br>Good luck!<br>David Rothstein<br><br><br><div class="gmail_quote">On Thu, Apr 30, 2009 at 11:17 AM, Pierre Rineau <span dir="ltr"><<a href="mailto:pierre.rineau@makina-corpus.com">pierre.rineau@makina-corpus.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Ok, so I won't.<br>
<br>
Thanks for your answer.<br>
<br>
Le jeudi 30 avril 2009 à 10:29 -0400, Khalid Baheyeldin a écrit :<br>
<div><div></div><div class="h5">> No. A 3 line module is not worth its own project and issue queue and<br>
> such.<br>
><br>
> This module is best posted in the snippets here<br>
> <a href="http://drupal.org/node/23220" target="_blank">http://drupal.org/node/23220</a><br>
><br>
> See also here <a href="http://drupal.org/handbook/customization/php-snippets" target="_blank">http://drupal.org/handbook/customization/php-snippets</a><br>
><br>
> On Thu, Apr 30, 2009 at 4:15 AM, Pierre Rineau<br>
> <<a href="mailto:pierre.rineau@makina-corpus.com">pierre.rineau@makina-corpus.com</a>> wrote:<br>
> Hi folks,<br>
><br>
> I made a really, really simple module (3 lines and a JS file).<br>
><br>
> It uses the "title" HTML attribute on text and textarea HTML<br>
> inputs to<br>
> display an empty value in the input, which disappear on focus,<br>
> and<br>
> re-appear on focus out if input is still empty.<br>
><br>
> This is simple, I saw something like 10 or 20 different JS<br>
> implementations; I choosed one of them, (one I saw on<br>
> Drupal.org's<br>
> forums), adapted it a bit the JS file to be more coherent with<br>
> Drupal6.<br>
><br>
> The real module just does a "drupal_add_js()" in hook_init()<br>
> (which<br>
> should be compatible with aggressive caching).<br>
><br>
> Do you think this is a good idea to commit it in the Drupal<br>
> CVS, as a<br>
> new project?<br>
><br>
> Or do you known some modules which already does the same<br>
> thing, in a<br>
> better way?<br>
><br>
> Regards,<br>
> Pierre.<br>
><br>
><br>
><br>
><br>
> --<br>
> Khalid M. Baheyeldin<br>
> <a href="http://2bits.com" target="_blank">2bits.com</a>, Inc.<br>
> <a href="http://2bits.com" target="_blank">http://2bits.com</a><br>
> Drupal optimization, development, customization and consulting.<br>
> Simplicity is prerequisite for reliability. -- Edsger W.Dijkstra<br>
> Simplicity is the ultimate sophistication. -- Leonardo da Vinci<br>
<br>
</div></div></blockquote></div><br>