Hi folks,
As a follow up to my response to Ghislain, here's where things currently stand:
The new and revised GTK2-based _gv library has been in use with CIETmap for
more than a year now without any problems. However, CIETmap has its own version
of gview.py that works with this _gv. Many things have changed from the
gview.py currently in SVN. As it is now, it won't work with the new _gv.
But this is not so bad since most of it is now fully incorporated into _gv.
For example, the GvData class is now _gv.Data, most of the GvShapes methods are
_gv.Shapes methods and GvShape has been been fully implemented as a true Python
object as _gv.Shape. So gview.py is not that important anymore...
Does this means that even if one builds the lib, he would not be able to access
it via the gview module? Well, a compatible gview.py does exist but has not
been comited yet for lack of testing. Nevertheless, it does work as ecollage
could testify ;)
Also, this file has changed almost beyond recognition so it would be difficult
to compare with the previous one.
So, should I comit it anyway?
Of course, there is the building issue. I know it seems like a daunting task
but if I could do it both on Linux and Windows, anyone who has ever compiled
from source can ;)
I'll try to post instructions on the website as soon as I can (gotta figure
out how first!).
More later... stay tuned!
BTW, I remind you that there is a #openev2 channel on irc.freenode.net...
I usually hang out there from 9pm-11pm EST each night as leGeddy.
cheers
--
Mario B.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
Openev-discuss mailing list
Openev-discuss@...
https://lists.sourceforge.net/lists/listinfo/openev-discuss