On 11/1/07, Christopher Barker <[EMAIL PROTECTED]> wrote: > starting up Peppy seemed to import the gdal module too - I wonder what for?
Hyperspectral imagery. Not a common major mode, I would have to agree, but I use it all the time for my job. > I think you really do need to have a plug-in system where registering > the plugin is a separate step from importing the while thing Here's a workaround I just found: lazy module importing. http://peak.telecommunity.com/DevCenter/Importing It's complicated because the major modes reside in plugins, and all the logic to determine if a file is editable with a major mode reside in the major mode code itself. So, the major modes are self-contained code; i.e. there's no huge case statements in the main program -- everything related to the major mode is with the major mode plugin code. The upshot is that the code needs to be imported to check to see if a file works with a major mode. Perhaps there could be a two-stage importing -- one small plugin that's always imported and contains the logic to determine if a file is editable with the major mode, and the other larger plugin that contains the bulk of the code. > If this > catches on, we can only hope there will be many, many, plugins in the > future. I need to write up some documentation to make that easier. But, obviously the framework is still in flux. :) > By the way, all the default key bindings use ctrl+whatever on the Mac, > where they really should be cmd+whatever. You're right, there are no default mac key bindings, and my Mac-fu is weak. Rather than simply converting the windows bindings, I'd like to create mac bindings that correspond to the Mac UI guidelines. Rob
