On Tue, 4 Dec 2012 12:24:28 -0200 Flávio Ceolin <flavio.ceo...@profusion.mobi> wrote:
> I have recently committed in IN-EFL/ecore some patches implementing > support for loadables modules. It makes the engines been loaded when > they are needed. I did not break the api, so each engine still has its > own api. It's far from ideal, should exists one api used by all the > modules but at least until the next version, we need keep the api. > > The modules (engines) usually exports just on symbol, the "new" > function, the other necessary functions are in the engine's interface. I'm a bit confused here, why is this needed? Isn't it the case that more often than not there's only one useful engine that is supported by the hardware? And not like you will be moving a window on the fly from X11 to fb? Certainly I don't think anyone will be using X11 and Windows engines in the same run of their proggy. How is this supposed to work? What use case is there for it? I can understand if it was for image loaders & savers, and other stuff, that makes sense, but engines? -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
