Davy Mitchell wrote:
Thanks Michael - looks really good and useful as I have started to
look into this for autocomplete in DIE.
30mb eh? That will be interesting :-)
What the PI generator script in particular does is generate skeleton
Python files representing the .NET APIs.
If your autocomplete is capable of understanding Python code, then it
will be able to use the same PI files (the generator script is open
source). It's a pretty big task. I would look at using and contributing
to something like PySmell.
The really hard job (as opposed to the merely very hard) is being able
to analyse 'broken' files with invalid Python syntax. Invariably when
the user is in the *middle* of editing a file it is in a state where you
can't parse it. You can tokenize it though and there are all sorts of
tricks to get round this.
This is where Wing does a good job. They haven't implemented the
'reverse duck typing' suggested by Orestis (PySmell creator) which would
allow you to infer ambiguous types from the way they are used.
Michael
Cheers,
Davy
--
Davy Stuff - http://daftspaniel.blogspot.com
Geeky Stuff - http://daftpython.blogspot.com
Davy's Ironpython Editor - http://code.google.com/p/davysironpythoneditor/
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
