> The objects that do *real* work are called services and can be published and > looked up in any number of ways - the plugins themselves are just the delivery > mechanism.
Ah, got it. > Yep - it is possible(!) - you just have to get the eggs that Envisage relies > on... The Envisage core is in a separate egg to the GUI workbench plugin so if > you just want the plugin framework etc you don't have to have mush at all (you > will need traits of course).... I'll see if I can whip up a minimal list of > eggs required to get Envisage + Traits minus the GUI stuff... That would be cool, because just for grins I tried to get the MOTD example running. I followed the instructions from https://svn.enthought.com/enthought/wiki/Install and built all the eggs that it could, but trying to install from the dist directory seems to be broken. You can't do easy_install -f . *.egg because that doesn't get the dependency order correct, and when you try to do it manually, if there's a missing dependency it tries to go to PyPI instead of looking in the dist directory. It's simply too frustrating to build. So, I'd appreciate any help to make it simpler, because it seems like a well thought out system and I'd like to try it. Rob
