kmf
October 24, 2018, 4:13pm
1
I have created issue 178 on github to document the fact that code needs to be added to the Seamly2D application to suport the user interface to the cloud based pattern sharing utilities at seamly.cloud
Potential contributors would clone the develop branch of the repository to create their own copy. For submitting code for issue 178, they would create a branch named feature-178 and push all new or changed code to that feature branch.
Please put future discussion about this new interface software here on this forum thread.
see also
opened 04:05PM - 24 Oct 18 UTC
enhancement
linked issue
API
seamlycloud
New SeamlyCloud feature
The Seamly2D program needs to have an clear and functional interface to the patt… ern cloud at **seamly.cloud**
This will be integrated into the Seamly2D code and will include as a minimum:
- Fetch a list of available patterns from the pattern cloud.
This would include subsets:
template patterns (e.g. basic blocks in various systems)
"my patterns"
shared patterns
Open a pattern directly in Seamly2D from the above list.
Save a new pattern version from Seamly2D directly to the pattern cloud.
The interface must provide a way to apply local and cloud stored measurement files to a pattern.
see also
# Contributing code
Thanks for contributing to Seamly code, documentation, translations, website, and wiki!
Our workflow is based on **Git Flow**, outlined in the steps below.
As always, please fix only one issue at a time.
Build your branch with Qt and test, then make a pull request.
Read more about **Git Flow**: http://nvie.com/posts/a-successful-git-branching-model/
Read more about **Pull Requests**: https://help.github.com/articles/about-pull-requests/ and https://help.github.com/articles/creating-a-pull-request/
## Naming conventions
Name your branch after the issue you will fix. Example: Name your branch **issue-#155** for issue #155.
The permanent named branches on this repo are:
* **develop** - Contains next major release. Used for testing and sharing among developers.
* **master** - Used only for releases.
* **release-x.x.x** - Created from **develop**. Contains feature freeze state before the next major release. Used for preparing each major & minor release with updated build information. Merge to **master** with new tag to create a new release.
* **hotfix-x.x.x** - Create from **develop** and **master**. Contains a quick emergency fix for big bugs. Merge to **master** (or **release**) and **develop**.
show original
1 Like