Re: [Pydev-code] PyDev Development first-step help

[Fabio Z. <fa...@es...>]

Adding more comments inline :)


On Mon, Nov 4, 2013 at 8:51 AM, Kurosch Petzold
<ku...@ze...>wrote:

> Hello Fabio,
>
> thanks for that reply.
>
> Further explanation follows:
>
>
> >> I want implement some features into PyDev and would like to know whether
> >> there is some documentation for development.
> >>
> >
> > As for documentation, I think you probably found:
> > http://pydev.org/developers.html (which gives details on getting the
> code
> > and tips on running it locally).
>
> Thanks for that pointer I did find that already, and thought there would
> be more to it.
> I would like to know whether I should use Jython or Java for the add-ons I
> want to implement.
>

I think for the level of integration you want in the features below, you
want to use it in java.


>
> >>
> >> Features I want to add are:
> >>  # hoare calculus plugin for code verification,
> >>
> > Well, I'm not sure what exactly you'd be verifying here, but as a
> > reference
> > you can probably use the visitor pattern to visit the files -- you should
> > probably create a subclass of
> org.python.pydev.builder.PyDevBuilderVisitor
> > (you can go to that class and press F4 in JDT to see those).
>
> I wanted to use jAlgos(http://j-algo.binaervarianz.de/) Hoare
> functionality and change it from C0 (a simple C dialect) to python, so
> that it is possible to verify ones code using Hoare functionality. This
> would be basically an extra plugin, which will need to access the code
> from the editor somehow, or I will need to extend the editor to be able to
> use that functionality.
>

Interesting :)


>
>
> >>  # some nice variable visualization for teaching purposes,
> >>
> >
> > Well, you probably need to give more details on what's the visualization
> > here in order to help you better...
>
> Basically I want to make some visualization for variables in debug, so
> that it is easier to understand if you do not know much about debugging
> and/or programming. Ofcourse this will mostlikly only work for some basic
> variables first (like array, vector, int, bool..)
>
>
> >
> >>  # some profiling of the code,
> >>
> >
> > There was a patch for a profiler once (
> > http://sourceforge.net/p/pydev/bugs/635/) but it didn't get integrated
> > (needs some work). It may be something you can take a look at... (the
> > patch is at that link).
> >
> Thank you; it seems that this patch is nearly finished and just needs some
> cleaning and implementing your suggestions obviously.
> I would also add some other profiling like program depth.
> I think this (http://pycallgraph.slowchop.com/en/master/) would also be
> useful for cProfiler. It creates a "call graph" of the python programm.
>

That'd be nice :)


>
>
>
> >>  # a mouse hover over functionality to show variable values like in the
> >> visual basic editor
> >>
> >
> > That'd be nice (but I'm not sure exactly what'd be needed, so, not sure I
> > can help you well there).
> >
> Well for this I need to register a timer to the editor window, so that if
> the mouse stays at one point a given time, lets say 5sec, it will start
> the debugger in the background with a breakpoint at the given line and
> requesting the value of the variable underneath the mouse pointer. So my
> question is, is it possible to run the debugger in the background with
> some breakpoint set and getting the wanted variable value? I tried doiung
> this running jython and pdb, but unfortuatly accessing pdb through jython
> is not possible as far as I managed.
>

Actually, when you're in a debug session, PyDev already does that for you
(but starting a debug session just because you're hovering over a variable
is probably something we can't manage to do properly as you'd need to get
to a proper path in the code which could prove impossible to do properly).


>
>
> >>  # and if possible some step back functionality to go a step back in
> >> debugging.
> >>
> >
> > Actually, that already exists: in the debug view, you can choose run >
> set
> > next statement (Ctrl+Alt+R) -- mainly, you can select what should be the
> > next statement -- python has some limitations on that (such as not being
> > able to jump anywhere -- it must be a place in the current frame -- and
> in
> > the same stack -- i.e.: you can't go from an except: block back into the
> > code that generated the exception as that'd be a different block for
> > python), but aside from those, it works pretty well.
> >
> Well if this is already implemented till the point of python limitation
> than there is this one done.
>
>
> Thanks,
>
> Kurosch
>
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> pydev-code mailing list
> pyd...@li...
> https://lists.sourceforge.net/lists/listinfo/pydev-code
>