user interface

This article describes the lcVCS user interface

###Projects Stack

1. Projects List - doubleClick to edit the name
2. Add/Delete/Search GitHub
3. Import and Export the project
4. The path is the path to the repo root folder (not editable)
5. The build path is a relative or full path to the directory where the stackFiles should be imported and exported from. The merge function is run on this so you can use LiveCode functions like revEnvironmentUserPluginsPath(). If you leave this empty the exported files will be next to the stackFiles.
6. The resource paths is a list of stackFiles or folders that should be loaded into memory during import and export. Merge is also run on this property.
7. The lcVCS plugin system allows you to add support for custom controls and libraries that save object references in in custom properties. See the discussion in the README about ID/UUID issues for reasons why you might need to do that.


####Project StackFiles

Stackfiles must be listed in order from the first to be imported/exported to the last. Objects on the lower stackFiles can refer to objects on higher in the list but not the other way around.


###GitHub Search

The GitHub Search feature is intended to help lcVCS users find open source LiveCode projects they might be interested to use or contrinbute to. In combination with the build path feature of lcVCS projects this creates means that plugins etc can be imported directly into the user extensions folder and users will be able to keep themselves updated using git and lcVCS.

Select a project then click Add Project then browse to and choose a folder to clone the repo into. The project will be added to the projects list once cloned and you will be able to import the stackFiles.