Browsing Icelandic translation

968.

If you already have an <emphasis>/openshot/</emphasis> folder, just change your current directory to it, and run the following command to get the lastest version:

971.

Now you should have the latest source code for OpenShot. [nbsp]To launch OpenShot from this folder, you must run the following commands. [nbsp]Remember, you must already have the dependencies for OpenShot installed, which is covered in the next topic.

974.

If you have made some changes to the OpenShot source code, and want to see everything you have changed, run this command:

976.

If you are unhappy with your local changes, and want to revert your changes, run this command:

979.

Once you have gotten the latest source code, the next step is to install all of the required dependencies. [nbsp]I would recommend installing OpenShot from your favorite package manager (such as Synaptic). [nbsp]This will install a version of OpenShot and all the required dependencies. [nbsp]This will not conflict with your local version of OpenShot source code. [nbsp]The only trick is to remember that the <guimenu>$ openshot</guimenu> command will launch the official version of OpenShot, and not your local version. [nbsp]So, you must remember to launch OpenShot with the following commands:

980.

Now that you have the latest source code and all of the dependencies, you can either use a text editor (such as gedit), or a full Python IDE, such as <ulink url="http://www.eclipse.org/">Eclipse</ulink> or <ulink url="http://www.aptana.com/">Aptana</ulink> (with <ulink url="http://pydev.org/">Pydev</ulink>) to modify the source code. [nbsp]The advantage of using a full Python IDE is the enhanced debugging capabilities. [nbsp]It is beyond the scope of this document to teach you how to debug Python with Eclipse or Aptana, but there are lots of good tutorials online.

982.

Now that you have a local version of OpenShot running, fixing bugs and adding new features is easy. [nbsp]Just modify the files, and re-launch OpenShot to see your changes. [nbsp]Of course, I can't tell you exactly how to fix a bug, that is up to you. [nbsp]So, good luck!

984.

Once you have fixed your first bug or added a great new feature, the next step is to share it with the OpenShot Team, so we can be sure your changes get into the official version of OpenShot. [nbsp]The easiest way to share your changes is to create a patch (or diff). [nbsp]Use the following command to create a patch:

986.

This will create a file called mychanges.patch, which should have all of the changes for all the files you have modified. [nbsp]Of course, if you have created new files, you will need to compress those up into a ZIP or TAR file, and include them with your mychanges.patch file.

987.

Next, create a <ulink url="https://launchpad.net/openshot/+filebug">new bug report</ulink> on LaunchPad (or find an existing bug report), and upload your patch and related files to the bug report. [nbsp]That's it! [nbsp]The OpenShot team will be notified by email that a patch has been submitted. [nbsp]Now you can subscribe to the bug report, and follow along to see if there are any questions or comments about your patch.