Ok, I see. I think that this plug-in is indeed a step into the right direction. First time in Eric I type a class, I instantiate an object of this class and after the "." I finally can see the attributes/methods of the class. And not only this, I can only see __repr__, __str__ and all that stuff. Maybe for a simple project you do not need intellisense at all but for projects that started to get big, it is a *must*.
Thanks! -----Original Message----- From: Detlev Offenbach [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 8:41 PM To: [email protected] Cc: objectref Subject: Re: [Eric] About Rope AutoCompletion On Dienstag, 8. April 2008, objectref wrote: > Hi, > > > > Latest Eric snapshot states that "snapshot-20080406 of the rope refactoring > plugin released. It is an update to rope 0.8.0 and adds an alternative > autocompletion provider for Python. " > > Does that mean that I can use an alternative autocompletion mechanism in > Eric ? I saw that I can select it from Settings/Refactoring (Rope)/Enable > Autocompletion. What are the main differences from Eric default > autocompletion mechanism at this time ? > > > > Thanks, > > > > Anthony Default autocompletion is that provided by QScintilla2, which is based on API files ot the current document. The alternative a/c provided by the rope plugin works by analysing the source code. The way I coded the plugin is, that if rope a/c is activated, that is tried first. If rope doesn't give any completion, it falls back to the default QScintilla2 based a/c. The editor component in eric4 provides a hook method, which can be set by a plugin. That way, plugins can provide alternative a/c providers. The contribution of an even better a/c provider would be appreciated. Regards, Detlev -- Detlev Offenbach [EMAIL PROTECTED] _______________________________________________ Eric mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/eric
