Re: Yet another reason for openTools API attention
- From: Charles McAllister <charles@xxxxxxxxxxx>
- Date: Wed, 28 Feb 2007 11:41:46 -0600
Sergio Sette wrote:
I think the current community has a great potential, just needs to be supported. And supports means documentation, documentation, documentation ;-) (or more code to look at)
Hey Nick, are you listening ? We are here a we just needs a little help !!
Yes! more examples.
for example here's a great article, http://dn.codegear.com/article/21114
also, whats really needed is a way to identify what symbol is at the current cursor position, and locations in the source that particular symbol is referred to, as well as the symbol's type and scope etc.
this kind of information is not easily obtained by the expert writer, and requires writing a parser that is accurate, for example, taking into consideration include files and compiler defines.
when you look at a product like CodeRush, i would think that half of that product is composed of its parser.
and then you got ModelMaker writing their parser, Castalia writing their parser etc.
also, something i could really use is a convenient way to paint on the editor's surface.
there are hacks available, but they have their shortcomings.
it would be great if there was an event for painting a line of code, which would take code folding into account.
.
- References:
- Re: Yet another reason for openTools API attention
- From: Sergio Sette
- Re: Yet another reason for openTools API attention
- From: Brian Moelk
- Re: Yet another reason for openTools API attention
- From: Sergio Sette
- Re: Yet another reason for openTools API attention
- From: Brian Moelk
- Re: Yet another reason for openTools API attention
- From: Sergio Sette
- Re: Yet another reason for openTools API attention
- Prev by Date: Re: Spacely indy
- Next by Date: Re: The Delphi Brand
- Previous by thread: Re: Yet another reason for openTools API attention
- Next by thread: Re: Yet another reason for openTools API attention
- Index(es):
Relevant Pages
|