与 Sencha Architect 的预期协作工作流程是什么? [英] What is the expected collaboration workflow with Sencha Architect?

查看:19
本文介绍了与 Sencha Architect 的预期协作工作流程是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我开始试用 Sencha Architect,我使用它的次数越多,我想到的关于它在开发环境中的实际可行性的问题就越多,我遇到的一个更大的问题是

I started a trial of Sencha Architect, and the more I use it more questions come to my mind for its actual feasibility usage in a development environment, one of the bigger questions I have is

在无法在不同编辑器中编辑单个文件的环境中,例如,多人如何协作开发网站的不同部分

In an environment that you can't edit the individual files in different editors, how can multiple people collaborate in developing different parts of a site, for example

app/models|components|views/Model1.js  <- In charge of developer one
app/models|components|views/Model2.js  <- In charge of developer two.

例如,在常规环境中,您可以使用 git 来分发每个文件,但在 Architect 中,您不需要手动编辑文件(这很糟糕,因为诸如配置文件之类的功能未在 Architect 中公开).如果您手动编辑它们,则会导致问题,或者可能会将您的代码覆盖回项目文件中的任何数据,因此我想知道与 Sencha 的正确或预期的协作工作流程是什么.

In a regular environment you could use git, for example, to distribute each file but in architect, you are not expected to edit files manually (which sucks because features like profiles are not exposed in architect). If you do edit them manually, it will cause problems or it may overwrite your code back to whatever data is on the project file so I am wondering what is the proper, or expected collaboration workflow with Sencha.

推荐答案

当我搜索同一主题时,我发现 metadata/ 目录是项目,并且所有组件都被分离到它们自己的元数据文件中.这与根级项目文件一起,可能是版本控制的重要部分.app/ 在保存时重新生成,可能可以从版本控制中排除.

When I had searched for this same topic, I had found that it is the metadata/ directory that is the important meat of the project, and that all of the components are separated out into their own metadata files. This, along with the root level project files, is probably the important part for version control. The app/ is regenerated on save and probably can be excluded from version control.

主要的 xds 项目文件包含更一般的引用,并且可能比元数据组件更改的频率更低.但是当创建新组件或修改项目/应用级别设置时,它会发生变化.

The main xds project file containers more general references and will probably change less often than the metadata components. But it would change when new components are created or project/app level settings are modified.

理想情况下,如果您只签入根文件和元数据文件夹,它应该可以正常工作.

Ideally, if you just check in the root files and the metadata folder, it should just work.

这篇关于与 Sencha Architect 的预期协作工作流程是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆