Wykres commitów

16 Commity (9d70160ccbf37e9c764535bcb1c4b78afe027bae)

Autor SHA1 Wiadomość Data
Lex Neva 7ab8dc4018 properly fail build when things break 2018-04-28 20:17:25 -04:00
Lex Neva a4ba6d06e0 get new windows-libembroidery.tar.gz 2018-04-01 21:39:12 -04:00
Lex Neva 084c5555f2
print through web browser (#127)
* spawn a web server and open a printable view of the design in the user's web browser
  * configurable inclusion of client and operator views
  * editable fields for color names, client, title, and purchase order number
  * groundwork laid to save these parameters back into the SVG
* major refactor of codebase to support printing
  * code is organized logically into modules
* added inkstitch logo and branding guidelines
* l10n text extraction now handled by babel
* removed legacy embroider_update extension
* partial fix for #125
2018-03-30 20:37:11 -04:00
Lex Neva c82636df32 fix windows build release 2018-02-23 00:00:33 -05:00
Lex Neva 633ec88186
windows build (#79)
Ink/stitch now supports windows!
2018-02-19 21:43:39 -05:00
Lex Neva 2e3e43e1ca don't lint embroidermodder's python files 2018-01-23 22:17:29 -05:00
Lex Neva 0cbf3544b7 fast finish 2018-01-23 22:15:09 -05:00
Lex Neva c9e90dc61d prevent build loop 2018-01-23 22:06:24 -05:00
Lex Neva 858be29401 trying for a single pre-release per branch 2018-01-23 21:56:48 -05:00
Lex Neva acaebaa956
add params for "TRIM after" and "STOP after" (#29)
* adds new options to Params: "TRIM after" and "STOP after"
  * adds tooltip support to Params
  * inkstitch now includes libembroidery and can directly output any supported file type
    * this avoids the need for `libembroidery-convert` and compiling embroidermodder!
  * TRIM support for DST format (inserts 3 JUMPs)
  * STOP command supported as an extra color change that the operator can assign to code C00
  * TRIMs cause the following jump stitch not to be displayed in the Embroidery layer
2018-01-23 20:13:37 -05:00
Lex Neva e13c16d50d don't deploy on lint builds 2018-01-13 22:46:44 -05:00
Lex Neva 38d88d1a2b hopefully finally fix travis deploy rules 2018-01-13 22:08:09 -05:00
Lex Neva 143eb342a4 fix travis deploy conditions 2018-01-13 20:45:14 -05:00
Lex Neva 8bab858be6
pyinstaller release method (#16)
pyinstaller packages up all of a python script's dependencies and builds them into standalone executables. It can either do a directory (containing a single executable and a bunch of shared libraries) or a self-contained executable that effectively just contains a compressed version of the directory.

The problem is, if you have several scripts like we do, you get several large directories or standalone binaries, and there's a ton of duplication between them. Fortunately it looks like using the directory method and just combining the directories works fine (for this project).

This PR runs the above build on any tagged commit and publishes a release in github containing the pyinstall-ified tarball. If the tag is named like "v1.2.3" _and_ the tag is on the master branch, then the github release will be marked as "production". Otherwise, it will be marked as a "pre-release". This means that we can build testable tarballs of the extension in a pull request by tagging a commit.
2018-01-13 20:18:50 -05:00
cclauss f244f58a17 Comment out: pip install -r requirements.txt 2018-01-07 15:41:53 -05:00
cclauss b4d72df937 Add free automated flake8 testing of pull requests
The owner of the this repo would need to go to https://travis-ci.org/profile and flip the repository switch __on__ to enable free automated flake8 testing of each pull request.
2018-01-06 19:51:28 -05:00