I loved tixy when I first discovered it a few years ago so created this https://www.mathsuniverse.com/tixy (with permission from the original author) with puzzles to solve on the tixy grid. I use it with my computer science students who get really into it.
I was blown away by the little functions at first and I too made a clone to experiment with calculang [1].
I added an evaluation feature (F9) so you can select sub-expressions and see what they do, which was helpful to figure out some patterns (video in [2])
What's wrong with that statement? It has historically and traditionally been true for raster displays, even if there do exist ways to use standard Cartesian-style coordinates with a computer.
There top left has usually been (0, 0) for hardware pixel coordinates (although even then there’s plenty of exceptions, e.g. mode 13h scrolling) but as a blanket statement about computer graphics in general it’s misleading.
I'm struggling to see the problem with this statement, other than maybe to add in the word "usually". My students will know of graphs in maths where the origin is always bottom left. When working with HTML canvas and every other computer graphics situation I've worked in, it's top left instead.
"PostScript uses a coordinate system where the origin is at the bottom-left corner of the page, with the x-axis increasing to the right and the y-axis increasing upwards."
Oscilloscopes use middle-left.
Unreal engine and SketchUp use Screen middle with xy increasing to the right.
in AutoCAD, the user coordinate system is 1/3 of the screen to the left for the origin, with X increasing to the right, and Y increasing upwards.
Almost all raster displays, and memory based programs assume top left, because that is how it was done first - counter intuitive.
It it not counter intuitive and the decision extends far earlier than the first displays.
A raster image onscreen is displayed in the order that the data appears when written down. It stands to reason that a data depiction should be in the same orientation as the display orientation. Displays were created by people who read from left to right, top to bottom. If the displays did not follow that order. images would be flipped or rotated when displayed in a data form.
The first pixel written to the display is in the top left because we read from the top left. If writers of another language had have popularised the text, perhaps things might have been different.
It draws a slightly tilted sine wave gradient (i=16y+x so atan(1/16) ≈ 3.6°) whose frequency increases until it starts to alias due ro the limited resolution (cf. Nyquist sampling theorem) and exhibit what’s essentially the wagon wheel effect [1]. Nice illustration of signal processing fundamentals!
I would love something like this in my living room. Especially if it is not just a screen. Maybe a grid of 256 screens? Or inflating balloons? Something easier to make? Just on/off big pixels?
104 comments
[ 3.2 ms ] story [ 195 ms ] threadhttps://fig.sonnet.io
It’s pretty fun because the shape dynamics are time, and not pressure/tilt based, so you need to draw in a rhythm.
Here’s how they work and how they’re implemented:
https://untested.sonnet.io/notes/fig-tree-brushes/
I was blown away by the little functions at first and I too made a clone to experiment with calculang [1].
I added an evaluation feature (F9) so you can select sub-expressions and see what they do, which was helpful to figure out some patterns (video in [2])
[1] https://calculang-editables.netlify.app/tixyish
[2] https://www.youtube.com/watch?v=uXUd_-xrycs
Umm...
Oscilloscopes use middle-left.
Unreal engine and SketchUp use Screen middle with xy increasing to the right.
in AutoCAD, the user coordinate system is 1/3 of the screen to the left for the origin, with X increasing to the right, and Y increasing upwards.
Almost all raster displays, and memory based programs assume top left, because that is how it was done first - counter intuitive.
A raster image onscreen is displayed in the order that the data appears when written down. It stands to reason that a data depiction should be in the same orientation as the display orientation. Displays were created by people who read from left to right, top to bottom. If the displays did not follow that order. images would be flipped or rotated when displayed in a data form.
The first pixel written to the display is in the top left because we read from the top left. If writers of another language had have popularised the text, perhaps things might have been different.
Why are device-independent bitmaps upside down? Raymond Chen https://devblogs.microsoft.com/oldnewthing/20210525-00/?p=10...
I think you had to wait for WinG or maybe even DirectX to get normal 1:1 mapping.
OpenGL is so old it had same stupid ideas about coordinates.
In OpenGL is (center, center)
Works well on phone. The phone keyboard is a bit clumsy but it works (that’s a phone issue)
I love the instant visual feedback!
'Vanishing Curve'
Learned by scrolling far enough right in view source: The last line is editable and eval'd.
Request to author: keep the newlines.
Right. https://tixy.land/?code=alert(%22foo%22)
https://tixy.land/?code=(y%2Fi*y%2Fsin(x%2Bt))*max(cos(t)%2C...
https://tixy.land/?code=sin%28i%2Bt%29
[1] https://en.m.wikipedia.org/wiki/Wagon-wheel_effect
a radar
https://c50.fingswotidun.com/show/?code=28*ddx*%24%3Ay*%243o...*
Quite a fun challenge.
The Suffix is 2<02->P8dus:vs
which is
https://tixy.land/?code=sin%28t%29*%281%2Bx%2By%29-x
I would love something like this in my living room. Especially if it is not just a screen. Maybe a grid of 256 screens? Or inflating balloons? Something easier to make? Just on/off big pixels?
There's no enter on Android Chrome on phone.
https://tixy.land/?code=sin%28t*x%29%2Bi%2F256