Re: [jokosher-devel] Extensions

[John Green <john thegreens co uk>]

On Tue, Oct 10, 2006 at 10:34:24AM +0100, Stuart Langridge wrote:
> I have had a thought. Do we think it's worth having a special filetype
> for J extensions? 

In principle yes. However atm Extension.py is looking at the extension to
decide how to treat it (either .py or .egg). We'd have to come up with of
another way of differentiating them.

There is another problem with extensions that occurs to me. Extensions are
meant to provide functionality that is not in core jokosher. You should also
be allowed to cater for dependencies that are not in core jokosher. E.g. I
have in the back of mind an idea of connecting from my phone using
bluetooth. Whether this would actually work or not I don't know but it would
mean the extension importing lots of dependencies that are completely
useless for anyone without bluetooth capability on their machine. The
question is what to do about these missing dependencies. We can trap for
these on startup (it goes down in Extension.LoadAllExtensions()) but what do
we do? Do we simply display the error? We could offer to disable any that
can't be resolved so it only happens the once which might be friendlier. I
don't know.

-- 
John Green