1234461 - Define base JS implementations of JsAccount objects

Status: RESOLVED DUPLICATE of bug 430716

(MailNews Core :: Backend, enhancement)

Description

[Kent James (:rkent)]

In bug 430716, JsAccount is introduced. That implementation suggests two variations for how to create objects for JS accounts:

1) Define a component that derives directly from the relevant JsAccount component (see for example testJaBaseUrlComponent.js and testJaBaseUrl.jsm)

2) Define a component that derives from a base JS implementation and extends it (see testJaFooUrl.js).

Although those methods are very similar there are some differences. In the long run, we want to have base JS implementations of all JsAccount classes, so we want extensions to use the second method, deriving from a standard JS implementation of each class.

This point of this bug is to define standard, stub JS implementations of the base classes in JsAccount that will be used as the parent of any extension-developed JsAccount types. The stubs will be extended over time, possibly replacing eventually the core C++ base classes.

We want extensions to be defined from the start deriving from the JS classes rather than the C++ classes, so these need to be defined before extensions start making extensive use of this.

Comment 1

[Kent James (:rkent)]

In the latest patch for bug 430716, I started to include these in the first JsAccount patches, so this bug gets absorbed by the original bug.