Ok, so I followed the codewise docs. here http://groups.google.com/group/leo-editor/browse_thread/thread/76a68d7e6bc2ddf9
In general I think things are looking good, here's a few thoughts. - I think p.<autocomplete> will always show Leo centric completions. I'd want to be able to turn that off, sometimes p is not a position :-) - codewise doesn't support docstring reporting, would be nice to add that - 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. - 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. - 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'. - the 'rescan everything you scanned in the past' option is really cool. 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. Cheers -Terry -- 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.
