There's also a problem of control.  You're assuming that all releases are compatible with Drupal.  In TinyMCE's case, not all of Moxiecode's releases have been "Drupal friendly" .  You'd actually need a third server/service to ping the URL of the most recent approved releases of external code. 

This idea was floated during the "no third party code" discussion back in May (my summary of that discussion - http://groups.drupal.org/node/3364#comment-12473 ).  Derek Wright did a great job of outlining the issues with this approach and was very clear that he was not going to write scripts to do this. ( http://lists.drupal.org/pipermail/development/2007-May/024045.html)

___

Kevin Reynen
Integrated Media Coordinator
Reynolds School of Journalism and
Advanced Media Research
University of Nevada, Reno



On 9/11/07, Sean Robertson <seanr@ngpsoftware.com> wrote:
That's a very good idea from a usability standpoint, but a problem for
security.  Any such feature would need to show the user what was about
to be downloaded with an appropriately stern warning and offer them the
opportunity to kill it.


adrian rossouw wrote:
>
> On 11 Sep 2007, at 6:54 PM, Fernando Silva wrote:
>
>>
>> I add to it the thought that this module could provide a way to
>>
>> select, show and install jquery plugins from the oficial jquery
>>
>> plugins page and "install time"!
>>
>
> How useful it that jquery.com is running the project module then.
>
> Do we know if their cvs tags are using something that project can use?
> because you could probably extend/ use the code of update_status to do
> that for you.
>
> just have it ping a different server, with the extra function to install
> the module.
>
> This could actually be a cool solution to the tinymce problem too.
> If a module could initialize a download of the lib from it's .install,
>

--
Sean Robertson
Web Developer
NGP Software, Inc.
seanr@ngpsoftware.com
(202) 686-9330
http://www.ngpsoftware.com