> But that doesn't just happen. True, but it didn't happen as you imply. Leo's core defines a gui-and-platform-independent set of api's which then get instantiated in plugins. Plugins can, and do, use platform-dependent features. For example, the wxWidgets plugin uses the scintilla text widget, something that does not exist by default in Tk/Tkinter.
Leo just started to work with IronPython last night, so the details are fresh in my mind. Amazingly, IronPython allows you to point sys.path (IronPython's sys.path, that is) at CPython's Python24\Lib and for the most part IronPython 'just works' with those libs. So all of Leo's core, being free of any gui code, just worked. That is, until it started to load the IronPython plugin :-) At which point I started to have newbie problems with dbgclr, but that's another story... Edward -------------------------------------------------------------------- Edward K. Ream email: [EMAIL PROTECTED] Leo: http://webpages.charter.net/edreamleo/front.html -------------------------------------------------------------------- -- http://mail.python.org/mailman/listinfo/python-list
