Community
Participate
Working Groups
The orion file service is now contributed by a plugin, which allows files to be served from a different server than the one providing the orion tools. To take advantage of this, the orion editor needs to use the file service to get/set editor contents. As part of this, I propose axing the "ISaveable" service. This service doesn't represent a saveable entity like it does in Eclipse desktop. Instead it is a universal "saver" service that knows how to save arbitrary contents to arbitrary URLs. This really needs to be paired with the service that obtains contents for the editor. In the future we may have a need for a "saveable" abstract for things like writing subsets of files, writing objects that cross multiple files, etc. However, the current incarnation of the service doesn't address any of these needs.
Fix released.
