The merge tool that understands your code

← semanticmerge

JavaScript, please!

C# is nice, but JavaScript rules the front-end :)

869 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    Arve Knudsen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    19 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Forgot password?
      Create a password
      Signed in as (Sign out)
      Close
      Close
      Submitting...
      • Joe Coutcher commented  ·   ·  Flag as inappropriate

        No JavaScript/JSON/TypeScript semantic merge support is kinda a deal breaker...especially when work has been "started" for 5 years now...

      • R. Joe Reich commented  ·   ·  Flag as inappropriate

        Looking for updates, ESPECIALLY for a Typescript parser. Considering how there is specific and definitive type-definitions for TypeScript it seems like it would be almost easier to implement than for JavaScript.

        Is the delay because actiprosoftware.com doesn't have implementations for either of them yet?

      • Anonymous commented  ·   ·  Flag as inappropriate

        Is this alive? started September 2013, last update on Feb 16... seems to be "moving" very slowly. Any updates? Would love to support with buying couple dozen licenses for this alone.

      • AdminCodice Software (Admin, plasticscm) commented  ·   ·  Flag as inappropriate

        Hi all!

        * You can download the javascript parser and some examples here: http://www.semanticmerge.com/parsers/semanticmerge-js-parser.zip
        * Please, unzip and copy the folder at: C:\Users\<youruser>\AppData\Local\PlasticSCM4\semanticmerge
        * The parser for javascript language should be specified through the -ep option when the @semanticmerge is launched
        e.g: -s=src.js -b=base.js -d=dst.js -r=result.js -ep="\"C:\<nodepath>\node.exe\" \"C:\<parserpath>\run.js\""
        * Also, you can check the scripts which are used to launch the js examples (sample-x*.bat)

        In addition, you need a license with external parsers support (javascript). Please, write us to support and we will generate you a license for testing purposes.

        Let me know if it helps!

      • Steve McCormick commented  ·   ·  Flag as inappropriate

        is there any update on the JavaScript parser? There was a comment saying that a version had been written about a year ago - is that available in the latest version on Plastic?

      • Anonymous commented  ·   ·  Flag as inappropriate

        Do TypeScript (first) and you will get JavaScript at the same time. Everyone should stop using JavaScript anyway and go with TypeScript. Since it is a superset of JavaScript there is no problem for those that want to write plain JS, but the option to type stuff is there for those who want to use it.

      • Ken commented  ·   ·  Flag as inappropriate

        So do you guys have any plan of when you would be releasing the JS version? And do you have a GUI for OSX? If I can have both, itd be my dream come true!!!! I always thought about language-based merging. And I finally found you guys!!!

      • psantosl commented  ·   ·  Flag as inappropriate

        We have a Javascript parser up and running, but we never made it public. We shared it once with this list. If anyone is interested... drop me a tweet @semanticmerge

      • gihrig commented  ·   ·  Flag as inappropriate

        Ah... JavaScript is not Java. Java is now available (November 1). Did, actually mean that work has begun on JavaScript?

        I'm working in Node and Backbone, so it's JavaScript everywhere, would love to see Javascript support (on OS X) ;-)

      semanticmerge

      Feedback and Knowledge Base

      (thinking…)