Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Scout/Coding Guidelines"

(New page: {{ScoutPage}} This page collects the coding guidelines for the Eclipse Scout project == API Compatibility == The scout RT API are downwards compatible with your the previous release. So...)
 
(Additions)
Line 9: Line 9:
 
=== Additions ===
 
=== Additions ===
  
Addition of a method on an interface is allowed if the default implementation is provided.
+
Addition of a method on an interface is allowed if the default implementation is provided:
 +
 
 +
This holds for
 +
* Abstract model classes: e.g. org.eclipse.scout.rt.client.ui.form.fields.stringfield.AbstractStringField
 +
* UI Fields: e.g. rg.eclipse.scout.rt.ui.swing.AbstractSwingEnvironment, org.eclipse.scout.rt.ui.swing.form.fields.browserfield.internal.SwingScoutBrowserField
  
 
{{Note|TODO|extend this section}}.
 
{{Note|TODO|extend this section}}.

Revision as of 07:59, 6 May 2013

The Scout documentation has been moved to https://eclipsescout.github.io/.

This page collects the coding guidelines for the Eclipse Scout project

API Compatibility

The scout RT API are downwards compatible with your the previous release. Some modifications are marked with the keyword migration in bugzilla meaning that some modifications are requested.

Additions

Addition of a method on an interface is allowed if the default implementation is provided:

This holds for

  • Abstract model classes: e.g. org.eclipse.scout.rt.client.ui.form.fields.stringfield.AbstractStringField
  • UI Fields: e.g. rg.eclipse.scout.rt.ui.swing.AbstractSwingEnvironment, org.eclipse.scout.rt.ui.swing.form.fields.browserfield.internal.SwingScoutBrowserField
Note.png
TODO
extend this section

.

Back to the top