Re: [Pydev-code] Getting started with PyDev scripting

[Joel H. <yo...@if...>]

Hi!

 > Nicely done, works very well for me (asside from the docstring issue
 > you mentioned), so... congratulations!!!

Thanks!

 > The only thing that I saw that you shouldn't do is storing another
 > editor reference in your class (self._oEditor), you should just use
 > the editor variable directly (it will always be available in your
 > namespace).

Right.

 > from org.python.pydev.core.docutils import ParsingUtils
 > ParsingUtils.eatLiterals(document,
 >                          StringBuffer(),
 >                          initialOffsetOfLiteral)

Who put StringBuffer in my scope? I can see it's there but I didn't 
declare it? Is it a Jython thing? Where can I read  up on this?

Oh, and is there something similar for retrieving the contents of 
parantheses? I tried:

iOffset = oSelection.absoluteCursorOffset
oStrBuf = StringBuffer()
print iOffset
print ParsingUtils.eatPar(document, iOffset,  oStrBuf)
print oStrBuf

which returns offset of the paranthesis that closes the closest nested 
paranthesised expression in which the cursor currently is placed, but 
oStrBuf is left empty. I was thinking maybe I should use this to detect 
parameters instead, since that might be an easy way of dealing with line 
continuations, comments and code directly after the scope opening colon 
on def lines. What do you think?

 > So, what were your first impressions on pydev scripting?

It's great. It gives me great opportunity for customisations, which 
otherwise would be impossible (since I don't Java :-). It's all still a 
little bewildering since I'm not yet used to how the internals of 
neither eclipse or pydev work. The learning curve seems steep (but not 
vertical). The dir utils you posted proved to be life savers. It's a 
pity the code is cropped when viewed in the html repository at 
sourceforge, so maybe you could put it somewhere accessible so that 
people not currently on this list also can benefit from them?

One impression is that there seem to be very little documentation. Maybe 
I've got myself to blame since I must admit I still haven't pulled down 
the pydev source. To my defense, I've been confined to WinXP the last 
couple of days and I don't really know how to cvs from that... On the 
other hand, this list has been a great help with speedy and constructive 
responses.

 > I'd really like to know ways to improve it...

It's too early for me to tell, I think. I need to mess around with it 
for a while first, but I'll get back to you once I come up with 
something solid. Should I post those feature requests to this list or to 
the tracker at sourceforge?

Now, back into the fray... :-)
/Joel