| Re: [orion-dev] Potential contributions for UCOSP student |
That sounds good, definitely something I'd be interested in doing. Unless something comes up otherwise, I'll talk to Andrew Ross about moving ahead with this.
Cameron
On Mon, Jan 21, 2013 at 9:35 AM, Andy Clement <andrew.clement@xxxxxxxxx> wrote:
Hi,
As Ken says, in Scripted we are running some bits and pieces on Node to feed the client with extra information on dependencies (which drives cross file content assist and navigation). This is encapsulated in the jsdepend library in scripted. Given the simplicity of our server side, I don't think it would be too tricky to run this library in another Node environment. Obviously it interacts with the filesystem but I believe there is an abstraction (or at least the beginnings of one) in there so it can be fed by whatever filesystem you have around (i.e. it doesn't use Node 'fs' directly). Obviously we don't have any other consumers of this yet right now so it hasn't been designed for re-use but in principal I don't think the task would be too tricky and we'd be amenable to changes that make it more easily consumable.Andrew can comment more specifically on activating the client side to utilize that info, but I think on the client side everything is there, it is just waiting for the data from the server.cheers,AndyOn 20 January 2013 11:27, Ken Walker <Ken_Walker@xxxxxxxxxx> wrote:
Welcome Cameron!
The Git REST command line might be interesting however we have some students in Poland working on some Git work for our Node server - likely not overlapped but maybe your focus elsewhere would be good.
Working on the Tasks might be a good approach and containable within the timeframe.
One item we were talking about last week was that the VMWare developers are utilizing the Orion editor in a stand alone desktop editor called Scripted. Scripted contains some of the same content assist code as Orion (they contributed back many features to Orion) but they have a hook to the Node file system to introspect over the files 'close' to the file you're editing to provide better content assist including understanding Node module support. It would be a very interesting task to look at how to utilize this in our Node.js version of Orion. Currently we do not do this, we just have the context of the file you are editing.
You can see an example of this module support for content assist here: http://blog.cloudfoundry.org/2012/10/11/using-the-new-scripted-_javascript_-editor-for-node-js-development/
The work would be adapting their content assist code to use our file system API on node.
I'm not sure this could be completely completed in the time frame you mention so perhaps Andy or Andrew could comment on how hard this task might be.
All the scripted source is available in the open as well (https://github.com/scripted-editor/scripted)
Any help on an area of Orion is welcome. Others on the list may have some suggestions as well.
Ken Walker
Co-Lead Eclipse Orion Project | Tools for the Web, On the Web
http://orionhub.org | http://wiki.eclipse.org/Orion
@k_e_n__w | @orionhub
Cameron Mann ---2013/01/20 02:05:51 PM---Hi all, I'm a participant in the UCOSP (http://ucosp.ca/) program being mentored by
From:
Cameron Mann <cpmann@xxxxxxxxxxx>
To:
orion-dev@xxxxxxxxxxx,
Date:
2013/01/20 02:05 PM
Subject:
[orion-dev] Potential contributions for UCOSP student
Sent by:
orion-dev-bounces@xxxxxxxxxxxCameron Mann_______________________________________________
Hi all,
I'm a participant in the UCOSP (http://ucosp.ca/) program being mentored by Andrew Ross and I was interested in contributing to Orion. I'll be doing ~8 hours of work per week until early April and I wanted to get some feedback on what could be a feasible contribution. I've been browsing the bug tracker and found a couple areas that were interesting to me as potential options.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=372119
https://bugs.eclipse.org/bugs/show_bug.cgi?id=361909
https://bugs.eclipse.org/bugs/show_bug.cgi?id=366722
With regards to the last one there it seems like there's a number of tickets related to improving tasks so I'd also be open to any of those or some combination thereof. Since I'm unfamiliar with the project I'm basically interested in figuring out which of these choices would be reasonable (or most reasonable) for a term project. I've got a decent amount of experience with Java through school though I have almost none with _javascript_ so I'd have to pick that up as I go.
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev