Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340822 - [client] change eclipse variable namespace to orion
Summary: [client] change eclipse variable namespace to orion
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.2   Edit
Assignee: Simon Kaegi CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-23 19:13 EDT by Susan McCourt CLA
Modified: 2011-09-01 11:41 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2011-03-23 19:13:35 EDT 
I noticed that some of the newer files (assert.js) use the orion variable namespace instead of eclipse.  We should switch everything else over at some point.
Comment 1 John Arthorne CLA 2011-03-23 21:09:06 EDT 
For many things we should really just stop declaring globally-scoped variables at all. For example anything that is intended to be accessed via the service registry doesn't need to occupy the global namespace.

Of course we will end up with various helper objects and functions that should be consolidated under a single top-level variable... orion is likely better than eclipse for this purpose.
Comment 2 libing wang CLA 2011-03-24 10:42:03 EDT 
git status and compare editor stuffs are already in orion name space.
Comment 3 John Arthorne CLA 2011-06-06 09:22:57 EDT 
This was done for M8.