Suggestion: Don't use overloaded Point and Range terms in API

One thing that we ran into problems with the original API were the Point and Range classes. Since the browser APIs contain classes named the same, we ran into naming collisions causing issues for those attempting to use the Atom API. I figured I would record this piece of tribal knowledge here so that we can avoid it in Xray.

Suggestions

Alternatives for Point:

• Location
• Coordinate
• Position

Alternatives for Range:

• Span
• Section
• Bounds
• Dimension
• Limits