"Greg Brunet" <gbrunet@sempersoft.com> writes:
"Patrick K. O'Brien" <pobrien@orbtech.com>
wrote in message
> SourceForge sometimes has errors on their servers. I would simply
> try it again.
>
> --
> Patrick K. O'Brien
> Orbtech http://www.orbtech.com/web/pobrienBTW: I meant to ask how things were going on the PyAlaMode project.
Coming from VB, I really miss the auto-complete capabilities of the IDE
when writing code, and you seem to have come up with the closest
solution to that from what I've seen among the various IDE's out there
for Python. I know that you got bombarded with recommendations in the
"PyAlaMode Debugger wants" thread in the wxPython mailing list. I
haven't seen anything about it on your web page, and didn't know if you
had a list of things that you might need help on. I'm only a beginner
at Python, but would be interested in helping out if there's a way to
contribute. Best wishes,
We're getting off-topic for the wxGlade list, so I'm copying the
wxPython-users list. Replies to this message should not include the
wxGlade list, since PyAlaMode has nothing to do with wxGlade.
PyAlaMode exists and works in a basic form. The foundation is pretty
good, and the namespace updating and autocompletion are very solid,
though more limited than the amount of introspection you can get in
PyCrust/PyShell. Also, the WingIDE folks have a screenshot that
appears to indicate that they've got some autocompletion tricks up
their sleeves that I haven't figured out yet.
But PyAlaMode is missing many features that it needs to be a decent
editor. So I keep going back to Emacs. I'd love to have help with
PyAlaMode. Creating an editor that can really compete with Emacs is a
big job and I have a limited amount of free time.
All my wxPython projects have recently moved to the wxPython CVS
repository, so I'll be shutting down the PyCrust project on
SourceForge. Everything is now part of the new "Py" collection. I'm
working on documentation, which is available here:
http://www.orbtech.com/www/PyManual.html
So you could check out wxPython from CVS, or wait for the next
release. Or, since it works pretty well with the current release of
wxPython, you could just check out the py package from here:
http://cvs.wxwindows.org/viewcvs.cgi/wxPython/wxPython/py/?only_with_tag=WX_2_4_BRANCH
I take that back. I just changed all the Py code to use the new
prefix-less "wx" package:
import wx
So you'd need to install that as well. (BTW, it only took maybe two
hours to convert the entire "py" package to the new syntax.)
Then, just let me know how you would like to contribute. Thanks.
···
--
Patrick K. O'Brien
Orbtech http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------