Monday, January 26, 2015

Elegant pairs


I was experimenting with the pervious post's pattern and the particular twist I was attempt wasn't fruitful but I did end up with this pattern. There two key pairs in this pattern: two purple rhombi (made with triangles) and the prominent pink/purple triangle-pentagons. I call this pattern elegant because of its fine lines: the slim dart gap between the rhombi, and the near touching pink polygons. Perhaps these fine features are also amplified by this type of symmetry.
I may have to augment my tool to help play with the colour choice and perhaps add in an easy centering tool. I guess these are less of a priority just a little of an annoyance...
Here are some png wallpapers

Sunday, January 25, 2015

Nice 6-fold symmetry


I like this one. Essentially, it's variations on a theme. Perhaps I add a twist and see if it will be as pretty.

On a side issue, tinyurl.com/p3c6mdh/newPentTri2.svg didn't work when I put https which redirects to https://c3b8f482385fc05f71d246e2e23a26cb99a3c770.googledrive.com/host/0BwD1YaggiIIAY1gxNEJEa2JKNlU/newPentTri2.svg which needs the https. Not surprising but there certainly is a lot of details to juggle--at least when you are doing posting content on the cheap... Of course, if Blogger simply let me upload my svg files I wouldn't have to do any gymnastics... I ended haven't to use my own host.

Sunday, January 18, 2015

Pentagons and Triangles


Here's a new pattern.  I have been a bit too busy to post this last semester.  Hopefully, next semester I'll have a bit more time to play with patterns.  This one has a few variations that I may continue to play with...  

Saturday, September 13, 2014

Tileland+ code

Tileland+ interface
Along with an interface update, I added a some language extras.  The native Tileland instructions remain (polygons, colours, and turning) but now I have added the environment instructions to the language.  In particular, I have added clipboard manipulation instructions. Although somewhat hidden, this addition is a metalanguage or a preprocessing language.
6o4b>

6o4b>6o4b>6o4b>6o4b>
It's actually pretty simple when you see an example.  An orange hexagon with a blue square would be 6 o 4 b.  The picture below is a that with a right turn or 6o4b>.  The colour follows the shape so that it has something to colour. Doing that 4 times is just 6o4b>6o4b>6o4b>6o4b>.  Another way to make the pattern is to use the clipboard.  I haven't yet introduced a concept of a cursor yet so the clips come from the entire current code. There are 5 instructions that affect the clipboard: x, v, n, m, and q.  The first, x, simply transfers the current code into the clipboard.  The second, v, adds the first clip to the current code. The next two n and m roll the clips left and right. The final one, q, clears all the clips.  The other letter instruction, z, removes the last chunk from the current code (only really useful in an immediate situation).  So, to make the loop of squares and hexagons using the clipboard you could type 6o4b>xvvvv or cut and paste that into the code textbox. The result of either action is [6o4b>][6o4b>][6o4b>][6o4b>] -- the brackets chunk the code but do not affect the resulting picture.

The code in the Tileland+ image was produced by using 2 different clips -- this required using the n and m instructs to change the first clip back and forth.  For instance, in this code, "6o4>6p>>>4o>x 6o4>x  vvvnvmvnvmvnvv", the first two chunks make the clips and the third chunk use the two clips.  In terms of cutting and pasting sometimes it's best to start with a fresh clipboard so an initial q can make a fresh start -- so q6o4>6p>>>4o>x6o4>xvvvnvmvnvmvnvvmvnvvmvnvvv so  makes the pattern in the image.

Play around with this version of Tileland and tell me what you think.

Wednesday, August 27, 2014

New TileLand prototype

This thing is "alpha" code.  It's hot off the press with enough functionality to do interesting things but it's not very polished.  I added the link on the side bar so it'll be easy to access.  The programs come in graphical and textual forms which currently allows you to save your programs by cutting and pasting the text into a place to use later. I stripped down the instructions to one letter to make it more compact and uniform and ease of coding with a keyboard.  I'm sure things will change when I get the time.
There are some annoying bugs that I will fix soon: the one the is most irksome is that my collision detection has some issues that I believe are mainly occurring with triangles but I really haven't done any extensive testing...  

Saturday, June 07, 2014

Revisiting an unravelling

This is based on an old pattern where I took a clockwise loop of 6 pentagons and combined them with two counter clockwise loops of 3 hexagons resulting in a clockwise loop of pentagons and hexagons. One way to think about the process is to imagine unravelling the loop of pentagons. I used this pattern back in back in 2007 and 2006 but this one has a bit more of a twist.
Perhaps I should come up with a visual of this unravelling. I was hoping I would find one in my blog but I didn't. I should make a better index for this thing...done. In this screen capture, you can see that the outside of the original pentagon loop is now the inside of the composed shape and the inside of the original loop corresponds to the 4 sides of the pentagons the are on the outside of the composed shape. Perhaps I'll play some more with this ‡(double dagger shape which I found its html code here).

Sunday, June 01, 2014

Zig, Zag, Zog


Here's just a bit of play before I head to Basketball. I call it zig, zag, zog because there are 3 chunks to the code. Usually, I have a standard zig-zag pattern alternating between to 2 chunks of code. But there are three loops: one if made of zig and zag, another is made from zig and zog, and the final is made of zag and zog. Not too deep but still nice with my new SVG output.
This picture of the code shows a as zig, b as zag, and c as zog. It's pretty clear that a calls b which calls a making a zig-zag loop; and similarly that b calls c which calls b making the zag-zog loop. But the zig-zog loop takes a bit of though--in the code for b since it calls both an a and a c. But essentially c results in a cbcbcb loop with that last b also calling an a so the first c essentially calls an a. Similarly a essentially calls an c thus resulting in the zig-zog loop. There's a bit of twisting calling going on.

Popular Posts