Re: [orion-dev] Rest API for project metadata

[Matthias Sohn <matthias.sohn@xxxxxxxxx>]

On Wed, Mar 13, 2013 at 5:28 PM, Anton McConville <Anton.McConville@xxxxxxxxxx> wrote:

Hi Christian,

Orion is really only just beginning to establish it's concept of projects. There's so much scope for it. I can see the benefits too, of having REST APIs for the project data - the more easily accessible data, the better, as far as I'm concerned ( my opinion only! ). It'd be exciting to see how projects could scale across applications.

Probably the next steps for projects will be to complete the user interface some more, to make it a good home for the goals of your work when using Orion.

I've filed a bug to track the request/requirement for an API for the project meta-data:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=403228

We'd love it if you helped us define projects more, given your user story. Please think about joining in the development of it. You can contact me or John directly, or join in the weekly Orion call, or bi-weekly User Engagement Hangouts. Event info here: http://wiki.eclipse.org/Orion

Chris is in my team, together with Stefan Lay and Michael Ochmann we are evaluating

how to use Orion to integrate a couple of web based development scenarios including the

RAD environment for mobile applications Chris was mentioning.

The results we reached so far look promising and we got positive feedback on an internal demo

we did recently so there is a good chance that we can start contributing soon.

Stefan and myself are at EclipseCon in Boston and it would be great if we could meet some

of you there to learn more about Orion.

Back to questions and requirements for the project support in Orion:

- we need different types of projects and hence would like to store some additional project meta

  data so it would be great if the project data model would be extensible. It seems at the moment

  we can extend it by simply adding additional custom properties which seem to be ignored by Orion

- some of our tools can also be used from a traditional Eclipse workbench so sources which were

  edited in Orion could be committed to Git and pushed to the git server which is also accessible

  from the Eclipse workbench using EGit. Hence it would be beneficial if the projects would be

  interoperable or at least translatable between these two environments. Did you consider to

  use the traditional .project file format ?

- looking at the current representation of projects in Orion 2.0 what's the idea of workspaces

  located underneath the node "projectData" ? Can the same user have multiple workspaces ?

--

Matthias