Active
Project:
Git on Drupal.org
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Sep 2011 at 06:34 UTC
Updated:
28 Mar 2013 at 16:17 UTC
https://github.com/ajaxorg/ace superb yummy! Online editor! Most excellent for small fixes.
Comments
Comment #1
boobaa/me seconds. This would be simply wonderful.
Comment #2
nevergone+1 :)
Comment #3
sdboyer commentedi'm actually using ace for a different project, so, becoming more familiar with it day by day.
the tricky thing with providing a direct interface to our code is getting direct *access* to it - we have to read the data straight out of git, which is on a remote machine. hardly insurmountable, but we've been dallying about it for a while. a simple enough node.js server to just grab the data and pass it back would be fine...we just haven't done it, because we haven't had the use case on the frontend clearly defined.
and, to that end, "adding ace" isn't sufficient to describe the use case you're looking to satisfy. do you just want a better code viewer? or do you actually want to be editing repository contents in the browser? where should this fit in?
Comment #4
chx commentedediting repository contents in the browser - yes please.
Comment #5
sdboyer commentedok so, off the top of my head, what we need for that is a standalone system (so that we can have it on a separate domain, for the same reasons that we have drupalcode.org on a separate domain) that can authenticate against d.o and authorize against project credentials. then, in addition to ace itself, we need a UI that can facilitate writing a commit message, and that can reuse committer information from d.o to mark up commit ownership correctly. it'll also need to be sensitive to any pushes that happen to the repo simultaneously, so that it can update itself and notify the user, or at least NOT blindly try to commit code when the edits were done against stale versions of file(s).