On Tue, 4 Dec 2012 13:40:57 -0200 Luis Felipe Strano Moraes
<[email protected]> said:

> On Tue, Dec 4, 2012 at 1:05 PM, Vincent Torri <[email protected]>wrote:
> 
> > On Tue, Dec 4, 2012 at 4:04 PM, Vincent Torri <[email protected]>
> > wrote:
> > > On Tue, Dec 4, 2012 at 3:24 PM, Flávio Ceolin
> > > <[email protected]> wrote:
> > >> Hi folks,
> > >>
> > >> 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.
> > >>
> > >> Some points to considerer:
> > >>
> > >> 1) I've tested the engines that i'm able to build, which means, sdl,
> > >> (opengl,software)_x11, buffer, wayland_(egl,shm). Windows, wince,
> > >> cocoa and ps3 i do not even built.
> > >
> > > i'll try the windows engines
> > >
> > >> 2) I've commited in the IN-EFL to someone working with one of these
> > >> engines try to build and possibly report to me the problems.
> > >>
> > >> 3) Engines such as (software,opengl)_x11 are been build in just one
> > >> module initially and exporting the "new" functions and interfaces
> > >> necessary.
> > >>
> > >> 4) I'm working to port it to new efl tree (expending more time and
> > >> been more careful) with the build system. If no one oppose i'll commit
> > >> it soon.
> > >
> > > put the engines in src/modules/ecore/engines, like evas
> > >
> > > I would like to have at least a diff of the files that are modified,
> > > please, before you commit
> > >
> > >> 5) I break the build between the commits, i did it to make easier
> > >> understand how the engines were ported
> > >
> > > good work anyway :)
> > >
> > > Vincent
> >
> > btw, what about doing that for efl 1.7 branch too ?? It's exactly the
> > same than what is in IN-EFL
> >
> 
> Is there a need to port this to the 1.7 branch? Honestly I believe we
> should push only bug fixes there, and this does not directly fix any known
> bugs.

correct.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [email protected]


------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to