On Mon, Oct 10, 2011 at 12:32 AM, Terry Brown <[email protected]> wrote:

> - codewise doesn't support docstring reporting, would be nice to add
>  that

The database has the regexp pattern that can be used to look up
definition in the source file, so this can be added easily.


> - it would be nice if codewise / Leo using codewise would support class
>  name completion, as in ZonalS<autocomplete> giving me ZonalStats.,
>  and then ZonalStats.<autocomplete> giving me the completions for that
>  class.

UI issue, should be trivial to add. Codewise has *very rudimentary* UI
work done for it, the early intent was just to demo the backend.


> - Although it's non-standard, when I've typed foo.get<autocomplete> I
>  see all the many many get* methods codewise has ever heard of - I'd
>  like to be able to pick the class (autocompleting of course :-), to
>  narrow down the list.
>
>  Without pinning down the keystroke/interface issues precisely, after
>  typing foo. I'd like to be able to pick a class from which to pick
>  completions.  Maybe Shift-Ctrl-Space instead of just Ctrl-Space, or
>  something.

Here's an idea: you may be able to dump "temporary class declarations"
in c.db. I.e. declare "foo is MyObj in test.ly : test_func().

> - the codewise command line m and f commands (show classes and
>  functions) don't seem to work, I wonder if they're just not
>  implemented for the command line, or something's missing more in the
>  codewise 'core'.

They work in bzr branch lp:codewise, may be bronen in the version in leo trunk.


> Repeating what I said before, some of the classes I deal with can't be
> instanciated without database connections etc., so I don't want to
> rely on instanciated objects.

In general, relying in instantiated objects will never work when
editing larger body of source text. You would have to execute the
whole file every time, which doesn't exactly yield to safe and
carefree development experience. Imagine trying to implement a script
that would manipulate the file system...

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en.

Reply via email to