On Mittwoch, 16. Juni 2010, Stjujsckij Nickolaj wrote: > All right. > Actually I've already started porting — I've cloned your eric5 hg repo, > started a branch for my work and made corresponding symlinks in my > ~/.eric4/ directory. > Can't say I've made much progress though (because of zero Eric/PyQt4 > experience), but plugin now could be loaded and configured (Preferences > page). Still I cannot figure out what advantages "Eric4 plugin" project > offers (except snapshot packing)
If you run/debug/... your plug-in project, an instance of eric will be started as the runtime environment for the plug-in. > and what to do next — I don't see any > error or backtrace neither in Log Viewer not in `eric4 --debug`. And > plugin certainly doesn't work as intended yet (-:E > > Hopefully I'll keep making progress (slowly but steadily) and I'd be > grateful for any advice about debugging plugins. And I hope you could help > me with other (possibly stupid) questions that would certainly arise (-:E > > P.S. [for everyone] I could publish my branch, but right now I don't see > real need in doing this. Stiil, if you want to help, track progress or > something, feel free to ask. > > > I don't have intentions to backport it right now (time constraints). > > It is backporting to Python 2 and to PyQt4 API v1. However, it should be > > fairly straight forward (e.g. porting eric to Python3 and API v2 > > actually took me about 3 weeks). If you would like to give it a shot I > > would recommend to do that as a separate plug-in (like the CVS plug-in). > > _______________________________________________ > Eric mailing list > [email protected] > http://www.riverbankcomputing.com/mailman/listinfo/eric > -- Detlev Offenbach [email protected] _______________________________________________ Eric mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/eric
