The following code generates the image provided below it. The coordinates passed into the line via PhoTeX are not having their coordinate system properly converted before being passed into svg.

define color blue #0000FF
define font arial "Arial" 12

canvas "Test.png" 300 300 {
    line -50w 0 50w 0 blue 3
}

Changes In This Clippy Update

Proper Clipping

Fixed clipping for:

• Rect
• Circle
• Ellipse
• Polygon Performed basic tests for these, but did not try any crazy edge cases. You can make a clipped object by doing this:

clipped rect 0 0 300 300 { ... } // All items inside ... that overflow the rect boundaries will be cut off

[New feature] Inner and Outer Clipping

I felt there was a need for two types of clipping when clipping an outlined object. This is due to the fact that you can either clip inside the stroke or outside the stroke and obtain a completely different effect. I explain the two types below with examples.

Inner Clipping

One can "inner clip", or clip inside the stroke by writing code like the following:

clipped in outlined #FF0000 10 rect 0 0 300 300 {
        image 0 0 500 500 "scor.jpg"
}

// OR just

clipped outlined #FF0000 10 rect 0 0 300 300 {
        image 0 0 500 500 "scor.jpg"
}

Yielding something like:

Inner Clipping

One can "outer clip", or clip outside the stroke by writing code like the following:

clipped out outlined #FF0000 10 rect 0 0 300 300 {
        image 0 0 500 500 "scor.jpg"
}

Yielding something more like this:

An Important Note

Both inner and outer clipping work perfectly for circles, rectangles, and ellipses. But for custom polygons, clipping can be quite difficult, so as of now, only inner clipping is supported. I hope to work on this again in the future to add outer clipping for custom polygons.

@JoeFurfaro It seems to work. I think we should use this as it simplifies the lark code and makes it much more flexible in terms of allowing whitespace.

Some Stuff I Fixed

• Top level placement of polygons (#5)
• Top level placement of lines (#4)
• Image primitive scaling and placement (#2)

Issue(s) That Still Need To Be Fixed

(At some point)

• Some placements of lines / polygons are still weird in PNG export, but all placements seem perfect for SVG preview in VS code and in browser
• I will make a new issue for the above point soon ^

When trying to build a simple triangle with this code:

define color blue #0000FF

canvas "Test.png" 300 300 {
    polygon -50w 50h 0 -50h 50w 50h blue
}

I get this output:

This has to do with no parent element translating the points in the polygon

Note if I place the polygon inside of a rect that is the same size as the canvas, I get the following output

(with this code)

define color blue #0000FF

canvas "Test.png" 300 300 {
    rect 0 0 100w 100h {
        polygon -50w 50h 0 -50h 50w 50h blue
    }
}

Modifications

• Updated requirements.txt to contain all dependencies
• Created a conda environment that contains all dependencies
• Exported photex conda environment to environment.yml in project root
• Added install instructions for conda environment to README.org Getting Started section

Reasons for Changes

• Faster quickstart for virtual environment users
• Clearer "Getting Started" instructions
• Requirements file was out of date

I think it should be their center. Here is an example:

From this code: canvas "Test.png" 1000 1000 { image 0 0 200 "scor.jpg" }

Svg is: <svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="1000" height="1000"> <image x="500" y="500" width="200" height="104.16666666666667" href="scor.jpg" /> </svg>

Currently we only export to SVG and/or PNG. Let's add JPG/JPEG as well. According to Joe, this can probably be done via the already added Pillow library.

I just realized that implementing the proposed usings/imports is actually quite trivial! We can do something similar to how C++ handles header files. We can copy the import into the file we are processing at the location of the import statement.

Proposed changes

Add another pass over the input file before the main pass. This pass will simply replace all lines that start are in the form of using [relative path to file] with the contents of the file at the path location. Then we can run through and do the main parsing.

@JoeFurfaro what are your thoughts about this?

The Problem

What if I want an SVG, PNG, and JPG export of my canvas?! I shouldn't have to write the canvas definition 3 times!!!

The Solution

Modify canvas definitions to support multiple file type arguments after the name... eg:

canvas MyCanvas svg 500 500 {
    ...
}

OR

canvas MyOtherCanvas svg png jpg 500 500 {
    ...
}

Idea

The goal is to automatically generate a Constants.py file from our Lark grammar file. This will help to minimize hardcoded and magic values throughout the interpretter.

What's changed

• There is a new Constants.py file that contains the constants expressed in the global lark grammar file.
  • This file can be regenerated by running python3 ConstantsBuilder.py from the src/classes/parser folder
• There is a new file that parses the grammar for the hardcoded values and extracts them into Constants.py

Why

• To make life easier by removing hardcoded values (less mistakes as things change as well as convenience as you need to remember less magic values to make changes)
• To add flexibility and freedom to change and experiment more easily
• Also acts as documentation as types and other things can be added later

TODO

• [x] Basic functionality
• [x] Apply to all files. Currently only photex.py uses the constants.py file
• [x] Add alias extraction
• [x] Test it
• [ ] Cleanup code (currently it is quite ugly

I ran pip3 install -r requirements.txt but kept getting the following error

OSError: no library called "cairo-2" was found
no library called "cairo" was found
no library called "libcairo-2" was found
cannot load library 'libcairo.so.2': dlopen(libcairo.so.2, 2): image not found
cannot load library 'libcairo.2.dylib': dlopen(libcairo.2.dylib, 2): image not found
cannot load library 'libcairo-2.dll': dlopen(libcairo-2.dll, 2): image not found

I think we need to clarify in the readme the troubleshooting steps for those who get this (and other) installation issues