#5117 Web-based commits, like GitHub and Google Project Hosting, with JavaScript-based source code editors

unreleased
open
nobody
None
General
nobody
2018-11-01
2012-10-14
Anonymous
No

Originally created by: marclaporte

Hi!

This is especially useful to increase contributions, especially for language files and CSS files. The current overhead of learning / setting up SVN is a hurdle.

Please see:
* http://dev.tiki.org/Web+Commits
* http://dev.tiki.org/Web-based+source+code+editor

And also:
* http://en.wikipedia.org/wiki/Comparison_of_JavaScript-based_source_code_editors
* http://googlecode.blogspot.ca/2011/01/make-quick-fixes-quicker-on-google.html
* http://github.com/blog/905-edit-like-an-ace

For Tiki, we use CodeMirror, which was deemed the best for our needs when we picked it and has been evolving nicely ever since.

We would like web-based commits of SVN files, but I suspect many will want it for other source control systems.

Thanks!

Discussion

  • Tony Becker - 2016-05-19

    I am interested in implementing this using the https://ace.c9.io/ editor, which is BSD-licensed. Seems like the complexity would be in generating the internal fork and PR that results from the edit(s). My use case for this would be mostly so non-technical users can submit documentation edits without getting too deep in the weeds.

    Before I go off in a direction that would not be mergeable later, does anyone have any thoughts on how this should work?

     
    • Dave Brondsema

      Dave Brondsema - 2016-05-23

      Sounds great. Another editor to look at is CodeMirror. It's homepage isn't as glitzy as Ace, but is pretty powerful and we are already using it for the markdown editor for all textareas. (It's a dependency of the SimpleMDE package).

      An initial version might be simpler to just do the commit directly, and rely on the user to make their own fork and PR. Also, SVN doesn't support forking/merging so it would be good for those repos.

      And it probably would be good to have a per-repo option to disable this if some projects don't want it. The "Disable one-click merge via web" option is very similar, and both help when a repo is a mirror of an official repo, and you don't want commits happening on the server at all.

      Let us know if you have any questions/thoughts as you go through it, this would be a great contribution!

       
      • Tony Becker - 2016-05-26

        I didn't realize CodeMirror was so featureful and already included in the
        project. That sounds like a better course.

        Agree on allowing per-repo option to disable, I had sort of assumed that.

        (I'm trying out the ticket-response-by-email feature!)

         

Log in to post a comment.