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

[Anton McConville <Anton.McConville@xxxxxxxxxx>]

- "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"

The short answer is yes, you can add your own JSON data into the project meta data, but the more forward thinking answer would be that we should evolve project data to consider generic elements that would be useful for multiple scenarios. So if you think your data fields would be helpful to others, let's work to do that.

- "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 ?"

Yes, and no. Yes in that members of the Orion team are familiar with Eclipse projects ( strengths and limitations ), and monitored how the Orion projects were taking shape, but no in that we didn't blindly take the .project file. Projects are very young, and we were eager to begin simply and progressively, so we're open to considerations still. It sounds like it might make sense to introduce some kind of compatibility. Our initial aims, as I suggested, were to introduce some new workflows through the user interface - to allow Orion to help embody goal driven projects, while considering ways to help inputs and outputs flow from it's cloud - so the current project data grew to support that initiative first.

- "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 ?"

I'm unhappy with how the workspaces behaves right now - and I'd like to adjust the behavior. The working set is there to allow a person to easily gather up the folders that are relevant to them for that project. I thought that adding a workspace in there might be helpful to lead the person into using the working set - and for it not to show up empty. Really that 'workspace' is just a folder in the default file system/drive that Orion runs on. So from that point of view, you could have many folders. The working set in project terms is a list of file system locations.

Anton



Matthias Sohn ---03/14/2013 07:03:20 PM---On Wed, Mar 13, 2013 at 5:28 PM, Anton McConville < Anton.McConville@xxxxxxxxxx

From:	Matthias Sohn <matthias.sohn@xxxxxxxxx>
To:	Orion developer discussions <orion-dev@xxxxxxxxxxx>
Cc:	orion-dev-bounces@xxxxxxxxxxx
Date:	03/14/2013 07:03 PM
Subject:	Re: [orion-dev] Rest API for project metadata

---

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_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev