Re: [cdt-dev] CDT API hover help and completion

[Chris Moller <cmoller@xxxxxxxxxx>]

Having thought about this for a couple of weeks, I'm fairly sure we're 
going to need a small family of parsers:  for legacy libs -- glibc, GTK, 
X, etc. -- the documentation is in no consistant format.  I'd considered 
something that would extract API data from the header files in 
/usr/include, or whereever they're kept in various OSs, but I was trying 
to include a mechanism that would show more than just the fcn def, or 
whatever: hover over a call, and you get the fcn def, double click on it 
and the whole man page or some other form of expanded doc pops up.  That 
kind of info just isn't in header files.

Your fellow Beemer Doug Schaefer suggested doxygen, which I suspect will 
work great for a lot of things, but I don't think it addresses older 
stuff like glibc and X.

So, to reverse the question, if _you_ have any requirements for the db 
format, let me know and I'll try to converge with you.

Chris

John Camelon wrote:
> If you have any requirements for the parser, please let me know as soon 
> as you can.  
>
> JohnC
>
>
>
> *Chris Moller <cmoller@xxxxxxxxxx>*
> Sent by: cdt-dev-admin@xxxxxxxxxxx
>
> 07/03/2003 02:19 PM
> Please respond to
> cdt-dev@xxxxxxxxxxx
>
>
> 	
> To
> 	cdt-dev@xxxxxxxxxxx
> cc
> 	
> Subject
> 	[cdt-dev] CDT API hover help and completion
>
>
> 	
>
>
>
>
>
> To the world at large:
>
> We here at Le Chapeau Rouge have started a project to supply API "hover
> help" and completion mechanisms for CDT.
>
> The basis for both of these is the construction of a collection of
> indexable databases containing the necessary information.  What's at
> least a first pass at creating one such db has already been done by
> writing a custom parser that extracts info from the GNU glibc manual
> .texi sources.  As time goes on, we plan to add dbs for libs like X,
> GTK, and whatever else looks useful.
>
> Our next step will be to tinker the CDT plugin to make use of the dbs,
> using the mechanisms already in place for JDT.
>
> Any input -- suggestions, wish-lists, whatever -- is welcome.
>
> Chris Moller
> Tinker at Large
> Red Hat, Inc.
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev