blob: 92777a50834d80c5ed67d6eeeedbb5ccda42b425 [file] [log] [blame]
<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'
#*****************************************************************************
#
#
#****************************************************************************
#
# Begin: page-specific settings. Change these.
$pageTitle = "PDE";
$pageKeywords = "pde, build, ui, plug-in, development, environment, bundle";
# Add page-specific Nav bars here
# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
# $Nav->addNavSeparator("My Page Links", "downloads.php");
# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);
# End: page-specific settings
#
# Paste your HTML content between the markers!
ob_start();
?>
<div id="midcolumn">
<h1><?= $pageTitle ?></h1>
<div class="homeitem3col">
<p>
The Plug-in Development Environment (PDE) provides tools to create, develop, test, debug, build and deploy Eclipse plug-ins, fragments, features, update sites and RCP products. </p>
<p>PDE also provides comprehensive OSGi tooling, which makes it an ideal environment for component programming, not just Eclipse plug-in development.</p>
<p><strong><em>In PDE we do tooling, but our business is people! </em></strong></p>
</div>
<table border="0" cellpadding="5">
<tr height=9>
<tr>
<td width=20></td>
<td><a href="/pde/download"><img border=0 src="images/downloads.jpg"></a></td>
<td>
<table border="0" cellpadding="0">
<tr>
<td><font size=+1><a href="http://download.eclipse.org/eclipse/downloads/">Downloads</a></font></td>
</tr>
<tr>
<td>Get the latest and greatest PDE release.
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width=20></td>
<td><a href="/pde/support"><img border=0 src="images/community.jpg"></a></td>
<td>
<table border="0" cellpadding="0">
<tr>
<td><font size=+1><a href="/pde/support">Support</a></font></td>
</tr>
<tr>
<td>Find support and interact with users and developers.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width=20></td>
<td><a href="/pde/start"><img border=0 src="images/reference.png"></a></td>
<td>
<table border="0" cellpadding="0">
<tr>
<td><font size=+1><a href="/pde/start">Get Started</a></font></td>
</tr>
<tr>
<td>Resources for new users, links to tutorials and articles.</td>
</tr>
</table>
</td>
</tr>
</table>
</p>
<div class="homeitem3col">
<h2>PDE Components</h2>
<p>
The PDE subproject is broken down into three main components, Build, UI and API Tooling. Each of
these components operate like a project unto its own, with its own set of committers, bug categories
and mailing lists. There are two additional components in PDE, Doc which handles the help documentation
and Incubator which develops non-SDK features.
</p>
<table width="100%" border="0">
<tr>
<td width="20%" valign="top"><b>Name</b></td>
<td width="82%"><b>Description</b></td>
</tr>
<tr>
<td width="20%" valign="top"><a href="pde-build">PDE Build</a></td>
<td width="82%">Ant based tools and scripts to automate build processes</td>
</tr>
<tr>
<td width="20%" valign="top"><a href="pde-ui">PDE UI</a></td>
<td width="82%">Models, builders, editors and more to faciliate plug-in development in the Eclipse IDE.</td>
</tr>
<tr>
<td width="20%" valign="top"><a href="pde-api-tools">PDE API Tools</a></td>
<td width="82%">Eclipse IDE and build process integrated tooling to maintain API</td>
</tr>
<tr>
<td width="20%" valign="top"><a href="http://wiki.eclipse.org/PDE/Incubator">PDE Incubator</a></td>
<td width="82%">Development of new tools that are not ready to be added to the Eclipse SDK</td>
</tr>
</table>
</div>
<div class="homeitem3col">
<h2>Getting Involved</h2>
<p>
The development of PDE is driven by the community in an open and transparent manner. By getting involved with PDE, you can help influence the future of the platform improve the quality of Eclipse. There are many ways to assist, filing bug reports, contributing fixes, producing new features, participating in milestone testing, etc. Each PDE component has its own bug triage rules, coding guidelines, and testing format, however a good place to start is the PDE UI <a href="pde-ui/get_involved.php">Getting Involved</a> page.
</p>
</div>
</div>
<div id="rightcolumn">
<div class="sideitem">
<h6>Contributors</h6>
<ul>
<li><a href="http://www.anyware-tech.com/">Anyware Technologies</a></li>
<li><a href="http://www.eclipsesource.com">EclipseSource</a></li>
<li><a href="http://www.ibm.com">IBM</a></li>
</ul>
</div>
<div class="sideitem">
<h6>Newsgroups</h6>
<p>Got Questions?</p>
<p>Try out the <a href="http://www.eclipse.org/newsportal/thread.php?group=eclipse.platform.pde">newsgroups</a> [<a href="http://dev.eclipse.org/newslists/news.eclipse.platform.pde/maillist.html">archive</a>]</p>
</div>
<div class="sideitem">
<h6>Links</h6>
<ul>
<li><a href="pde-build">PDE Build</a></li>
<li><a href="pde-ui">PDE UI</a></li>
<li><a href="pde-api-tools">PDE API Tools</a></li>
<li><a href="http://wiki.eclipse.org/PDE">PDE Wiki Page</a>
</ul>
</div>
</div>
<?php
$html = ob_get_contents();
ob_end_clean();
# Generate the web page
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>