<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Mozilla/4.7 [en] (WinNT; I) [Netscape]">
<title>org.eclipse.ercp.swt.expanded.common</title>
</head>
<body>
<b>org.eclipse.ercp.swt.expanded.common</b>
<p>This folder holds common SWT code that can be used across Expanded eSWT
implementations. The classes are contained in subfolders that match the
SWT desktop source folder names. This folder represents a Simple Project
(i.e., it is not a Java Project). It is not meant to be loaded in your
Eclipse workspace. It is meant to be shared across eSWT implementations
via CVS modules. CVS modules work like linked resources (Eclipse concept)
or symbolic resources (Linux concept). A CVS module is defined for each
subfolder in the org.eclipse.ercp.swt.core.common folder:
<ul>
<li>eswt-expanded-common --> module for SWT-common folder</li>
</ul>
<p>These above definitions exist in the modules file of the CVSROOT repository
component. An Expanded eSWT implementation can then reference these modules. For
example, the org.eclipse.ercp.swt.expanded.win project (i.e., the win32/wm2003
implementation of Expanded eSWT) defines itself in the modules file as follows:
<pre> org.eclipse.ercp.swt.expanded.win org.eclipse.ercp/org.eclipse.ercp.swt.expanded.win &eswt-expanded-common</pre>
<p>The above indicates that the org.eclipse.ercp.swt.expanded.win module consists of
the org.eclipse.ercp/org.eclipse.ercp.swt.expanded.win folder plus the common SWT code
modules. Access to the modules file in CVSROOT is restricted. To define a module,
you must send a request to webmaster@eclipse.org. Please follow module naming
conventions similar to what is defined for the Expanded eSWT win implementation.
</body>
</html>