|Re: Extending Orion with Plugin without using the Orion server [message #1090074 is a reply to message #1085794]
||Mon, 19 August 2013 17:19
| Mark Macdonald
Registered: July 2009
Yes, it is possible. The Orion client code is not coupled to the Orion server; instead the client depends on various service APIs (for example: file storage, preference storage, etc). Service APIs are usually implemented by a plugin (= a web page embedded in an IFrame). Alternatively services can be implemented without using plugins: this allows you to write your whole app in a single static, traditional web page if you desire.|
So basically, you can host the Orion client code pretty much anywhere, without requiring any particular back-end server.
I would start by determining what your app's needs are. Do you want the full Orion UI? Are you interested in making your app extensible with plugins? Do you want the ability to traverse a hierarchy of files and folders, or just a simple editor that only handles a single kind of file?
Depending on what your needs are, you can try either of these options:
- Full Orion UI + service registry
Start by looking at the page that provides the full Orion editor (edit.html and the related files setup.js, defaults.pref). The defaults.pref file gives the URLs of the default set of plugins that the Orion UI will try to load. You can replace those as needed. The setup.js file does most of the page initialization, which you can also modify to add or remove additional UI components or services.
- Just an editor
Start by looking at embeddededitor.js and edit.js -- these give an example of a simpler web page. The page has no service registry and no plugins, but it still provides a full-page editor with content assist and syntax highlighting.
Powered by FUDForum
. Page generated in 0.01936 seconds