[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[udig-devel] Developers Guide is starting to come together.
|
Over the last week we have been researching and laying out the
guidelines for uDig development for addition to the Developers Guide
- http://docs.codehaus.org/display/UDIG/Developers+Guide
- http://docs.codehaus.org/display/UDIG/Repository%2BStructure
- http://docs.codehaus.org/display/UDIG/Plug-In+Structure
I am going to cut&paste a bit for discussion purposes:
Project Example Naming Convention
Plug-In net.refractions.udig.render named in agreement with internal
package structure
JUnit Test Plug-In net.refractions.udig.render-test Append "-test"
Plug-In Fragment net.refractions.udig.german Provide "./language/"
file at the root udig
Plug-In Fragment net.refractions.render-1 Do anything except add a dot
Features net.refractions.udig.render-feature Append "-feature" to
associated root Plug-In
Java Project gml no convention
For a plugin: net.refractions.udig.xyz:
* net.refractions.udig.xyz:
Provides public API referenced by other plug-ins, interfaces
referenced by other plug-ins go here. This is optional.
* net.refractions.udig.internal.xyz:
Implements extention points intergrating this plug-in with the
uDig Framework. This is usual.
* net.refractions.udig.internal.xyz.etc:
You can use additional packages inside your internal package.
Some interesting reading for RCP stuff:
http://www.eclipsepowered.org/
