|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4502(para)
|
|
|
981.
|
|
|
Fixing Your First Bug
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4502(title)
|
|
|
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!
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4503(para)
|
|
|
983.
|
|
|
Sharing Your Changes with the OpenShot Team
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4503(title)
|
|
|
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:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4504(para)
|
|
|
985.
|
|
|
$ bzr diff > mychanges.patch
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4509(command)
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4511(para)
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4512(para)
|
|
|
988.
|
|
|
Join the OpenShot Developers Team on LaunchPad
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4512(title)
|
|
|
989.
|
|
|
If you are fixing bugs or adding new features to OpenShot, please consider <ulink url="https://launchpad.net/~openshot.developers">joining our </ulink><ulink url="https://launchpad.net/~openshot.developers">team</ulink> on LaunchPad. [nbsp]We have a mailing list that will keep you up to date on the newest bug reports and plans related to OpenShot.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
openshot.xml:4513(para)
|
