q3k
/
OctoPrint
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
274 Commits
1 Branch
0 Tags
18 MiB
JavaScript 74.5%
Python 10%
CSS 9.2%
Jinja 5.5%
Less 0.7%
 
 
 
 
 
Go to file
Ferdi van der Werf 956b6ad33d Probably fixes #17 issue 
On OSX spp.Destroy() causes an segfault, sizer.Remove(app) removes app
from the form but tries to call spp.Destroy() afterwards.
By hiding and detaching I created a workaround for the OSX problem.
This solution needs testing on Windows and Linux.
 		2012-04-09 01:26:37 +02:00
Cura Probably fixes #17 issue 2012-04-09 01:26:37 +02:00
scripts Add printrun startmenu shortcut 2012-04-04 11:16:26 +02:00
.gitignore Upstream merge 2012-04-08 22:43:39 +02:00
README.md Update README to point people better to the right location 2012-04-06 16:20:22 +02:00
package.sh https://github.com/daid/Cura/issues/37 package.sh does not run correctly when current directory is not script directory 2012-04-07 13:28:43 -07:00

README.md

Cura

If you are reading this, then you are looking at the development version of Cura. If you just want to use Cura look at the following location: https://github.com/daid/Cura/wiki

Development

Cura is developed in Python. Getting Cura up and running for development is not very difficult. If you copy the python and pypy from a release into your Cura development checkout then you can use Cura right away, just like you would with a release. For development with git, check the help on github. Pull requests is the fastest way to get changes into Cura.

Packaging

Cura development comes with a script "package.sh", this script has been designed to run under unix like OSes (Linux, MacOS). Running it from sygwin is not a priority. The "package.sh" script generates a final release package. You should not need it during development, unless you are changing the release process. If you want to distribute your own version of Cura, then the package.sh script will allow you to do that.