531 results found
-
VS plugin: Add in-editor diff markers with associated commands
We were using the VisualSVN plugin for Visual Studio before, and we miss the excellent "Quick Diff" feature: https://www.visualsvn.com/visualsvn/features/
This feature replaces/enhances the "Track Changes" markers in the Visual Studio code editor with colored lines (in the left margin), to indicate blocks of lines that are changed relative to the latest changeset (different colors for modified, added, deleted). It also adds commands (revert block, navigate prev/next change block).
There are some other (open source) plugins that offer similar functionality: "Git Diff Margin", "TfsPendingChangesMargin", "HgVS".
12 votes -
Switch/Update should include metadata for cloaked items
As it is, "cm ls" and the Items view will not show cloaked items after an initial update/switch in a new workspace, since metadata for the cloaked items has not been fetched.
If you perform a "cm update --cloaked" and then delete the cloaked items, they will still show up in "cm ls" and in the Items view (as "Cloaked / Not on disk"), since the metadata has then been fetched into the workspace.
Besides consistency and always having a simple way to see that there are cloaked items, this actually makes a practical difference when having multiple cloaked items…
6 votes -
Visual Studio plugin: Jump to current line when opening Annotate
When opening Annotate from the code editor in Visual Studio, pre-select the annotated line that corresponds to the cursor position in the code editor (and scroll it into view).
7 votes -
Improvements to the Annotate view
Taking some ideas from TortoiseBlame:
When right-clicking a changeset/line, add a choice "Annotate previous changeset" (this is so you can trace the earlier history of the line you're interested in).
When right-clicking a line and choosing "Diff contents of branch/changeset ...", the file that you are currently annotating should be pre-selected in the Comparison window that appears.
Use a tooltip box to display log message (and branch, date etc) when hovering the mouse pointer over a changeset/line.
Remove the horizontal color gradient. While a nice effect, it distracts from the per-date/author color gradient.
Add automatic coloring of changeset text to…
47 votes -
Follow active workspace when showing user in window title
When the preference "Other Options - Show current Plastic SCM user in the window title" is active, it always displays the username configured under "Preferences - General". If there are connection profiles stored under "Preferences - Profiles", this may not be the same user that is logged in at the active workspace. It may not even be a valid user at all, since you will be transparently connected if there is a valid profile.
To be really useful and accurate, the username displayed in the window title should be updated every time the active workspace changes - instead of blindly…
4 votes -
Add context menu on "background" in Items List view (and Windows Explorer)
When the Items view is in "List view" mode, there should be a context menu when right-clicking on the white background (as opposed to right-clicking on a file or directory). This context menu should display choices relevant to the "parent" folder we are looking into.
Likewise, in the Windows Shell extension, the Plastic SCM context submenu that appears when right-clicking on the white background in Windows File Explorer should display choices relevant to the parent folder (the same choices you get if you go one level up and right-click on the folder in question).
This is how Windows File Explorer…
3 votes -
Remember splitter heights in "Diff changeset" and "Explore changesets on branch"
Window sizes for these windows are remembered the next time you open them, but adjusted heights of the splitter panes (comment, changes, diff) are not.
11 votes -
New preference: "Always undo unchanged on Refresh in Pending Changes"
When working in the Visual Studio plugin, changed files are always Checked-out when saved. If you re-save a file after restoring it to original contents (by Ctrl+Z or tweak-untweak a value etc), it's still Checked-out and will still appear in Pending Changes with a "Files are identical" Diff. The preference "Compare file contents instead of timestamps when determining Changed status" does not help here as the file is explicitly checked out.
There is an "Undo unchanged" command but it's dangerously close to the "Undo changes" button. It would be nice to have the option to always perform a silent "Undo…
41 votes -
Add "Update Cloaked" (and "Update Forced") to Items context menu.
If i have items or xlinks specified in cloaked.conf, the only way to force an update of these is to:
either removed them from cloaked.conf before "Update workspace"
or run "cm update --cloaked <path>" from the command line.
NOTE: Contrary to old documentation, running the "cm update --forced <path>" command will not update cloaked stuff.
I suggest adding a "Update Cloaked" command to the context menu in the Items view. Maybe also an "Update Forced" command, but this is probably less important.
14 votes -
Horizontal comparison panes in diff viewer
Would you consider adding optional horizontal comparison panes to the diff viewer, displayed or hidden with a button or a key combination?
It becomes useful when there are changes in long lines. Thanks to them you don't usually have to scroll the window in order to see all changed areas. This idea comes from WinMerge, which has both vertical and horizontal comparison panes.
3 votes -
Show changeset numbers in branch explorer
I'd like to see the changeset numbers in branch explorer in the same way they are shown in 2D version tree.
60 votes -
Deep integration with VersionOne
http://community.versionone.com/Help-Center/Administration/CommitStream
VersionOne introduces the new CommitStream feature which deeply integrated with GitHub/GitHub Enterprise. And it doesn't support Plastic yet.
https://ideaspace.versionone.com/default/Idea/Detail/2248
And I found others asked VersionOne to support Plastic as well.0 votesHi Seto,
First of all, we’d like to thank you for your interest in improving Plastic SCM!
We’ve studied your proposal and we’ve found this new VersionOne functionality really interesting. However, it seems that they’ve selected only few version control systems to be natively supported, all of them web-based and build around Git.
Since the new CommitStream appears to be deeply git-oriented at the moment, we believe that it should be the VersionOne team who takes the initiative to decide whether they would consider to support other version control systems. We would be really happy to work with them and connect our systems, but we’re afraid that this request is beyond our reach :-(
We’ll wait for a while to see if there are some movement on their side and we’ll let you know if we hear something.
Again, thank you for your suggestion!
Regards,
Miguel -
use the .gitignore file if it is present
Have plastic simply use the .gitignore file if it is present. Now that we support the online git repos like github bitbucket and VSO.
If you have .gitignore use that methodology and if you have .ignore use that methodology.
And maybe give user option to generate a .ignore file from a .gitignore.
21 votes -
Allow the pending changes view to ignore EOLs
(see http://www.plasticscm.net/index.php?/topic/2883-pending-changes-does-not-ignore-eols/)
I would like an option to allow the Pending Changes view to ignore EOLs.
Ideally this would happen automatically, so that if the option were enabled differences which are simply down to EOLs are not treated as pending changes.
Another idea
4 votes -
Ignore Case in Diff View
Some languages, like Visual Basic 6, are case insensitive. An option to ignore case sensitivity would remove some of the false positives the Diff Viewer reports because of case differences.
7 votes -
Code review per Branch compared with another Branch
Currently Plastic allows Code Review Per Branch. Problem is it shows differences between the original node from which the feature branch was created (in dev) and the head node of the feature branch.
However, this is a problem: when you update your feature branch merging updates other devs have merged in dev branch.
Why? Because all their changes also appear in the code review. So at this point is not possible to do a reasonable code review of the code in the feature branch.
The solution: Take the same approach that BitBucket takes. The code review should show only differences…36 votes -
automatically update workspaces overview upon new workspace from repo
Client shows all repositories.
User selects one and executes "Create workspace for this repository"
A new workspace will be created.
User switches to workspace overview.
The new workspace isn't shown until user hits F5. The workspace overview should automatically being updated.1 vote -
"Create submodule" to repo context menu
I'd like to add submodules to repositories by right clicking on the repo. I would then type the name of the submodule (i.e. <submodule>), only, instead of typing <reponame>/<submodule>. This avoids possible typos when typing <reponame>.
4 votes -
Repository description
Add a description property to a repository and add it as a column to the repository browser to allow for a long description to give detailed information about the contents of the repo. Repo names tend to be short and don't always explain what the repo contains, especially when there are 100's of repo's for different projects.
15 votes -
Support symlinks on Windows
Please add support for Symlinks (directory junctions, reparse points, ...) on Windows.
114 votes
- Don't see your idea?