[wingide-users] Wing 2.0 Plugin documentation

Wing IDE Support support at wingware.com
Sat Aug 28 13:34:57 EDT 2004


Our plugin/scripting API is in the code now but not documentated
and hidden.  Cleaning it up for general consumption was too much
to do before 2.0 final but we're planning on starting to do that
immediately after 2.0 final.

I've put you on a list of people we'll email when our 2.0 source
distribution is available, which should be soon.  That is the first
step and you could start working on this immediately after that
if you are willing to deal with patching code, etc.  Eventually
scripters won't need source access at all, but early users will
likely want to be able to quickly make small changes needed by
their particular script.

(BTW, most of what you need is already there, or fairly easy to 

Stephan Deibel

Wing IDE for Python
Advancing Software Development


On Sat, 28 Aug 2004, Adam Feuer wrote:

> Wing folks,
>   We're fans of Wing, and use 1.1 quite a bit. We also use the Bicycle
> Repairman (BRM) source code refactoring tool a lot. In Wing1.1 we use
> BRM in emacs to refactor, switching back to Wing to write code. It's
> awkward, but it's much better than having no refactoring capability.
>   We would like to write a BRM plugin to Wing2.0 so we can use BRM from
> inside of Wing. This would give us a big productivity boost. I've heard
> that the plugin architecture is easier to use in 2.0 than in 1.1, which
> is why we've waited to do this.
>   Can anyone point me at some documentation for Wing2.0 plugins?
> Hopefully with some example source code?
>   Here are the things we need to be able to do in Wing: 
>   * Add a "Refactor" menu somewhere.
>   * Give Wing a command to save the current file to disk.
>   * Get the full pathname of the active file.
>   * Get the line number and column number of the cursor in that file.
>   * For some refactorings, we also need the coordinates of the selected
> area, if the user has selected text.
>   * Give Wing a command to reload the current file from disk. (And
> possibly reload the other files the user has loaded, although if we have
> to we can rely on Wing's automatic reload ability.)
>   * Map the menu commands to keyboard equivalents.
>   Here are some things that would be nice to do in Wing:
>   * Display various dialog boxes- yes/no, a selectable list of items
> (references), etc.
>   * Change to active file to one that we specify, possibly loading or
> reloading from disk.
>   * Move the display coordinates to a particular place in the file so
> the user can see the refactoring and approve it if neccessary.
>   Any pointers or help anyone has would be appreciated. Naturally we'll
> contribute the plugin back to the community.
> cheers
> adam
> --
> Adam Feuer <adamf at aviarc dot com> 206-834-1803
> Director of Software Development, Aviarc Corporation http://www.aviarc.com/
> _________________________________________________
> Wing IDE users list
> http://wingware.com/lists/wingide

More information about the wingide-users mailing list