Changes

The good news is if you can get enough of a Zynthian running to open up it's inbuilt webserver, forever known as webconf in these parts, you can select an option that will allow you to return to the stable state.

The good news is if you can get enough of a Zynthian running to open up it's inbuilt webserver, forever known as webconf in these parts, you can select an option that will allow you to return to the stable state.

[[File:Zynthian software repositories.png|600px|right]]

[[File:Zynthian software repositories.png|600px|center]]

In the above example, where a little development is being done, the zynthian-ui ( the main zynthian code that controls the Touchscreen display and the main audio and midi functionality is set to another branch. Selecting the stable check box will get you back to your stable structure, and not destroy your edited code in this separate 'branch' called DUO Piano code if you have behaved properly in setting this up.

In the above example, where a little development is being done, the zynthian-ui ( the main zynthian code that controls the Touchscreen display and the main audio and midi functionality is set to another branch. Selecting the stable check box will get you back to your stable structure, and not destroy your edited code in this separate 'branch' called DUO Piano code if you have behaved properly in setting this up.

It's Microsoft's Visual Studio code,  https://code.visualstudio.com/ know to friends and enemies alike as VSC.

It's Microsoft's Visual Studio code,  https://code.visualstudio.com/ know to friends and enemies alike as VSC.

[[File:Zynthian-visual-studio-code.png|600px|right]]

[[File:Zynthian-visual-studio-code.png|600px|center]]

==== So what is a host machine? ====

==== So what is a host machine? ====

Go to [https://code.visualstudio.com/Download VSC Download page] and pick the appropriate version. For your particular Pi OS. If you are running 64 bit software pick .deb arm64, if you are on a 32 bit Pi OS then pick .deb arm32.If you are on MAC or PC then download accordingly.

Go to [https://code.visualstudio.com/Download VSC Download page] and pick the appropriate version. For your particular Pi OS. If you are running 64 bit software pick .deb arm64, if you are on a 32 bit Pi OS then pick .deb arm32.If you are on MAC or PC then download accordingly.

[[File:Microsft-vsc-download page.png|600px|thumb|right|VSC Download Page]]

[[File:Microsft-vsc-download page.png|600px|thumb|center|VSC Download Page]]

This will download the selected version and you install as appropriate to your operating system. ON my Pi5 I open the download folder  

This will download the selected version and you install as appropriate to your operating system. ON my Pi5 I open the download folder  

<br clear=all>

<br clear=all>

[[File:File-download.png|600px|thumb|right|Pi Desktop Download Folder]]

[[File:File-download.png|600px|thumb|center|Pi Desktop Download Folder]]

and right click on the downloaded file and select Package Install.  

and right click on the downloaded file and select Package Install.  

It will and you will have a new icon appear in your desktop menu in the Programming section.  

It will and you will have a new icon appear in your desktop menu in the Programming section.  

[[File:Visual-studio-code-menu-item.png|600px|thumb|right|Pi Desktop VSC menu item]]

[[File:Visual-studio-code-menu-item.png|600px|thumb|center|Pi Desktop VSC menu item]]

simply pressing on the icon will run Visual Studio Code, but for the moment there is a bit more to consider...

simply pressing on the icon will run Visual Studio Code, but for the moment there is a bit more to consider...

The zynthian software exists as a set of directories ( or folders if you prefer) in a directory on the zynthian called  ...../zynthian.

The zynthian software exists as a set of directories ( or folders if you prefer) in a directory on the zynthian called  ...../zynthian.

[[File:Zynthian-home-directory.png|600px|thumb|right|Zynthian home directory]]

[[File:Zynthian-home-directory.png|600px|thumb|center|Zynthian home directory]]

But it is a little more involved than this and this is linked to the directory /home/pi. Don't worry too much about this it just is part of the overall desire to no longer run the software as the root user and move to more modern versions of the operating system and is an ongoing process. It is however relevant when you try to run the code locally outside of the normal linux tools, specifically systemd.

But it is a little more involved than this and this is linked to the directory /home/pi. Don't worry too much about this it just is part of the overall desire to no longer run the software as the root user and move to more modern versions of the operating system and is an ongoing process. It is however relevant when you try to run the code locally outside of the normal linux tools, specifically systemd.

The GUI software running on the zynth that operates the touchscreen are located within the zynthian ui directory. and there is a file called zynthian.sh. This is a shell script which isn't written in python but in a language, generally called shell script. It is a collection of commands one runs on the terminal we mentioned earlier an allows various things to be configured, before the actual python script that does the work, which is called zynthian_main.py, is run.  

The GUI software running on the zynth that operates the touchscreen are located within the zynthian ui directory. and there is a file called zynthian.sh. This is a shell script which isn't written in python but in a language, generally called shell script. It is a collection of commands one runs on the terminal we mentioned earlier an allows various things to be configured, before the actual python script that does the work, which is called zynthian_main.py, is run.  

[[File:Zynthian-ui-folder.png|600px|thumb|right|Zynthian-ui directory]]

[[File:Zynthian-ui-folder.png|600px|thumb|center|Zynthian-ui directory]]

One of the main things the shell script set up is the debugging level which decides what level of message the zynthian generates when it encounters a logging command in the python script. . .

One of the main things the shell script set up is the debugging level which decides what level of message the zynthian generates when it encounters a logging command in the python script. . .

You put it on Github because that is where the zynthian software itself resides ...

You put it on Github because that is where the zynthian software itself resides ...

[[File:20240120 14h10m25s grim.png|600px|thumb|right|Zynthian page at Github]]

[[File:20240120 14h10m25s grim.png|600px|thumb|center|Zynthian page at Github]]

But that is where Zynthian tells the world about its contribution and you need the good people at zynthian to approve your contribution, and they wont do that till you ask in the right way. . .

But that is where Zynthian tells the world about its contribution and you need the good people at zynthian to approve your contribution, and they wont do that till you ask in the right way. . .

[https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo The github write up is here...] But in summary it's done from the appropriate zynthian page end of the process.

[https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo The github write up is here...] But in summary it's done from the appropriate zynthian page end of the process.

[[File:Zynthian-ui fork page.png|600px|thumb|right|Zynthian page at Github]]

[[File:Zynthian-ui fork page.png|600px|thumb|center|Zynthian page at Github]]

<br clear=all>  

<br clear=all>  

And here are the default options which will suit nearly all circumstances. You should only strike from the testing branch.

And here are the default options which will suit nearly all circumstances. You should only strike from the testing branch.

[[File:Zynthian-ui-forking-2.png|600px|thumb|right]]

[[File:Zynthian-ui-forking-2.png|600px|thumb|center]]

<br clear=all>

<br clear=all>

Here is the confirmation in my personal github space.

Here is the confirmation in my personal github space.

[[File:Zynthian-ui-page-forked to wyleu.png|600px|thumb|right]]

[[File:Zynthian-ui-page-forked to wyleu.png|600px|thumb|center]]

<br clear=all>

<br clear=all>

==== Can I view files on my Zynthian-ui github repository? ====

==== Can I view files on my Zynthian-ui github repository? ====

[[File:Zynthian-ui-page-forked to wyleu.png|600px|thumb|right]]

[[File:Zynthian-ui-page-forked to wyleu.png|600px|thumb|center]]

In fact there is a very useful github element that allows you to view code on gihub within a browser based tool that is nothing more or less than VSC.

In fact there is a very useful github element that allows you to view code on gihub within a browser based tool that is nothing more or less than VSC.

and press the . key...

and press the . key...

[[File:Zynthianwyleu-zynthian-ui-vsc.png|600px|thumb|right]]

[[File:Zynthianwyleu-zynthian-ui-vsc.png|600px|thumb|center]]

<br clear=all>

<br clear=all>

and here in VSC in github showing a ctldev file ready to be examined.  

and here in VSC in github showing a ctldev file ready to be examined.  

[[File:Github-vsc-editing-zynthian-ui-testing-ctrldev file.png|600px|thumb|right]]

[[File:Github-vsc-editing-zynthian-ui-testing-ctrldev file.png|600px|thumb|center]]

<br clear=all>

<br clear=all>