152 results found
-
Export Branch Explorer to Image (png/jpg).
It's nice to capture a full-resolution (zoom=1) snapshot of the current BranchExplorer view for a number of reasons like presentations, sprint celebrations, framed photos for product milestones etc.
In most cases I have to zoom out to an unacceptable level to see a couple of weeks of work on the branch and having a full-res image would help.
3 votesWhile it is certainly interesting, we are discarding this at the moment because it didn’t generate enough interest.
-
'cm diff' should compare a file against previous revision by default
'cm diff' compares against the last checked in revision if the file is modified in the workspace. If it is not, it just gives a message "Item has only one revision". It would be more useful if in this case it compared the last two revisions. Finding appropriate revision numbers on the command line is not easy.
3 votesIt’s the current behavior
-
Add XML to SemanticMerge
Seems many people save xml files as 1 huge long string. This makes line by line comparison rather worthless. If SemanticMerge could parse xml this would make comparison and merge of xml files so much better.
6 votesGood idea. But please add it to the semanticmerge area :P. We already have it in mind.
-
Qt Creator & MonoDevelop Integration
I wish support for Qt Creator and MonoDevelop 4 since is our IDE of choice for our development process. Thanks.
1 vote -
annotate whitespace and eol options
As far as I can see, the GUI is missing the useful --ignore options from the command line.
22 votesIn the annotate view, if you click on the “Options” button, you will be able to configure it.
-
Quick Diff
Quick Diff support for Eclipse.
That makes it possible to see the Diff status, in a ruler, when you edit a file.3 votes -
License information on home screen
I would like to access the license information, and be able to add a new license, from the first screen where I can select diff or merge.
3 votesI think this refers to semanticmerge instead
-
Random file name in external diff tools
When you diff files using an external tool, Plastic SCM creates temporary files for the revisions being compared, but generates random names for them. So when the diff tool opens, the file names it displays are like "tmp210f.tmp.vb". After a while you forget which file you are viewing and these names are not helpful :).
IMHO it would be much better if original file names were used, extended for instance with changeset numbers so they don't repeat.
3 votesAs pointed, it is already doable
-
Protecting the main branch from accidental check-ins
Sometimes you may start working on the main branch unaware without creating a child branch first. You get in trouble if your dirty changesets are used by others.
A good solution to protect the main branch from accidental check-ins is to deny users the check-in right on main branches. To perform a check in from their child branches they will have to log in as a different user (as an 'integrator').
The problem is that it is cumbersome. You have to run the Plastic SCM client configuration wizard to log in as an 'integrator' and then remember to switch back…
9 votes -
visibility per workspace
It would be nice to be able to define visibility rules per workspace and not per repository.
6 votesNever got an answer :-(
-
Plugin for netbeans
Is one of the most used IDE of the JAVA development and is the one i use more because of his GUI designer, feature that eclipse doesn't have for free or erent enought good
60 votesDeclined at least temporarily. NetBeans users can take advantage of “transparent scm” while we get enough requests to consider it again.
-
Create a admin tools that make it easy to push out setup rules for repositories.
We have multiple repositories and as a company we try to name everyone's workspaces the same and put them in the same location on everyone's computer. It would be nice if there was an admin tool that would just make it so as someone loaded Plastic, it would just set that stuff up.
3 votesThe request has been staying around for years and nobody else voted for it.
-
automatically found moved/deleted files
Sometimes plastic doesn't recognize a moved file because it moved and changed and some other times when a duplicated files is deleted plastic thinks it was moved.
Therefore it would be nice to have the option to change these things right in the pending changes view. Maybe just a context menu option for deleted files: "File was moved" and for moved files: "File was deleted"3 votesThis is the “search moves” option in pending changes
-
Context menuitem for writable.conf
Title says it all.
3 votesDidn’t get enough support in about 3 years :-(
-
Close Diff / Merge tools with escape button
Allow Diff / Merge tools to be closed with escape button - very helpful when perform comparison of multiple files before Check In from Visual Studio.
3 votesShouldn’t you use standard CTRL-F4 to close it? It works on every windows app, doesn’t it? :)
-
3 votes
We’re not sure if you are talking about semantic merge here.
-
Visual Studio Plugin - In the Checkin changes window, CTRL+SHIFT+Enter to Commit changes and comment.
I'm a huge fan of not moving my hand to the mouse whenever possible and I check-in quite often so this could be a huge productivity gain with a simple fix.
0 votesThanks! :)
-
rules to exclude file segments from change detection
We have a lot of automatic generated files which are under version control.
These files often contain a timestamp of their creation and some other information which aren't that much important and don't need to be controled by plastic.
The idea: It would be nice if I could define a rule (maybe using a regex) to define lines or segments in these files which maybe change but don't cause plastic to show them as pending changes.
3 votesWe have something called the hidden changes list. Why don’t you check it?
-
Support components-based development
A number of forum and uservoice conversations show that XLinks in their present implementation are not sufficient for common scenarios of component-based or modularized development. While XLinks may be an elegant and powerful idea, they are not a replacement functionality of working with subtrees provided by virtually every other system, from SVN to Git and including Plastic SCM 3. Further, a basic solution can be implemented in Plastic 4 with shell scripts and cloacked.conf. Some native means of working with components in subtrees of a repository would be very useful.
7 votesWe consider Xlinks a powerful enough solution for component oriented development in its current form, and most of the customers agree.
Git support is no better at all (it is quite weak compared) to Xlinks (you’ve to handle the dependencies manually with Git).
-
Xlinks to single files (VSS style)
We would like to convert from VSS to Plastic SCM, but VSS's file sharing works completely different than Xlinks in Plastic SCM (as far as I understood).
Firstly, there needs to be a possibility of creating xlinks to single files, just like in VSS. It is really important for us. We want to share single code files and single binaries between projects. Sharing the whole project (as a repository) when only its binary file is needed (or several code files) is no solution to us :-(.
Secondly, there should be two xlinks modes:
A link to a specified revision -…
3 votesXlinks to files doesn’t seem to be a popular idea and it almost breaks the underlying concept.
- Don't see your idea?