535 results found
-
Add option "Ignore blank lines" (like "Ignore EOLs") as comparison method
I often have more or less blank lines after debugging. When I do not like them to checked in I have to go through all changed files and add / remove blank lines. It would also be great if the menu items have a checkbox, one per option (Ignore EOLs, Ignore whitespace, Ignore blank lines).
4 votes -
layout branches in branch explorer by attribute
I use the manual relayout mode to layout my branches in a way, that release branches are on top, the trunk is in the middle and all issue branches are below.
This way I have a fast overview of the changes that are released.
[They also have different colors ;)]All these branches have an attribute called "role" with different values:
"Release" for releases
"Trunk" for the trunk
"Patch" for issuesNow, it would be VERY nice if I could teach the branch explorer, that branches should be layed out in an order (top to bottom) based on the attribute…
6 votes -
Gluon, compare contents of text files instead of time stamps
Gluon, compare contents of text files instead of time stamps.
Text files that are exactly the same are being seen as changed in Gluon.
1 vote -
Indicate whether or not a changeset / branch has been synced from the Branch Explorer
Do something (change color, icon, etc) to show that changesets/branches have not been synced.
6 votes -
Add option to always show active branch
When using inclusion/exclusion filter-rules in Branch Explorer, the active branch may become hidden. I want some way to force the active branch to be always visible.
There is a special coloring-rule (currentselectorbranch) for the "Active branch in this workspace", but there is no way to do the same in an inclusion rule. (As I don't think it's possible to locate the active branch via a simple find-branch-query?)
I propose adding a way to (optionally) always show the active branch. This could implemented simply as a new "Display option" - "Always show active branch" or as a special inclusion…
3 votes -
Having the ability to set an Icon for each repository
If we could set individiual icons for each repository (like its possible in Jira) working with many repositories becomes more easy. Currently I have to ensure that I am looking at the correct one by looking at the name. Just quickly checking the icon would be a lot faster.
Additionally the names do not fit into the workspace tabs, having a small version of the icon displayed there would switching workspaces much quicker.3 votes -
Optionally affect xlinked repos when doing "Apply label to workspace contents"
When applying a new label, there is a checkbox "Label all XLinked repositories".
However, when moving a label ("Apply label to workspace contents") there is currently no way to automatically apply (or move if existing) a label by the same name in xlinked repositories.
It would be very nice to be able to do this (as an option).
3 votes -
Add prio order for inclusion and exclusion rules as well
In Branch Explorer, it's hard to combine inclusion and exclusion rules since there is no way to adjust priority order between them, and exclusion always seems to override inclusion.
I would suggest evaluating (for each branch) the inc/exc rules from top to bottom and stopping at the first (enabled) matching rule (just as for the custom coloring rules). Then you could re-use the "move up" button for adjusting these prios (only keeping the separation of color-rules from the inc/exc rules).
3 votes -
add branch alias
Would be cool to have aliases for branches.
The whole system builds up on branches names and you may refer to them from other programs, so you can't change the name.Example: Branch with name 'Task0815' is a new feature called 'Branch aliases' (see what I did there? ;])
In the Branch Explorer this branch could be displayed as:
Task0815 | Branch aliasesThis would enhance the overview inside the branch explorer, because having Task001 to Task999 isn't telling you much.
At the moment this would be inside an attribute or the branch description, but both aren't displayed until you…
3 votes -
Update Office Plugin
Currently, the Plastic SCM installer provides an option to include plugins for various IDEs as well as Office.
The Office Plugin support is provided for 2003, 2007, and 2010. Noting that the year is 2016, and that two releases of Office have occurred since then, the plugin should be updated to work with the latest versions.
Additionally, the Office Plugin doesn't have quite the same "polish" and "style" that the rest of Plastic has when running on Windows, so it could use some touching up.
Finally, if this isn't a priority - and since it really exists to integrate with…
10 votesWrongly closed. We have only closed the diff scripts.
-
25 votes
-
Add a view and a command for viewing all xlinks in a repo
I want to quickly list all the xlinks in a workspace, both in the GUI and on the command line.
The "cm xlink" command lists info about one specified xlink, but how do I list them recursively (without doing a "cm ls -R | grep xlink" or using "cm fileinfo" in every subfolder)?
I think there should be a command for this, perhaps "cm findxlinks", similar to "cm findprivate". A raw list of absolute paths to xlink-folders would do fine.
Also, I would like a GUI view listing all the xlinks in a repo (similar to the Branches view).
3 votes -
Add support for branch depth in find branch command
I propose adding a "depth" or "level" filter-option for the branch find-object, to filter on branch namespace-depth (just like "Display branch levels" in Branch Explorer Display Options).
Example:
find branch where level < 3
6 votes -
Add support for namespace in "find branch" command
Currently, finding a branch by namespace is not possible. Even worse, [find branch where name = 'main'] returns 1 branch, but [find branch where name = '/main'] returns none!
Please add full namespace support so we can find branches by complete name, such as [find branch where name = '/main/task001/subtask_1'].
This request originates from the following forum post:
11 votes -
Make better use of the icons in History and Changesets views
The "View history" and "Changesets" views would benefit from having different icons for each changeset line, depending on whether there's an incoming (or outgoing?) merge etc. As it is currently, the icons in these list views are not really used to their full potential since they are all the same...
4 votes -
User Translation Table in Sync View
I wanted to replicate a whole repository and need to map user names.
I managed to replicate single branches using the user translation table. However, in "Sync replication", there is no such option. That is, I have to replicate each branch one by one. I have to select the translation mode in the GUI each time I replicate a new branch.3 votes -
Add progress bars to Merging / Save revision as windows.
Save revision as freezes the entire Plastic SCM client while it downloads the file from the server and saves it on disk. This unacceptable, especially for big files.
Progress bars must be added to Merging / Save revision as windows so users can see, well, the progress of the operation, and not wonder did it get stuck or something. Especially for people with slow internet connections.
10 votes -
Improve XLink conflict resolving in merge
Imagine the following scenario:
A repo with a XLink with a main branch and a child branch. Both branches have the same XLink.
Now the following occurs:
1) XLink is changed in both main branch and child branch
2) You do a merge from main to child branchYou'll get a conflict (which is expected). However, the "Source" and "Destination" values aren't very human readable in the GUI. I'm assuming they're the GUID's of the changeset or something similar.
Could you make it more human readable? Displaying the associated changeset, branch etc?
38 votesHi supporters!
We would need an answer to the question we asked here to be able to move forward. Otherwise, without extra info, we would need to discard.
Thanks,
pablo
-
Add home button to 'Branches' tab
Add the home button like the one in the Branch Explorer to the Branches tab. This makes it much easier to jump to the current branch especially when being on a higher level branch.
6 votes -
In 2D History of a directory, show merge arrows that affect its subtree
I often bring up the 2D history tree for a directory to see what changes are done to items in its subtree. This works quite fine, but it does not show merge arrows for merges that involve items inside the relevant subtree. This makes it harder to follow what happened.
For example, I can see "C" changesets on a child branch and then later a "C" changeset on the main branch where the comment on the latter says it was merged back from the child branch, but there is no merge arrow displayed.
For a more informative view, I suggest…
3 votes
- Don't see your idea?