For me there is only one question left to fix this bug: How should methods of extensions be accessible?
Right now they behave like direct members of the engine:
engine.some_extension_method()
There are also some possible alternative solutions:
engine.extensions.some_extension_method()
engine.extensions.NameOfExtensionClass.some_extension_method()
As this is only internal stuff, I think we are safe to go with the current implementation and change over to another one if necessary (e.g. when we get a huge number of extension methods)
IMO this is the only open question we should discuss before merging this branch into lp:zeitgeist.
What do you think?
For me there is only one question left to fix this bug: How should methods of extensions be accessible?
Right now they behave like direct members of the engine: some_extension_ method( )
engine.
There are also some possible alternative solutions: extensions. some_extension_ method( ) extensions. NameOfExtension Class.some_ extension_ method( )
engine.
engine.
As this is only internal stuff, I think we are safe to go with the current implementation and change over to another one if necessary (e.g. when we get a huge number of extension methods)
IMO this is the only open question we should discuss before merging this branch into lp:zeitgeist.
What do you think?