(rfc) recommend installing a plugin when needed

[James Westby]

On Mon, 2008-01-28 at 06:23 -0200, Martin Albisetti wrote:

I've cut out most of what you have said, as it sounds sane to me,
and it looks like you are taking in the direction that makes the
most sense to me. There may be specifics to discuss as the 
implementation proceeds, but I don't think they'll be to large.

> Now, a few questions.
> Would this go right into the Core, or just tweak what would be needed
> and develop it as a plugin?

I don't see a reason why this shouldn't be a plugin. We can add any
necessary code to the core to allow it to do it's job (intercepting
missing commands for instance), but the rest should live perfectly
happily as a plugin.

> Would be add the plugins information to the XML manually or would we
> require plugins export the information needed somehow?

As there is going to be a central place to store this information
then I don't think exporting it buys us much. Also I don't think there
is that much information required from the plugin is there? For instance
the list of commands is easily findable.

I would only suggest reconsidering XML. I don't think it's needed, but
I won't stand in your way; I will mention it just this once. However
I think it is important to consider how to handle format changes for
this file, and XML may make this easier.

> I'm already starting to jump into some coding to cook up a demo of how
> it would work, but I'm rather anxious to get some feedback on where
> I'd like to go with this.

Great, keep us updated on your work.

Thanks,

James