设计与开发的协作_协作开发人员日记1：探索新设计

设计与开发的协作

We are thrilled to welcome Codice Software, the company behind Plastic SCM, to the Unity family! We built Collaborate to give users the ability to share projects amongst small teams who want an easy way to sync their projects without navigating the complexity of version control. We brought Plastic SCM into the fold for larger teams looking for more advanced features like branching, locking, merging and a standalone GUI. This means that we will no longer be doing the plan referenced in this blog post. We will continue to support Collaborate with its current feature set.

我们很高兴欢迎 Plastic SCM背后的公司Codice Software加入Unity系列！ 我们构建了Collaborate，以使用户能够在小型团队之间共享项目，这些团队希望以简单的方式同步其项目而无需浏览版本控制的复杂性。 我们将Plastic SCM引入了大型团队，以寻找更高级的功能，例如分支，锁定，合并和独立的GUI。 这意味着我们将不再执行此博客文章中引用的计划。 我们将继续通过其当前功能集来支持Collaborate。

指导原则 (Guiding principles)

Collaborate was created because we believe that all creators should be able to enjoy the benefits of version control without having to understand its intricacies. Our first attempt at solving this was to create a simplified UI that abstracted away complex concepts. For example, the workflow of ‘add’, ‘commit’, and ‘push’ became just ‘publish’. From your feedback, we learned over the last year that having a simplified UI isn’t enough. Many of you wanted to personalise your experience by having the ability to choose the UI that best fit your comfort level with version control. 

之所以创建Collaborate，是因为我们相信所有创建者都应该能够享受版本控制的好处，而不必了解其复杂性。 解决这个问题的第一步是创建一个简化的UI，抽象出复杂的概念。 例如，“添加”，“提交”和“推送”的工作流程就变成了“发布”。 从您的反馈中，我们在过去的一年中了解到，拥有简化的用户界面还不够。 你们中的许多人想通过选择版本控制最适合您的舒适程度的UI来个性化您的体验。

To guide the redesign, we’ve established a set of guiding principles. They are:

为了指导重新设计，我们建立了一套指导原则。 他们是：

1. Performance and stability are top priority.

   性能和稳定性是重中之重。

2. The UI should provide a simplified view that enables creators inexperienced with VCS to get up and running quickly. 

   用户界面应提供简化的视图，使没有VCS经验的创建者可以快速启动并运行。

3. The UI should provide an advanced view that aligns with the workflow and terminology that experienced VCS users are familiar with.

   UI应提供一个高级视图，该视图应与经验丰富的VCS用户熟悉的工作流和术语保持一致。

4. Standard routine actions should be so simple that they require no documentation.

   标准的常规操作应如此简单，以至于不需要文档。

5. Advanced routine actions should require no documentation for experienced VCS creators and minimal documentation for inexperienced VCS creators. 

   高级例行操作不需要经验丰富的VCS创建者任何文档，而经验不足的VCS创建者则不需要文档。

6. Features that are “risky” to a project in “the wrong hands” should be gated to prevent accidental use.

   应该对“用不正确的人使用”项目的“风险大”的功能进行门控，以防止意外使用。

新设计 (The new design)

We wanted to share the latest iteration of the design, which has gone through some adjustments based on your feedback. This design will continue to evolve with the feedback you share with us.

我们想分享设计的最新迭代，该迭代已根据您的反馈进行了一些调整。 您与我们分享的反馈意见将使这种设计继续发展。

Simple UI view

简单的UI视图

The goal with this view is to simplify the publish workflow as much as possible. For those familiar with “old” Collaborate, you’ll recognize similarities to that UI with a few notable changes:

此视图的目标是尽可能简化发布工作流程。 对于那些熟悉“旧”协作的人，您将认识到与该UI的相似之处，但有一些显着的变化：

1. All modified files are listed.

   列出所有修改的文件。

2. You can easily find specific files via the search bar.

   您可以通过搜索栏轻松找到特定文件。

3. The “All” checkbox will let you quickly select/deselect the files.

   “全部”复选框可让您快速选择/取消选择文件。

Advanced UI view

进阶使用者介面检视

The goal with the advanced view is to offer a UX that more closely mirrors typical git workflows. This view has all the same features as the simple UI, with a few key differences: 

高级视图的目标是提供一个更紧密地反映典型git工作流程的UX。 该视图具有与简单UI相同的所有功能，但有一些主要区别：

1. The list of files is presented in a tree view, rather than a collapsed view.

   文件列表以树形视图而不是折叠视图显示。

2. Only files located within the “Include” section will be published (rather than having to check a box). “Including” a file is the equivalent of executing the ‘git add’ command on it.

   仅位于“包含”部分中的文件将被发布(而不需要选中一个框)。 “包含”文件等效于对其执行“ git add”命令。

3. You can easily find specific files that live in either the include or exclude section via the search bar.

   您可以通过搜索栏轻松地找到包含或排除部分中的特定文件。

Branching

分枝

Branching may be the most requested feature that we’ve gotten from you. For those of you not familiar, it is a way to work on your project in isolation from the rest of the changes that are being made by other members of your team. This is very useful if you are prototyping, making a risky change, or if you want to separate out your project by release. Branching features will be supported both within the editor and on the Services Dashboard.

分支可能是我们从您那里获得的最需要的功能。 对于不熟悉的人来说，这是一种将项目与团队其他成员所做的其余更改隔离开来的一种方法。 如果您要进行原型设计，进行有风险的更改，或者要按发行版划分项目，这将非常有用。 编辑器和服务仪表板均支持分支功能。

Within the editor, you can create a new branch or switch to an existing one at the top of the window:

在编辑器中，您可以在窗口顶部创建一个新分支或切换到现有分支：

Switching to a new branch will automatically filter down your history view to show only changes made to files within that branch. We’ll share the mockups for merging branches later.

切换到新分支将自动过滤历史记录视图，以仅显示对该分支内文件的更改。 稍后我们将共享合并分支的模型。

Viewing the History – Searching & Restoring 

查看历史记录–搜索和还原

Being able to explore past changes is a key benefit to using version control. To aid in this, the history window will have more robust search capabilities such as by keyword (file name, commit ID, publish message, etc.) and/or date range. The filter will show all of the past commits that meet your criteria.

能够探索过去的更改是使用版本控制的主要好处。 为此，历史记录窗口将具有更强大的搜索功能，例如按关键字(文件名，提交ID，发布消息等)和/或日期范围。 过滤器将显示符合您条件的所有过去提交。

Once you’ve located the file(s) that you are interested in, you can access them via two methods:

找到您感兴趣的文件后，可以通过两种方法访问它们：

1. Rollback: This will replace your existing file(s) with the version that was published. You can do this to all the files in the commit or just a single one. It is very useful if your current version is no longer correct and you do not wish to preserve it. 

   回滚 ：这将用发布的版本替换您现有的文件。 您可以对提交中的所有文件执行此操作，也可以对单个文件执行此操作。 如果您当前的版本不再正确并且您不想保留它，这将非常有用。

2. Restore: This will create a copy of the file rather than replacing your existing file. It is very useful if you want to explore how you did something in the past without losing unpublished changes.

   恢复 ：这将创建文件的副本，而不是替换现有文件。 如果您想探索过去的工作方式而不丢失未发布的更改，这将非常有用。

Git命令行支持 (Git command-line support)

Collaborate working with git command-line is another one of our more highly requested features, and we’re happy to confirm that it will be supported! Like with most things, with greater flexibility comes greater challenges. To support it properly, we want to make sure that any changes made from the command-line or other git tools are expressed clearly in the UI. This can be challenging because Collaborate simplifies a lot of the git actions. 

与git命令行进行协作是我们要求更高的功能之一，我们很高兴确认将支持该功能！ 与大多数事情一样，更大的灵活性也带来了更大的挑战。 为了正确地支持它，我们希望确保从命令行或其他git工具进行的任何更改都在用户界面中清楚地表达。 这可能具有挑战性，因为Collaborate简化了许多git操作。

Imagine, for example, that you have modified five files and now they’re ready to go to the server. Using the command-line, you locally commit two of the files. Then you switch to the Unity Editor to continue working, and publish the rest of the changes to the server through Collaborate’s simple UI.

例如，想象一下，您已经修改了五个文件，现在它们已准备好进入服务器。 使用命令行在本地提交两个文件。 然后，您切换到Unity编辑器以继续工作，并通过Collaborate的简单UI将其余更改发布到服务器。

The problem with this scenario is that the simple UI wouldn’t normally have a way to show local commits that have occurred. However, now the UI will display a message reminding you of the local changes and guide you towards the advanced view which more closely represents what was done via other tools:

这种情况的问题在于，简单的UI通常无法显示已发生的本地提交。 但是，现在，UI将显示一条消息，提醒您本地更改，并引导您进入高级视图，该视图更紧密地表示通过其他工具完成的操作：

我们在哪里发展 (Where we are with development)

Over the last month, we’ve been focused on adding the base code to perform git operations between the Unity editor and the Collaborate service. This means that we can now execute git commands needed to power the simple UI, advanced UI and some history functionality via the Unity editor. It also sets us up for our current bucket of work – making the UI pretty. More specifically, over the next month we’ll be working on the following:

在过去的一个月中，我们专注于添加基本代码以在Unity编辑器和Collaborate服务之间执行git操作。 这意味着我们现在可以通过Unity编辑器执行为简单UI，高级UI和某些历史功能提供动力所需的git命令。 它还使我们为当前的工作做好了准备–使UI变得漂亮。 更具体地说，在下个月，我们将进行以下工作：

1. Creating reusable building blocks for many of the UI components, such as common buttons, search functionality, file lists, etc. 

   为许多UI组件创建可重用的构建块，例如常用按钮，搜索功能，文件列表等。

2. Making server changes to support both new and old projects on the Services Dashboard. 

   进行服务器更改以支持“服务”仪表板上的新项目和旧项目。

Since most of our work has been focused on the architecture and backend, we don’t have much UI to show yet. However, here’s a small preview of our work so far:

由于我们的大部分工作都集中在体系结构和后端上，因此我们没有太多的UI可显示。 但是，以下是到目前为止我们的工作的一小部分预览：

We will share our progress with you and talk more about new features, such as workflows to better support large projects. So please join us on the Collaborate forum and stay tuned to this blog!

宽 E将与您分享我们的进展，更多地谈论新的功能，如工作流，以更好地支持大型项目。 因此，请加入我们的协作论坛，并继续关注此博客！

如何参与 (How you can get involved)

We want to thank everyone who has signed up for the Collaborate UI study and who have provided us with feedback on the forums. Your feedback has been instrumental in helping us shape Collaborate, and we would love more of it! For those of you interested in participating, you have a couple of options:

我们要感谢所有注册了Collaborate UI研究并向我们提供了有关论坛反馈的人。 您的反馈对帮助我们塑造协作起到了重要作用，我们将不胜感激！ 对于那些有兴趣参加的人，您有两种选择：

1. If you want to discuss the designs mentioned here, head over to this forum post.

   如果您想讨论此处提到的设计，请转至本论坛帖子 。

2. Sign up for the Collaborate UI study and provide critical feedback on the designs.

   注册进行 Collaborate UI研究 并提供有关设计的重要反馈。

3. If you just want to provide general feedback on features that you’re interested in, you can post them on the forum. We are always monitoring and may reach out to you to set up a call to discuss your requests in more detail.

   如果您只是想对自己感兴趣的功能提供一般性反馈，可以将其发布在 论坛上 。 我们一直在监视，并可能与您联系以建立电话以更详细地讨论您的请求。

翻译自: https://blogs.unity3d.com/2019/07/01/collaborate-developer-diary-1-exploring-the-new-design/

设计与开发的协作