Re: [cdt-dev] Please move C++ Class Browser to committed on the CDT 2.0

[Kleanthis Hapitas <khapitas@xxxxxxxxxx>]

Good to hear Thomas!

Are you guys planning to produce any
documentation (feature description, design doc, whatever) that would help
us better understand what it is you are planning to do on this item? 

On a related note, I have broken another
plan item (Eclipse 3.0 support) into two - one to cover compatibility with
the Eclipse 3.0 release (fixing things like emacs key bindings) and one
to cover support for some of the new capabilities that we could (should?)
take advantage of in the 3.0 framework. The compatibility item has been
moved to committed (that's a no-brainer), but the 3.0 enhancements is still
proposed. You had volunteered a little while ago to put together a list
of such enhancements based on the reported features and functionality from
Eclipse 2.0 ----> Eclipse 3.0 M*. I think such a list would be extremely
helpful. Who knows, it might even spur some action :-)

Regards,

Kleo Hapitas

Thomas Fletcher <ThomasF@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx

11/28/2003 10:16 AM

Please respond to
cdt-dev@xxxxxxxxxxx

To	"'cdt-dev@xxxxxxxxxxx'" <cdt-dev@xxxxxxxxxxx>
cc	Chris Wiebe <cwiebe@xxxxxxx>
Subject	[cdt-dev] Please move C++ Class Browser to committed on the CDT 2.0 plan

I'd like to also move the C++
Class Browser/C++ Hierarchy View 
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=47441)
to the committed state
on the CDT 2.0 plan.
 
QNX has assigned and committed
the resources to work on this item.
 
Thanks,
  Thomas