531 results found

1. Allow update-merge on "Update Workspace" and "Switch"

   Back in old Subversion, the scenario of "Updating to a newer changeset (on the current branch) while there are Pending Changes in the workspace" was handled very smoothly and seldom caused any problems. (Sure, conflicts can arise but they are usually minor since we are on the same branch.)

   I'm aware that it's recommended that each developer works on their own child branch. Nevertheless, this situation comes up, for example when two child branches are being concurrently merged back to the parent. Also, the Plastic team has already put some work into supporting this scenario:
   http://codicesoftware.blogspot.com/2012/02/working-on-single-branch-update-merge.html
   "While our recommended pattern is definitely branch-per-task, sometimes you’ll find yourself sharing a branch with another developer or even the whole team."

   Unfortunately, the current handling of this scenario is not optimal. There are (at least) 3 methods for updating the workspace to the latest contents on the current branch, and the third method differs from the first two in ways that are hard to predict:

   (1) Pressing "Update workspace" button on the Items view.
   (2) Switching to the same branch.
   (3) Pressing the "View new changes" button that appears in the Pending changes view when there are newer changesets.

   The setting "Other Options - Behavior when trying to switch / update with changed items" / PendingChangesOnSwitchAction controls some aspects regarding the behavior of method (1) and (2). When using the "No-Checkout" workflow, it has been recommended to choose the option "Allow" or "Allow, showing a warning" for this setting. However, in my experience this does not work well at all. This setting only affects Changed files and it causes several problems, even potentially blocking a subsequent Checkin! On the other hand, the default option "Do not allow, show an error" will prevent any attempt to use method (1) and (2) when there are local changes. Also, if there is any checked-out items, method (1) and (2) will be disallowed regardless of settings.

   (Details: If I switch/update with locally Changed files with the above option "Allow, showing a warning", I get the Confirm Update dialog. If I then choose to continue with the Update, I get the Update Results dialog. Here, my Changed files are listed as "not up-to-date" even if the new changesets on my branch contained only changes unrelated to these files! And if the new changesets on my branch did contain changes related to my changed files, I may even become unable to Checkin because of an error "parent revision is inconsistent with the loaded one"! Also, if I use "Update forced" I would lose my local changes.)

   Method (3) is only available if we have activated "Look for newer changes in the repository" under Options in the Pending Changes view. This method is working much better, since incoming changes are handled by a sub-branch-merge.

   (NOTE: When cloaking is active, the method (3) will always cause a Merge instead of an Update if there are newer changesets, potentially leading to unnecessary "sub-branching" even when there are no changes in the workspace!)

   My suggestion is to:

   • Completely remove the setting "Behavior when trying to switch / update with changed items"
   • Handle "Switch" and "Update Workspace" (method 1 and 2) very similar to "View new changes" (method 3).

   This would make the handling much more consistent. Both Changed and Checked-out items can then be merged, and a trivial switch/update can be performed if there are no conflicting files.

   Back in old Subversion, the scenario of "Updating to a newer changeset (on the current branch) while there are Pending Changes in the workspace" was handled very smoothly and seldom caused any problems. (Sure, conflicts can arise but they are usually minor since we are on the same branch.)

   I'm aware that it's recommended that each developer works on their own child branch. Nevertheless, this situation comes up, for example when two child branches are being concurrently merged back to the parent. Also, the Plastic team has already put some work into supporting this scenario:
   http://codicesoftware.blogspot.com/2012/02/working-on-single-branch-update-merge.html
   "While our recommended pattern… more

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Add an option to prevent changing branches when you have added (private) files which are marked as pending adds.

   This would prevent you from adding a file and forgetting to add it to source control before changing branch. This idea here is that you would set Plastic up to discover private files so you can see which files need adding. Any solution files or built data you would put in separate folders which aren't under source control and thus aren't detected by Plastic. This approach prevents you from forgetting to add files, i.e it'll build for you locally but not for others.

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Add a branch weight for layouting in branch explorer

   I like to have my branches ordered bottom-up as they are closest to release. So my issue branches are below the trunk which is below release candidates and hotfix branches.

   I do this manually right now. So I have two lines für release/hotfix branches then the trunk and then everything else.
   This is fine as long as there are only 2 branches in the upper two lines. But sometimes there are more (especially when 'older' branches are updated with new data. Then they overlap.

   My suggestion:
   Add a weight property to branches (maybe via conditional rules) and order the branches by their weight in the branch explorer. Heavy branches go down and light branches stay up. This would allow me to use the auto-layout and enjoy the right ordering.

   I like to have my branches ordered bottom-up as they are closest to release. So my issue branches are below the trunk which is below release candidates and hotfix branches.

   I do this manually right now. So I have two lines für release/hotfix branches then the trunk and then everything else.
   This is fine as long as there are only 2 branches in the upper two lines. But sometimes there are more (especially when 'older' branches are updated with new data. Then they overlap.

   My suggestion:
   Add a weight property to branches (maybe via conditional rules) and order the branches… more

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Add ways to disable Diff auto-updating on changeset

   The new "multi-screen diff" in Plastic 6.0 is excellent. It was introduced in 6.0.16.884; if you have the Plastic SCM main window open on part of your screen, and open one diff window on another part of your screen, then the diff window's contents will change when you move around in the Branch Explorer.

   (Slightly related uservoice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/15615156-show-diffs-in-branch-explorer-and-changesets-views )

   However, this has a few flaws related to cases where you don't want the "Diff changeset" window to change. To stop the Diff from updating when you click a changeset, you need more than one Diff window open. This is OK in theory, but in practice it works like this:

   • If you double-click a changeset to open the 2nd Diff window, the double-click is ALSO interpreted as a single-click which updates the contents of the 1st Diff window.

   • If you right-click a changeset to choose something in the context menu, this is ALSO interpreted as a single-click which updates the contents of the 1st Diff window.

   • One of my coworkers is going nuts over this and would like an option to completely disable the auto-updating of Diff window content.

   The new "multi-screen diff" in Plastic 6.0 is excellent. It was introduced in 6.0.16.884; if you have the Plastic SCM main window open on part of your screen, and open one diff window on another part of your screen, then the diff window's contents will change when you move around in the Branch Explorer.

   (Slightly related uservoice: https://plasticscm.uservoice.com/forums/15467-general/suggestions/15615156-show-diffs-in-branch-explorer-and-changesets-views )

   However, this has a few flaws related to cases where you don't want the "Diff changeset" window to change. To stop the Diff from updating when you click a changeset, you need more than one Diff window open. This is OK… more

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Allow comments for added files in Code Review

   It would be nice to set comments in added files.

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Better handling of dark theme in Linux

   Using a dark theme with the linux build ends up with some pretty glaring white backdrops to things and lots of unreadable text.

   It seems Plastic isn't using the supplied gtk theme colours, but instead has hardcoded colours for certain things.

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. In Changesets view, also show files in change set

   In the Changesets view, have a split view, that shows the filenames of the files in that change set.

   The view could be just like you use in the Pending Changes view, where the split is resizable, with the top half showing change sets, and the bottom showing the files in the changeset currently selected. That way you can quickly arrow up/down through the change sets and see the files instantly in that set.

   If you want to get to the diffing tool, you still need to double click the changeset. This is only about showing the files in the changeset.

   In the Changesets view, have a split view, that shows the filenames of the files in that change set.

   The view could be just like you use in the Pending Changes view, where the split is resizable, with the top half showing change sets, and the bottom showing the files in the changeset currently selected. That way you can quickly arrow up/down through the change sets and see the files instantly in that set.

   If you want to get to the diffing tool, you still need to double click the changeset. This is only about showing the files in the… more

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Use "tab mechanism" from Branch Explorer sidebar in all other sidebars

   The Branch Explorer "Options" sidebar has its "tabs" in a vertical layout, which works better when there are several tabs. Other sidebars (in the Branches and Changesets views) use horizontal tabs instead. It would make sense to unify these so the same type of sidebar component is used in all these places.

   Additionally, I think the "View History" view should have a sidebar as well...

   12 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   planned  ·  AdminCodice Software (CEO / Founder, plasticscm) responded

   Our plan is to redo the windows GUI and implement what we already have on Mac and Linux… which is exactly what you’re asking for :-)

9. Shell extension - mark parent dir modified. (a la tortoise git\svn)

   When modify one item, mark parent directory modified.

   11 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. merge the three logins I have for your sites.

    I currently have a login for downloading Plastic SCM. I have another login for the community forum, and I have a third login for this site.

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. 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

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Support for CodeLens Change and History

    I'm actually not too sure how this works but it seems like there's an opportunity to provide in-context change history info via CodeLens. I see it with Git changes and it works pretty cool - see attached screenshots.

    ref: http://go.microsoft.com/fwlink/?LinkId=320331

    •  

    •  

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. 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:

    http://www.plasticscm.net/index.php?/topic/2003-add-an-attribute-to-a-newly-created-branch-changeset/

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Make all Branch Explorer colors customizable

    In Branch Explorer, the alternating date-background color can be changed via a variable in a .conf file, but none of the other color schemes.

    There is also the Themes feature in Preferences, but those seem to leave the Branch Explorer unaltered (even leaving it light for the dark themes)!

    What we do have is the ability to color branches by attribute (conditional format) and to color changesets by user/replication-source. (But sadly, the color by replication source feature is currently broken.)

    My request is to expose all the border, fill, background, selection and font colors to the user, either via .conf variables or via Themes customization.

    These color settings would of course still be overridden by conditional format and changeset colors. Being able to change the default colors for borders, selection etc is important for readability. Also, for a consistent Theme look, we also need to be able to customize background colors etc.

    Another (minor) issue is the darker border-color around the latest changeset on each branch, which I find to be only distracting (since the selected changeset is also using a dark border). So I would like to be able to choose the same border-color here as for other changeset borders.

    Mostly, I'm interested in just making everything tweaked for visibility, so that it's easy to locate things. Too many different colors make it more difficult to get an overview. Every color should carry information. I like things like "color by user" but sometimes it gets in the way, if it makes it harder to locate the selected item for example...

    In Branch Explorer, the alternating date-background color can be changed via a variable in a .conf file, but none of the other color schemes.

    There is also the Themes feature in Preferences, but those seem to leave the Branch Explorer unaltered (even leaving it light for the dark themes)!

    What we do have is the ability to color branches by attribute (conditional format) and to color changesets by user/replication-source. (But sadly, the color by replication source feature is currently broken.)

    My request is to expose all the border, fill, background, selection and font colors to the user, either via .conf… more

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. 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 Plastic rather than is Plastic - consider releasing the code for the plugin as an open source product, allowing the community to contribute to its updates, maintenance, and enhancements.

    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… more

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    AdminCodice Software (CEO / Founder, plasticscm) responded

    Wrongly closed. We have only closed the diff scripts.

16. Integrate the Repository configuration (plastic configuration wizard) with the Plastic UI.

    Currently, to use a different repository server, you have to run the configuration wizard multiple times.

    It would be much more convenient to be able to open the Plastic SCM tool and click "add new server..." or "select repositories from server..." so that the user can choose where to get a list of repositories (projects) to work with - and start creating workspaces to pull the project down to.

    The following is a scenario I ran into:
    1) I created a local plastic server to replace my personal CVS server for projects that I work on at home. Using the configuration wizard works fine for that - assuming I will only have a SINGLE plastic server.
    2) I decided that I wanted to ditch CVS/TFS at work and replace it with plastic - however, I also often work from home - now I have to configure my WORK server through the plastic configuration wizard. Which DROPS my original configuration. I can create workspaces from the NEW server, but have no ability to create workspaces on the "old" (meaning, personal/home) one until I switch the active server - by re-configuring it through the configuration wizard - thus dropping my Work server configuration.

    Currently, to use a different repository server, you have to run the configuration wizard multiple times.

    It would be much more convenient to be able to open the Plastic SCM tool and click "add new server..." or "select repositories from server..." so that the user can choose where to get a list of repositories (projects) to work with - and start creating workspaces to pull the project down to.

    The following is a scenario I ran into:
    1) I created a local plastic server to replace my personal CVS server for projects that I work on at home. Using the… more

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Keep typed comment when closing checkin dialog without commit.

    Sometimes i type comment for a checkin but then discover some issues in the list of files that force me to close the dialog (loosing the already typed comments).

    The current woraround is to open notepad and copy the comment into it for later use. But that is rather clumsy.

    So request is that when you close the commit dialog without commit the typed comment is added to the dropdown list of previous comments (or is just restored when the dialog is re-opened for the same workspace).

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Show progress indication for Undo of many/large files

    When undoing pending changes on a very large (binary) file or a large number of files, the operation can take a considerable amount of time, especially if connecting directly to the repo server over Internet.

    It seems the original file contents are re-downloaded, but that is not directly obvious so a progress indicator (just as for update/switch) would be helpful here. Otherwise one may think that the process has stopped working...

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. 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

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Add the ability to tag repositories

    Similar to the request to group workspaces and repositories (https://plasticscm.uservoice.com/forums/15467-general/suggestions/2772036-group-workspaces-and-repositories) but not quite the same.
    
    Using submodules to group repos limits you to a single classification of a repository. Ideally you are able to tag a repository with several keywords like you do on a forum or an article. This would allow us to tag a repository with 'real-time control' or 'imaging algorithm' but also tag it with a product name that uses it or the programming language that it is written in.
    This would necessitate a new repository view in the client where instead of a list of repos you get a tree view list of tags which expand to show the repos that have that tag.
    To set the tag, a right click menu 'Add Tag' would need to be added to the normal repo view.
    Having this feature would allow easy navigation of many small repos and further encourage use of the Xlink feature.

    Similar to the request to group workspaces and repositories (https://plasticscm.uservoice.com/forums/15467-general/suggestions/2772036-group-workspaces-and-repositories) but not quite the same.
    
    Using submodules to group repos limits you to a single classification of a repository. Ideally you are able to tag a repository with several keywords like you do on a forum or an article. This would allow us to tag a repository with 'real-time control' or 'imaging algorithm' but also tag it with a product name that uses it or the programming language that it is written in.
    This would necessitate a new repository view in the client where instead of a list… more

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close