API Geometry Exposure

[james-rae]

Update:
after haggling, was decided to go with the old RAMP.GEO style. When possible, error checks will be done for attempting to access stuff before GeoAPI has initialized

RAMP 2

Exposes the geometries on global RAMP.GEO.*

var myRampPoint = new RAMP.GEO.Point(parms);

RAMP 4 Similar

Also expose the geometries on RAMP global.

We can keep the GEO grouping or rename it.

The geometry classes are not tied to an instance of RAMP so this is fine.

Main benefit is would allow older code to be migrated as-is.

RAMP 4 Instance

Alternately put the classes on the instance.

Pagecode

function initRAMP() {
    var rInstance = new RAMP.Instance(params);
    var myRampPoint = new rInstance.geo.Point(otherparams);
}

Internal code

var myRampPoint = this.$iApi.geo.Point(parms);

The one possible pro here is that most code will be working with the instance API and not the global RAMP api, so saves them having to go back to the window object.

Also, the Geometry classes will not exist until GeoAPI has loaded, which is what initRAMP guarantees, so perhaps that is another advantage.

Lets Haggle

Thoughts?
Preferences?
Alternatives?
Grouses?

[james-rae]

Final solution. It is available both on the global RAMP var as well as on an Instance API via the .geo nugget. There is no longer a separate GeoAPI library so concerns about timing the loading of the lib are moot.