Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Merge-To: Merging on the fly

Wednesday, July 25, 2012 Amalia 0 Comments

Merging is a common operation that everybody does several times per day. Still, merging could be one of the most complex operations on a good version control system.

Plastic SCM is the good guy (our favorite hero in this adventure), it automatically solves as many conflicts as possible.

0 comentarios:

Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Plastic SCM Release 4.1.10.320 is out!

Monday, July 23, 2012 Amalia 0 Comments

Plastic SCM 4.1.10.320  has been released
The features of each Plastic SCM release, up to and including the latest version, can be found in the release notes page.
As you know we're releasing a new version weekly (in fact we produce new versions on a daily basis, but we announce once a week), and the last one we made public includes a few bug fixes you might be interested in:


  • We fixed a bug on the Tree List View that we've hunting for a while: sometimes double clicking a file wasn't opening it... now it was finally solved.
  • We had an issue with our built-in textbox on Linux systems (visible on the diff and merge tools): if a line started with tab or space, selecting the first char on the line was almost impossible. It is fixed now too.
  • 0 comentarios:

    Who we are

    We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

    If you want to give it a try, download it from here.

    We also code SemanticMerge, and the gmaster Git client.

    Plastic SCM Version Control System for Visual Studio 2012 Release Candidate

    Thursday, July 19, 2012 Amalia , 0 Comments

    Plastic SCM sim-ship with the next version of VS12


    We are happy to announce that the latest Plastic SCM release (from 4.1.10.315) works with the Visual Studio 2012 Release Candidate.
    Visual Studio is one of the most used IDEs by Plastic SCM users out there and that's why we're trying to continuously improve our integration with it.

    The new plugin allows our customers to implement full SCM operations and enjoy the new features in Visual Studio 2012: colors, fonts, UI text, icons .
    You can enjoy it in this video:


    Plastic SCM for VS12 is creating an experience, adapting its features for VS12 release candidate:

    Colors

    Visual Studio 2012 has two new themes, a light theme and a dark theme, in addition to the supported high-contrast OS themes. Plastic SCM works with both light and dark themes.


    Fonts and UI Text

    Font and comprehensible text is crucial to effective UI. In VS12, user can choose fonts and their styles, setting the font on a dialog, fonts in editors, etc. The Plastic SCM plugin for VS12, shown below, is capable of using all these advantages.


    Icons

    The updated Metro-style Visual Studio icons have simple geometry, clean lines, and only enough detail to communicate their meanings. Except for status notifications, new Visual Studio icons are gray-scale.  As you can see in the images below, the Plastic SCM plugin allows you to check the state of your files.


    Plastic SCM Settings 

    You can also select your Plastic SCM preferences.





    0 comentarios:

    Who we are

    We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

    If you want to give it a try, download it from here.

    We also code SemanticMerge, and the gmaster Git client.

    GlassFS: plastic made transparent

    Tuesday, July 17, 2012 Amalia 0 Comments

    Hi there! Moths ago we introduced glassfs as a prototype, but now I'm happy to announce it has been included on the latest 4.1 release!

    glassfs - the joke

    First things first: what glassfs means? Well, our motto during development was "glass makes plastic transparent" and that's where the name comes from.

    glassfs - the story

    Our first approach to glassfs, a couple of years ago, was to make scm operations as transparent as possible... at the end of the day the ideas there got integrated in 4.0 in our "transparent scm" initiative.
    We always got inspired by "ClearCase dynamic views" and, know what, developing in kernel mode on Windows was sort of a cool thing to do for some team members. After discarding some alternatives and after the final "transparent scm" thing turned "precise move tracking using kernel stuff" almost unnecessary (except for performance, but that's another story yet to be completed), we decided to revamp the "glass" project using the cool "dokan project" which is sort of a "Fuse" for Windows.

    What glassfs is about?

    Suppose you're on baseline 137 but you need to take a look at the sources back at baseline 130. In Plastic SCM you can go to the label, right click and browse the sources, opening the files you need to check. This is useful but sometimes you'll miss some sort of "grepping" on your files, won't you? If that's the case, the "explore label" functionality won't help, you'd have to open files one by one or simply switch your workspace to the baseline 130 (which is fast, but sometimes you don't feel like doing so).
    Glassfs comes to the rescue: it mounts a virtual drive on windows with the exact content of the branch, changeset or label you decide. And then you can access the files as you'd if they were on a regular directory... but without having to download everything to disk first.
    The "glassfs unit" is "virtual" and hence it will only read from the repository the files you really access.
    Cool, isn't it? It is some sort of read-only dynamic view. You can search text on the files using the tools you prefer...

    How to use it

    In this demo you can learn how to use glassfs.

    For example, if you run glassfs on your command line, you will see something like this, how to use glassfs:

    c:\ glassfs
    Usage: glassfs drive client.conf selector
    Example: glassfs z: c:\users\plastic\client\client.conf "rep 'codice' path
     '/' branch '/main'"
    

    Executing glassfs for first time, and may be you show this: you haven't got dokan.dll

    c:\Program Files\PlasticSCM4\client> glassfs v: c:\Users\Administrator\AppData\L
    ocal\plastic4 "rep 'codice' path '/' br '/main'"
    Unable to load DLL 'dokan.dll': The specified module could not be found. (Except
    ion from HRESULT: 0x8007007E)
    glassfs is not able to find a dll, most likely Dokan.dll.
    If that's the case download and install  http://dokan-dev.net/wp-content/uploads
    /DokanInstall_0.6.0.exe
    If still it can't find it, maybe you need a reboot or place the dll together wit
    h the glassfs binaries
    If you're here it means you don't have the Dokan FS Driver installed
    If that's the case download and install  http://dokan-dev.net/wp-content/uploads
    /DokanInstall_0.6.0.exe
    

    Then, downloading and install dokan.dll. You can find here,  Dokan library.


    And now, you can enjoy with glassfs, using your virtual unit :-)



    Limitations and future work

    Right now glassfs is limited to readonly, which means you can't write any files on that virtual drive. Practically it means if you open Visual Studio and try to "browse symbols" it won't work since Visual Studio tries to write temporary files on the paths where your project is.
     "Find in files" will just work, but "go to definition" of a symbol won't... yet! Yet, because we're working on a new version with temporary file support :)


    0 comentarios:

    Who we are

    We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

    If you want to give it a try, download it from here.

    We also code SemanticMerge, and the gmaster Git client.

    Plastic SCM Release 4.1.10.315

    Monday, July 16, 2012 Amalia 0 Comments

    In the latest releases of Plastic SCM, Enterprise DVCS,  versions 4.1.10.312 to 4.1.10.315 we introduced a bunch of new features and bug fixes. Beside the full release notes here, this blogpost will highlight some of them.
    Just in case you haven't downloaded this version yet you can do that here


    New Features

    Microsoft Visual Studio 2012 package

    Now, the new Visual Studio 2012 integration package is available in the Plastic SCM installer.
    Plastic SCM allows you to perform the most common version control operations directly from inside the Microsoft Visual Studio 2012. You can enjoy our context menu, pending changes view, integrated diff, branch explorer, workspace explorer, ...


    pending changes view in Plastic SCM



    "Switch to new branch"

    Under this title we implemented a new feature to make your life easier.
    Now when you open the Create Branch dialog:

    • The default option should be from Changeset, not from Label
    • The checkbox "Switch to this branch" should be recorded, so the next time the Create Branch dialog is opened, shows you the last decision pick up by user.

    Bugs Fixed

    Timestamp of the changeset zero can be updated

    Plastic SCM team discovered that we are working on a replicated repository, Changeset Zero, didn't got the oldest date.  

    We have fixed it so the Changeset view or other queries based on date work properly.



    GUI MAC, drop down buttons in Pending Changes view on MAC

    Plastic SCM team fixed an issue with the menu in the dropdown buttons in the Pending Changes view, GUI MAC.
    The first time you click on the arrow to expand the "Checking changes" button in the Pending Changes view, it works. But the next time, the items of the list are not selected, so you can not shelve or check the changes to other branch.


    
    

    0 comentarios:

    Who we are

    We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

    If you want to give it a try, download it from here.

    We also code SemanticMerge, and the gmaster Git client.

    Webinars: Always Learning

    Thursday, July 05, 2012 Amalia 0 Comments

    Plastic SCM Webinars

    You can review all our webinars in Plastic SCM You Tube channel
    We suggest you some of them:

    Shelving is a way of saving all of the changes on your box without checking in.

    Plastic SCM, the only DVCS in the world with exclusive checkout

    Review all the usability improvements. Our lives will be easier will all these shortcuts!

    In real world, every day you have directory conflicts. Plastic SCM resolves all of them.

    0 comentarios: