Changes between Version 40 and Version 41 of DevelopersGuide/DevelopingPlugins

Timestamp:

2010-01-12T19:50:49+01:00 (15 years ago)

Author:

stoecker

Comment:

typo

DevelopersGuide/DevelopingPlugins

@@ -66 +66 @@
   * '''DONT''' use special characters in the plugin name, stick to alphanumeric characters. Call the plugin {{{routing4all}}} not {{{routing 4 all :-) !}}}. Note that the plugin name is used to '''create file and directory names''' on the computer where plugins are installed. If it included special characters like /, ., \, etc. these operations may fail. 
 
-You are recommended to use a Java package for the plugin main class and all other classes you need in the plugin, i.e. {{{org.foobar.josm.routing4all}}}. Stick to the well-established naming conventions used in the Java world (lower case package name, camel case class names, etc.). The required minimum in package naming is one individual part in the path structure of your plugin class names. The path of the base class is used to detect the source of exceptions. So when you base class is my.example.class.MyPlugin, then "my.example.class" is used to detect your plugin code. All important parts of your plugin should use that and also it should be unique for the plugin (i.e. add at least one part with the name of your plugin).
+You are recommended to use a Java package for the plugin main class and all other classes you need in the plugin, i.e. {{{org.foobar.josm.routing4all}}}. Stick to the well-established naming conventions used in the Java world (lower case package name, camel case class names, etc.). The required minimum in package naming is one individual part in the path structure of your plugin class names. The path of the base class is used to detect the source of exceptions. So when your base class is my.example.class.MyPlugin, then "my.example.class" is used to detect your plugin code. All important parts of your plugin should use that and also it should be unique for the plugin (i.e. add at least one part with the name of your plugin).
 
 == Callbacks == #Callbacks