>Hi George,
>
>>AFAIK, for Intellisense to work across multiple environments it would have to heavily utilize Windows messaging services. Further, given the component design direction currently being utilized, it doesn't make much sense to me that they would build in this feature independently of its implementation elsewheres.
>
>Actually, I tend to disagree here. First of all, the VFP 7 Intellisense bases on DBF files, that means it is native to VFP. Also, at one point during the demo, the debugger came up and what was in the code window really looked like CEE, except that the object had a different name.
>

What Calvin showed at DevCon, IMHO, was really two different kinds of Intellisense. One, the command intellisense, helps the developer finish VFP commands by finishing out common keywords and displaying a tooltip with the parameter list. This is the Intellisense that is based on DBFs.

The "other" Intellisense is object Intellisense, which cannot be table based because of its dynmic nature. Object Intellisense for COM objects would be fairly easy todo right now, because the object does not have to be instanciated to traverse the tlb and gather the methods and properties. Intellisense for native VFP objects, however I think might be another story. At design time, you cannot dependably resolve THISFORM to the active form with _SCREEN.ActiveForm, or SYS(1270). So even if we could catch every key in the editor window, getting an actual object reference to the object in question would be pretty tricky. (Any ideas? You've amazed me plenty of times before...)

>Taking this into account and looking at the possibilities that are available in VFP and the VFP API, all we need is a hook to capture every single key stroke instead of just reacting on the SpaceBar or something like this, and we are practically done.

Agreed. This and solving the difficulty of object resolution above woud get us all the way there. I was actually hoping that you knew of a way to fire code on every keypress...

>Reading the current line in the editor window is easy,

I believe you, but how?

>displaying a listbox at the current cursor position is not difficult either,

Ok. I can do this.

>neither is displaying a tooltip.

And this.

>And what else is needed to implement IntelliSense? Quering the code for some key words,

And this... well, maybe.

> analyizing the class hierarchy, obtaining information from ActiveX controls and OLE servers via the type library... All of this can easily be done within the current design of VFP.

Like I said above, COM server is simple, but native objects are giving me a headache.