Detlev, Sorry for the late reply. I noticed the plugin PDF yesterday, a little too late for my first go at a plugin. Serves me right! I'm usually the one who tells people to 'read the manual.' The instructions and reference are great. The setup you have created for debugging plugins is very convenient. I used it to create another plugin in about half the time as the first.
Might be nice if the plugin docs were in the help viewer somehow. (I didn't think to look in the source directory until later.) Thanks, -- Larry > From: detlev <[email protected]> > Date: Mon, 25 Jan 2010 19:00:30 +0100 > To: <[email protected]> > Cc: Larry Shaffer <[email protected]> > Subject: Re: [Eric] Access running eric4 instance through its shell? > > Hi, > > first of all your plug-in project should have the project type "Eric Plugin". > The main script should be the file that starts with "Plugin...". When you > run/debug/... your plug-in project, the plug-in is run inside a fresh eric4 > instance. All this and much more is described in the plug-in document > available in the eric4 package. I highly recommend reading it. > > Regards, > Detlev > > On Sonntag, 24. Januar 2010, Larry Shaffer wrote: >> Hi, >> >> I'm not quite clear on this. Would I need to debug a project that is the >> full eric4? (i.e. Load eric4 into eric4?) Or, can I debug the plugin's file >> directly? If so, how? >> >> Or, can the breakpoint info saved with the plugin's file, and eric4 goes >> into debug mode when the plugin is run, but without loading eric4 inside >> eric4? >> >>> From: detlev <[email protected]> >>> Date: Sun, 24 Jan 2010 15:22:51 +0100 >>> To: "[email protected]" <[email protected]> >>> Subject: Re: [Eric] Access running eric4 instance through its shell? >>> >>> On Sonntag, 24. Januar 2010, Larry Shaffer wrote: >>>> Hi, >>>> >>>> Is it possible to access the running instance of eric4 that you are >>>> working in through its Python shell? Or, is there another way to 'see' >>>> inside of eric4 to help when making plugins, etc? >>> >>> When you are debugging your plugin within eric, you may set a breakpoint >>> anywhere you like. Just make sure, that the "Trace into interpreter >>> libraries" is checked. >>> >>> Regards, >>> Detlev >> > > > -- > Detlev Offenbach > [email protected] > _______________________________________________ Eric mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/eric
