S60 Open to new features

The href="http://www.forum.nokia.com/main/resources/tools_and_sdks/carbide_cpp/">Carbide.c++
Development Tools for SymbianOS is built upon
open source standards—mainly the Eclipse
platform which uses the OSI href="http://www.opensource.org/docs/certification_mark.html">certified
Eclipse
Public License.  While Carbide is not open source, many of the
Eclipse plug-ins it is built upon are.  Additionaly, the
Carbide.c++ SDK leverages these open platforms to provide Eclipse
plug-in developers and “buildmiester’s”
to customize the
way Carbide.c++ works in their environment.

The
Carbide.c++ SDK provides Eclipse plug-in developers access and control
of the Carbide.c++/SymbianOS
project and build environment.  Check the Carbide.c++ Help
contents under Carbide.c++ Plug-in
Developer Guide / Getting Started for information on
setting up an Eclipse development environment for building upon the
Carbide.c++ SDK.  Because Carbide.c++ is based on Eclipse and
Java, a large library of plug-ins and libraries
are available to assist Carbide.c++ plug-in development. 

As an automated test developer for Carbide.c++, I am essentially a
Carbide.c++ plug-in developer.  Using the Carbide.c++ SDK, href="http://sourceforge.net/projects/abbot">Abbot.swt, Eclipse
and its libraries, I write Carbide.c++ plug-ins that, when installed,
can run Carbide.c++ through a grueling hours-long automated
validation.  There is almost no limit to what can be accomplished
from within an Carbide.c++/Eclipse plug-in. 

I know of efforts outside our group, within Nokia and outside, to
create Carbide.c++ plug-ins to integrate necessary tools into
Carbide.c++ or to better integrate Carbide.c++ into thier build
environment.  I hope to cover Carbide.c++ plug-in development more
in future entries, to encourage more Carbide.c++ plug-in authoring, and
to ask for feedback on what type of plug-ins customers wish Carbide.c++
had available.