General

General

Categories

JUMP TO ANOTHER FORUM

  1. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. I would like to see Plastic SCM have support for TestTrack Pro issue management system. See the following link to add support using TestTrack's SDK for C#: http://labs.seapine.com/wiki/index.php/TestTrackSOAPSDKTutorial-CSharp

    For more information on TestTrack, go here: http://www.seapine.com/ttpro.html

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. I wanted to be able to quickly see (within the branch explorer) branches that have changesets after the last merge in the branch.
    An enhancement could be to do this only for child branches of a specific branch.

    As I described here:
    http://www.plasticscm.net/index.php?/topic/876-highlighting-un-merged-branches/pagefromsearch1

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. As far as I can see, the GUI is missing the useful --ignore options from the command line.

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. For the PSCM GUI, check-in's seem to take a long time meanwhile locking the main ui thread. Executing the check-in command in a seperate thread would be really nice and a progress bar to show at the status bar would be even better.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. When selecting a changeset, I'd like to have a preview area where the changeset's details are shown (at least which files have been changed). Currently, I have to double click a specific changeset in order to see the details.
    Think of an email client like Outlook, where you can read the mail by selecting it in your list of mails without opening the mail in an extra window.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. During a lengthy operation (Update/Switch), I would like to be able to continue working on another of my workspace tabs. As it is, the Update/Switch dialog is modal and I have to wait for the operation to finish before I can switch tabs.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to apply color to branches (simple but usefull tool). All of us works on separate branches and we have as well our "under dev" or task specific branches. We merge from and to only using our main branches. Colorcoding is very intuitive way to differentiate "development/beta" branches from final branches

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. When creating a code review with files that have been merged into the branch it (sometimes) properly categorizes them as CC "Changed in merge source and destination). However, the diff does not show which lines came from the source and which were change in the destination. It would be great to have those separated out for easier code review.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. The conditional format and changeset colours are currently per workspace. It would be nice if all my workspaces were consistent and I didn't need to configure them all manually.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Repo / workspace names will not fit in the workspace tabs if using long descriptive names.

    This becomes worse when using the feature of "sub-repositories". When having several subrepo workspaces we could end up with only the parent repo name visible in the workspace tab.

    I'm aware that I can rename workspaces, but it would be better if the tab widths were not so restrictive.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Currently I get told I can't delete a branch "because it has revisions". I appreciate the warning, but it should allow me to say "ok, delete the revisions too" rather than cancelling the delete. Deleting each changeset manually to allow the branch to be deleted is a pain.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We 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).

  17. Please port the v3 vss import wizard to v4.

    The route by vss2git failed big time probably on a binary in vss. The route by svn is also far from flawless (I could not even exportmy error free vss to svn).

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. For us, a common operation is that we have run compilation etc in a workspace and then want to wipe out all the generated output files to get a clean workspace again (similar to "make clean" in a Makefile).

    This is a feature I miss from TortoiseSVN, which has a context command "Clean up". What that command does is to bring up a small dialog with cleanup-options, where I can choose things like these (translated to Plastic nomenclature):


    • Refresh shell overlay icons


    • Delete private items


    • Delete ignored items

    • Undo all changes

    • Undo unchanged


    • Apply cleanup to xlinks as well


    Perhaps…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. It's very good that we have keyboard shortcuts Ctrl+N/M for prev/next Diff, but in the grander scope they are rendered sub-useful since these keys only work when one of the Diff panels has keyboard focus.

    For example, in the Pending Changes view I like to review all changes before Checkin. To do this, I select the first item in the list. I can then use keys Up/Dn to walk around between changed items and the inline Diff is updated accordingly.

    However, when there are many diffs in a file I want to review them all so I try the Ctrl+N/M…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. It doesn't seem possible to find the parent revision of an item on the command line. It would be useful if 'cm hst' listed the parent revision of each revision listed.

    It would also be useful for the GUI history table to have a similar column.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?