Difference between revisions of "Add a Class"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 16: | Line 16: | ||
====Class properties==== | ====Class properties==== | ||
:;Package:The package name | :;Package:The package name | ||
::*The platform supplies this part: <tt>com.platform.{namespace}</tt>, where {namespace} is defined in the [[Developer Configuration]] settings of the current tenancy. | ::*The platform supplies this part: <tt>com.platform.{namespace}</tt>,<br> where {namespace} is defined in the [[Developer Configuration]] settings of the current tenancy. | ||
::*You supply this part: <tt>{packagename}</tt> | ::*You supply this part: <tt>{packagename}</tt> | ||
::: The result is the fully-qualified package path for the class: <tt>com.platform.{namespace}.{packagename}</tt> | ::: The result is the fully-qualified package path for the class: <tt>com.platform.{namespace}.{packagename}</tt> |
Revision as of 19:25, 3 June 2011
Prerequisite
Before you create a class, you need to decide what package to put it in. Here are a few notes to help you make that decision:
- Packages let you organize classes into different directories according to their functionality, their usability, or any other category that makes sense. (The only rule is that classes in one package have a qualitatively different kind of functionality compared with those in another package.)
- Packages help to avoid class name collision. (The same class name can be used in different packages.)
- Classes in the same package can access each others package-protected fields and methods, as well as their public members, without doing an import. So classes that cooperate with each other extensively generally belong in the same package.
- Classes that are part of a different package can be accessed with an import declaration.
To add a class:
- Click Designer > Logic > Classes
- Click [New Class]
- Fill in the class properties.
- Click [Save]]
Class properties
- Package
- The package name
- The platform supplies this part: com.platform.{namespace},
where {namespace} is defined in the Developer Configuration settings of the current tenancy. - You supply this part: {packagename}
- The result is the fully-qualified package path for the class: com.platform.{namespace}.{packagename}
- The platform supplies this part: com.platform.{namespace},
- Class Name
- The name of the class
- Java code
- Enter Java code in the text area.