Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Announcing WebUI V2

Tuesday, July 13, 2021 Neha Khalwadekar , 0 Comments

collaborate seamlessly any time, anywhere, and on any device.

Introduction

We've been working on an improved version of WebUI for our Enterprise and Cloud Edition users and are excited to announce its release to the public. Our goal for WebUI is to connect teams and help increase productivity for real-time content creators by providing deeply integrated role-based workflows so that all Plastic users can easily get their work done.

With this version, we explored some of the problems creators were encountering and asked how we might be able to address them. For example, if a technical artist needs to review their team's code but does not have a local setup, they can easily go to https://www.plasticscm.com/orgs/<your-org-name> to collaborate seamlessly any time anywhere and on any device.

Improved WebUI

Quick Tour of WebUI

How to access

  • In order to access the WebUI beta, you will need to navigate to https://www.plasticscm.com/orgs/<your-org-name> in your browser.
  • You can log in with your LDAP/UP or Active Directory email and password.
  • Once you log in successfully, you can view a list of repositories on your server.
Note: Encrypted organizations are currently not supported. If you have an encrypted organisation, you will not be able to access WebUI as the team is actively working on a solution. This will be available in the next milestone release.

Features

Repo list

  • You now have the ability to view the repositories and interact with VCS through WebUI.
  • You can perform a search on the repo list including quick actions like sorting by Date/User.
  • There are breadcrumbs everywhere on the site to help you easily navigate.

File Explorer

Next, comes the File Explorer, a repository browser to explore the contents of a branch. With this view you will be able to do much more than just navigate your repo structure and find a given file.

  • You can switch between your branches by clicking on the current branch name.
  • You can also switch to Labels view by clicking on main and selecting labels (Labels are similar to Tags in Github).
  • You will be able to use the search field for files. History will take you to the changeset view.
  • You can download a zip file of the repository by clicking on the Download button .
Improved File explorer

Code Review

One of the main reasons to have a web interface for a repository is to let users perform code reviews consistently irrespective of their OS or hardware.

  • You can open one of the reviews and see file diffs for each branch, comment on them, request for a change, or ask questions.
  • The overlay icons on the users help identify the status of the review (Rework required, Under review, Reviewed)
  • Collaboration has been significantly improved on our team as we now have multiple reviewers available for your code review.
Improved Code review
Improved Code review

Changeset

  • Just like in the regular desktop GUI, it is also possible to list the recent changesets.
  • You can also easily create a code review from here, show diffs, or browse repositories.
Changeset

Annotate/Blame

The Blame helps you determine who made changes to a file. You can easily navigate between the two views.

Blame View:

  • Clicking on an annotation button will open the panel at the bottom and focus on it.
  • Hovering left to a line number will show the go to the previous revision button.
  • Click on the line numbers will also display the changeset description at the bottom of the page.

Normal view:

  • Compared to what we have now there's collapsible information about the current changeset at the top of the file.
Annotate/Blame

Areas of Improvements

  • If you have an encrypted organisation, you will not be able to access WebUI as the team is actively working on a solution. This will be available in the next milestone release.
  • We have a few open bugs that we are currently looking into:
    • The info button on the Changeset view is currently not working.
    • The edit title on Code review is being reviewed.

Major Milestones

  • We are excited to be working on amazing features such as Diff window - semantic split to be released in the near future. This will allow you to show diffs in a super clear way which is one of Plastic's top differentiators.
  • We also have other interesting feature the team will be looking into like:
    • Merge Categories
    • Display images on code review
    • Conversation area

Wrap-up

We are in the early stages of alpha development of our webUI and we are actively seeking your feedback to create a great web experience for our users and a unique experience for RT3D content creators.

Please take this quick survey to share your feedback with us so we can build a better product for you and your teams.

Neha Khalwadekar
I am working out of Toronto. I started out as a Software Engineer and dabbled in some DevOps before getting into Product Management. I'm coming from LoyaltyOne - Airmiles, and TD and am excited to be joining Unity and build some wonderful products!
I enjoy volunteering, cooking, gaming, watching basketball. I've been able to survive the pandemic by spending time with my pup, Whiskey.
You can reach me at @bytes_and_bites.

0 comentarios: