No Description
karrad 3698b492d5 T4625 resetting GLCD progress bar, updating start gcode slice message 3 days ago
.github Improve issue template a bit 11 months ago
cmake Fix PYTHONPATH pass-through 11 months ago
cura T4225: Added toolhead priority 1 month ago
docs Some extra tips for users of the profiler. 1 year ago
icons updated colors, .ico and Cura LE icons and splash screen 1 year ago
plugins Changed Marlin FW to v1.1.9.28 for all LulzBot printers. 1 month ago
resources T4625 resetting GLCD progress bar, updating start gcode slice message 3 days ago
tests Merge remote-tracking branch 'um/3.2' 10 months ago
.gitignore adding pro series filament 8 months ago
CMakeLists.txt Reintroducing rCT7472f5546afa0682f24bb5a8fe0ce0397f82ab81 Add possibility to manage PYTHON_SITE_PACKAGES_DIR. 10 months ago
CPackConfig.cmake Removing PostProcessing repo version number, since it was merge into cura-lulzbot repo. 8 months ago
Jenkinsfile Move Jenkins timeout into parallel_nodes block 10 months ago
LICENSE Changing AGPLv3 to LGPLv3 1 year ago
README.md Merge remote-tracking branch 'um/3.2' 10 months ago
build.sh Add the scripts used to build the release package (still needs some more work, but works on my desktop) 3 years ago
cura-lulzbot.desktop.in Merge remote-tracking branch 'um/3.1' into upstream3.1 1 year ago
cura.appdata.xml T1244: Replacing Cura2 names with cura-lulzbot or Cura LulzBot Edition. 1 year ago
cura.sharedmimeinfo Adding cura.sharedmimeinfo 2 years ago
cura_app.py T1152: For linux log console output for frozen app to console instead of the file. 9 months ago
installer.nsi Typo in association 1 year ago
pytest.ini Added unit test stub 2 years ago
run_cura-lulzbot.sh T1244: Replacing Cura2 names with cura-lulzbot or Cura LulzBot Edition. 1 year ago
run_mypy.py Make the run_mypy.py script find Uranium via the PYTHONPATH env var. 1 year ago
setup.py Change AGPL to LGPL 1 year ago
version.json updated version to 3.2 10 months ago

README.md

Cura

This is the new, shiny frontend for Cura. Check daid/LegacyCura for the legacy Cura that everyone knows and loves/hates. We re-worked the whole GUI code at Ultimaker, because the old code started to become unmaintainable.

Logging Issues

For crashes and similar issues, please attach the following information:

  • (On Windows) The log as produced by dxdiag (start -> run -> dxdiag -> save output)
  • The Cura GUI log file, located at
    • %APPDATA%\cura\<Cura version>\cura.log (Windows), or usually C:\Users\\<your username>\AppData\Roaming\cura\<Cura version>\cura.log
    • $USER/Library/Application Support/cura/<Cura version>/cura.log (OSX)
    • $USER/.local/share/cura/<Cura version>/cura.log (Ubuntu/Linux)

If the Cura user interface still starts, you can also reach this directory from the application menu in Help -> Show settings folder

For additional support, you could also ask in the #cura channel on FreeNode IRC. For help with development, there is also the #cura-dev channel.

Dependencies

  • Uranium Cura is built on top of the Uranium framework.
  • CuraEngine This will be needed at runtime to perform the actual slicing.
  • PySerial Only required for USB printing support.
  • python-zeroconf Only required to detect mDNS-enabled printers

Configuring Cura

  • Link your CuraEngine backend by inserting the following line in ~/.config/cura-lulzbot/config.cfg : [backend] location = /[path_to_the..]/CuraEngine/build/CuraEngine ```

Build scripts

Please checkout cura-build for detailed building instructions.

Plugins

Please check our Wiki page for details about creating and using plugins.

Supported printers

Please check our Wiki page for guidelines about adding support for new machines.

Configuring Cura

Please check out Wiki page about configuration options for developers.

Translating Cura

If you’d like to contribute a translation of Cura, please first look for any existing translation. If your language is already there in the source code but not in Cura’s interface, it may be partially translated.

There are four files that need to be translated for Cura:

  1. https://github.com/Ultimaker/Cura/blob/master/resources/i18n/cura.pot
  2. https://github.com/Ultimaker/Cura/blob/master/resources/i18n/fdmextruder.def.json.pot
  3. https://github.com/Ultimaker/Cura/blob/master/resources/i18n/fdmprinter.def.json.pot (This one is the most work.)
  4. https://github.com/Ultimaker/Uranium/blob/master/resources/i18n/uranium.pot

Copy these files and rename them to *.po (remove the t). Then create the actual translations by filling in the empty msgstr entries. These are gettext files, which are plain text so you can open them with any text editor such as Notepad or GEdit, but it is probably easier with a specialised tool such as POEdit or Virtaal.

Do not hestiate to ask us about a translation or the meaning of some text via Github Issues.

Once the translation is complete, it’s probably best to test them in Cura. Use your favourite software to convert the .po file to a .mo file (such as GetText). Then put the .mo files in the .../resources/i18n/<language code>/LC_MESSAGES folder in your Cura installation. Then find your Cura configuration file (next to the log as described above, except on Linux where it is located in ~/.config/cura) and change the language preference to the name of the folder you just created. Then start Cura. If working correctly, your Cura should now be translated.

To submit your translation, ideally you would make two pull requests where all *.po files are located in that same <language code> folder in the resources of both the Cura and Uranium repositories. Put cura.po, fdmprinter.def.json.po and fdmextruder.def.json.po in the Cura repository, and put uranium.po in the Uranium repository. Then submit the pull requests to Github. For people with less experience with Git, you can also e-mail the translations to the e-mail address listed at the top of the cura.pot file as the Report-Msgid-Bugs-To entry and we’ll make sure it gets checked and included.

After the translation is submitted, the Cura maintainers will check for its completeness and check whether it is consistent. We will take special care to look for common mistakes, such as translating mark-up <message> code and such. We are often not fluent in every language, so we expect the translator and the international users to make corrections where necessary. Of course, there will always be some mistakes in every translation.

When the next Cura release comes around, some of the texts will have changed and some new texts will have been added. Around the time when the beta is released we will invoke a string freeze, meaning that no developer is allowed to make changes to the texts. Then we will update the translation template .pot files and ask all our translators to update their translations. If you are unable to update the translation in time for the actual release, we will remove the language from the drop-down menu in the Preferences window. The translation stays in Cura however, so that someone might pick it up again later and update it with the newest texts. Also, users who had previously selected the language can still continue Cura in their language but English text will appear among the original text.

License

Cura is released under the terms of the LGPLv3 or higher. A copy of this license should be included with the software.