Changes

m
Line 55: Line 55:     
=== How to test ===
 
=== How to test ===
 +
For testing your development, you should install your forked development version into your zynthian box. Something like this could do the job:
 +
 +
systemctl stop zynthian
 +
cd /zynthian
 +
mv zynthian-ui zynthian-ui.orig
 +
git clone https://github.com/#your_github_account#/zynthian-ui.git
 +
cd zynthian-ui
 +
git checkout #your_development_branch#
 +
/zynthian/zynthian-sys/sbin/zynthian.sh
 +
 +
For better debugging, i recommend to edit "/zynthian/zynthian-sys/sbin/zynthian.sh" and enable exception raising, like that:
 +
 +
ZYNTHIN_RAISE_EXCEPTIONS=1
 +
 +
For avoiding adding/commiting every time you change/fix something, i recommend copying the files directly to your zynthian box. This will avoid polluting the git history and simplify the development/test cycle. Once your changes are tested and your code stable, you can add/commit and sync your zynthian box from your development repo, like this:
 +
 +
cd /zynthian/zynthian-ui
 +
git checkout .
 +
git pull
 +
 +
This will overwrite your local changes and will take the latest changes from the repo.
    
=== How to get the software into Zynthian(-master) ===
 
=== How to get the software into Zynthian(-master) ===
   −
If it's your first developiment for zynthian, you should get familiar with git and github. I recommend start "forking" in github the repository you want to work in (zynthian-ui) and creating a "branch" for your development. When you have a stable version of your work, you should make a "pull request" from your forked github repository.
+
If it's your first development for zynthian, you should get familiar with git and github. I recommend start "forking" in github the repository you want to work in (zynthian-ui) and creating a "branch" for your development. When you have a stable version of your work, you should make a "pull request" from your forked github repository.
 +
 
 +
See also: [[Zynthian_Devel_General|How to contribute to Zynthian development?]]