Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: Shopping list (was: Re: [cdt-core-dev] Do we need a cdt.core.

> 
> Michel Paquet, my boss, is working on a list of things we would want to
> contribute for the next release.  It looks like we should be able to at
> least get the new parser to the same level of functionality as the old one
> by the next release.  Michel can comment more.
> 

Ok, meanwhile, here is a (draft) proposition, feel free to comment/remove/add.
Some of it are things, we want to tackle, but if others want to take a
stab at certain features ... by all means.
=================================================================
The plan below is a proto plan and input from the community is very welcome. 

A-  The overall themes for C/C++ core/UI are:

	- robust and enhance 
	- improve usability 
	- improve documentation, write articles 

B- Planned Items

	- Core Model Architectural issues 
		* interface improvements
			+ Propose changes from Amer Hoda(rationale)
			+ LRU caching of the ICElementInfo and removing
			  the hashtable of the ICElement.
			+ Implementing the copy/move/.. operations on the
			  ICElement
			+ Implementing the copy/move operations on the IArchive,
			  to be able to extract/copy/delete object form an object
			  archive i.e. "ar x libm.a cos.o"
			+ Cleaning of the COFF/PE parser and IArchive for COFF
			+ Use of IStorage to create ICElement, for example this
			  is needed by the debugger, when inspecting a shared
			  library outside of the workspace.
			+ Improvement on the event mechanism of the ICElementDelta
			+ Extension-point for the Default C/C++ Parser. 
		* Tutorials and examples on the use of CDI/Launch
			+ ICElement programing examples: 
		* Formating(using GNU indent)

	- Build Model 
		* Smarter management of CMarkers of IResource
		* CMarker persistent
		* Interface API
		* Extension-point to change the builder
		* default reference implementation(?).

	- Index Model (not being worked on)
		* search
		* navigation (F3)

	- UI
		* Change the Copy/Rename wizards to be 2.x
		* UI(PropertyPage) for the builder
		* allow external source paths
		* Disable/Enable text hover



Back to the top