| author | fturovic <frank.turovich@nokia.com> |
| Tue, 27 Jul 2010 15:28:19 -0500 | |
| changeset 1704 | 24ac5a5cf80c |
| parent 130 | 825355d51766 |
| permissions | -rw-r--r-- |
| 130 | 1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
2 |
||
3 |
<html> |
|
4 |
<head> |
|
5 |
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
|
6 |
<title>Carbide Plug-ins Overview</title> |
|
7 |
<link rel="StyleSheet" href="../../book.css" type="text/css"/> |
|
8 |
</head> |
|
9 |
||
10 |
<body> |
|
11 |
<h2>Carbide Plug-ins Overview</h2> |
|
12 |
||
13 |
<p>Creating a Carbide tool plug-in requires some knowledge and understanding of the Eclipse plug-in environment. There are two methods of creating Carbibe plug-ins, including:</p> |
|
14 |
<ul> |
|
15 |
<li><a href="../gettingStarted/import_examples.htm">Importing</a> an existing Carbide tool plug-in and modifying it </li> |
|
16 |
<li><a href="PLUGINS_ROOT/org.eclipse.platform.doc.isv/guide/firstplugin.htm">Creating</a> a new Eclipse plug-in and adding Carbide API calls</li> |
|
17 |
</ul> |
|
18 |
<p>Each has its advantages and disadvantages. Importing an existing Carbide plug-in provides a working plug-in that you can modify and add to easily to get something up and running quickly. However, the plug-in probably doesn't include the API interaction you want to implement and includes a lot of resources you probably don't need or want. Creating a new plug-in from scratch has the advantage of giving you a clean slate upon which to add your own code. It doesn't include any basic Carbide support like menu items and preference panel calls that nearly every tool requires, forcing you to add them on your own.</p> |
|
19 |
<p>Which one you choose depends on the type of plug-in you want to develop and how much support you need to get up and running. In either case, both methods will require access to Carbide projects to allow them to interact with the active project.</p> |
|
20 |
<h2>Accessing Carbide Project Information</h2> |
|
21 |
<p>The following pages describe how to access specific Carbide project information for use in your own tool plug-ins.</p> |
|
22 |
<ul> |
|
23 |
<li><a href="sdk_getprojinfo.htm">Getting Carbide Project Information</a></li> |
|
24 |
<li><a href="sdk_getinfmmpinfo.htm">Retrieving INF and MMP Project Information </a></li> |
|
25 |
</ul> |
|
26 |
<h4>Related information</h4> |
|
27 |
<ul> |
|
28 |
<li><a href="PLUGINS_ROOT/org.eclipse.platform.doc.isv/guide/firstplugin.htm">Simple Plug-in Example</a> (Platform Plug-in Developer Guide)</li> |
|
29 |
<li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/tasks/carbide_tools.htm">Creating Carbide Plug-ins</a></li> |
|
30 |
<li><a href="PLUGINS_ROOT/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm">Plug-in Development Environment Guide</a></li> |
|
31 |
</ul> |
|
|
1704
24ac5a5cf80c
updated copyright dates and fixed some css issues
fturovic <frank.turovich@nokia.com>
parents:
130
diff
changeset
|
32 |
<div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br> |
| 130 | 33 |
License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
34 |
</body> |
|
35 |
</html> |