mdel

In order to understand which changeset is responsible for the file modification, the changeset number is not convenient enough. having the "changeset comment" would make it easier to recognize the changeset. (PS: This column already exist in the Changeset tab) (PS2: This is a common feature for Perforce or Git GUI)

Hello, Here is my first feedback after playing around with PlasticX Good: GUI feels very reactive. Opening tab, clicking button, ... I cannot explain why but reactivity feels way better than the other GUI Seeing the username on top-right is very appreciable improvement for me because I as administrator of our Plastic SCM server I am often switching user between my personal account, administrator root account, and some other user account to check their issue and permissions Having the left menu and tab merge as a unique menu on the left is simpler Having custom view opening (i.e "browser repository in this changset", and "browse changeset of this branch") opening on the right view is less confusing than having a lot of multiple tab at the same time. Bug: It is not possible to close custom view once they are open Dislike: Font rendering looks weird. I have posted more details in this specific thread. "Workspace selection" window does not open a new window. When working with several workspace at the same time, you I often need several workspace window open at the same time. It will be convenient to be able to do it from the "worskpace selection" window, at least as an option GUI Non Sense to me: "Switch Workspace" Button location: The "Switch Workspace" button is on the button where all the workspace information are on the top bar. It took me time to find this button and I think it will feel more natural to have it with the rest of infos "Update" and "View" button confusion: There still are two button to update a workspace with different behavior and located at different places: "Update Workspace" and "View (incoming change)" It is not clear that the "View" button can be used to update the workspace. Every new user when they start with Plastic will at some point complain to me they cannot update their workspace (because "Update workspace" button fail when merge are required. And I have to tell them actually they should use the "View" button I think a unique button should be good enough (it can suggest a merge if necessary) Even if two buttons need to remain, they should be located at the same place The server global permission button is still a button you access from the context menu of a specific repository. I think it should be in a more "global" location. The fact it is called "repository server" is confusing because it could mean it is repository specific, that's what I thought the first time. (especially it is under a repository specific context menu). The User Permission window is very inconvenient when you have a lot of group and user. It is not possible to compare the permission between groups and users because they are displayed on separated view. If you want several user to apply the same policy to several users (i.e same permission set) you need to go back and forth between the view to check they are the same. The window is not large enough to display all the permission so not only going back and forth but you also need to scroll at the right position. It is not possible to check several permission quickly because every time you check a permission the description of that permission open and it move the position of all the checkbox below. Impossible for you to target the checkbox The window is too small to display all the checkbox, so you need to scroll. Try to check 1 out of 2 checkbox, and notice how painful it is A simple 2D Tab UI with line being permission and column being user (or vice-versa) will already improve a lot the situation

Hello, I had the same experience than @Mikael Kalms as soon as I launch PlasticX GUI the font rendering gave me a very bad impression. It looks poor compared to user GUI I am using on Windows, and it look poor compared to the regular Plastic GUI. It feels very blurry. @Daniel Peñalba I do not think it is related to Skia renderering because Chrome does have better font rendering than PlasticX on Windows too.

I would like to connect code review trigger to notification mechanism. I already have an e-mail plug and slack plug configured and being able to handle notification for my merge bot. I wish to re-use it instead of implementing another notification system for triggers. Is there a way to connect a trigger to a plug? For instance would it be possible to a custom merge-bot to intercept triggers? thank you

Hello, I do understand in the scenario of locking file, checking out is the way to lock the file. But it is also possible to checkout a file without locking feature enable, but I do not understand why this would be interesting?

Understood, thank you.

I would like my some of my workspace tree folder to point to the same subtree on Windows. Common method is to create a symlink to point to the folder owning the desired substree. Example: mklink /D myfolder myfolder_destination Is it possible for PlasticSCM to store such information and to replicate when updating the workspace?

Understood, thank you.

Hi @calbzam Thank you for your answer. I know it is possible so set which user and group are allowed to edit comments, but with this mechanism only I do not find a way to implement the following: "nobody is allowed to edit changeset comments except the changeset author". Regards,

Hello, I would like to prevent users from being able to modify changeset comments, except in the case the user is the owner of the changeset. Is there a way to do that? Thanks,

Hello, I would like to enforce branch to follow a particular convention when a user create a branch. For instance enforcing a predefined list of prefix: e.g bug-<name>, feature-<name>, user-<name>. I did not find in the documentation any "branch rule" mechanism. Thanks,

Hi Rafael, What I wanted to know was if it was possible to return to the same "branch explorer" visualization. I think your answer is telling that it is not possible: I can go back to the same state of the main branch, but I cannot remove the child branch. I think the philosophy in Plastic SCM is not to be obsessed about the changeset history. As opposed to git, since plastic can handle much heavier repository, it does not matter if your repository has its history a bit messy. Thank you, I think you answered my questions.

Thank you Rafael. By merging the moved changesets back to the main branch, it's kind of a "copy" instead of being a move. Because of the merge link it is not possible to delete bad changesets. Is it possible to delete those bad changesets? Maybe there is a way to merge without keeping the merge link? Or removing the merge link afterward? Regards, mdel

Hello, In the situation where my main branch is A<-B<-C<-D, by running Move changeset to a different branch to the changeset C it will move C and D in another branch. In the case it was a mistake operation, I did not find anyway to revert this operation (and having C and D back to the main branch). In other word, it is always possible to split a branch in several branch (using Move changeset to a different branch and branch rename) but I did not find a way to merge 2 branches back to one. Thanks