AgileApps Support Wiki Pre Release

Difference between revisions of "Add a Class"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 5: Line 5:
:* Classes in the same package can access each others package-protected fields and methods, as well as their public members, without doing an <tt>import</tt>. So classes that cooperate with each other extensively generally belong in the same package.
:* Classes in the same package can access each others package-protected fields and methods, as well as their public members, without doing an <tt>import</tt>. 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 <tt>import</tt> declaration.
:* Classes that are part of a different package can be accessed with an <tt>import</tt> declaration.
[[File:newclass.gif|right|thumb]]


====To add a class:====
====To add a class:====

Revision as of 19:27, 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:

  1. Click Designer > Logic > Classes
  2. Click [New Class]
  3. Fill in the class properties.
  4. 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}
Class Name
The name of the class
Java code
Enter Java code in the text area.