-
This is still my most favorite CSS-hack of all time, from jQuery-times.
-
The whole process works now! Opening file, editing and saving to JPEG.
-
I managed to get the correct resulting image-crop from OpenCV. I passed the wrong Vector2 to CV as the destination-size before, and got the original images ratio for some reason. Opening an image via Drag&Drop also works. The only thing left is to add saving the file.
-
Added Drag & Drop and Raygui Panels and Styles. Next will probably be to load and save images. Currently the image is hardcoded. Planning to add some more ornament. A nice-to-have would be to crop the destination-image to the final crop without the “outside”.
-
It kinda works now. At least the straightening part. I’m feeding the images into OpenCV, and converting them back to a Raylib-compatible format. The whole load/save-cycle is still missing. Thinking about doing a crop-selection on the resulting image.
-
Switched to trying to use OpenCVs Transformation Matrix with Raylib. I’m getting some pixels, but nothing really working yet. Feels adventurous.
-
Currently playing around with C++ and Raylib. Trying to re-create Skewbacca, the tool I created to un-skew laptop-images. I got pretty much everything down except getting the correct transformation matrix. I got a little help from Claude, but the the calculation didn’t do quite the right thing, so now attempting to come up with it myself. I really don’t want to introduce OpenCV or ImageMagick.
-
Deno and Skia-Canvas
I have used Deno for Advent of Code, and I like the OOTB Typescript-Support. It’s also pretty simple to add Skia-Canvas for graphical stuff without having to use Raylib (which is great, but if you don’t need Input or Sound, and want to use canvas-API, may be too much).
$ deno add npm:skia-canvas
Add
"nodeModulesDir": "auto"
to deno.json$ deno install --allow-scripts $ deno run --allow-all main.ts
This example can be used as a starting-point:
import { Window } from "skia-canvas"; const win = new Window(300, 300); win.title = "Canvas Window"; win.on("draw", (e) => { const ctx = e.target.canvas.getContext("2d"); ctx.lineWidth = 25 + 25 * Math.cos(e.frame / 10); ctx.beginPath(); ctx.arc(150, 150, 50, 0, 2 * Math.PI); ctx.stroke(); });
-
The current thingie I’m working on is a game inspired by Golden Idol. The main loop is sorting chat-threads. Discover a story by sorting chats. Making a little prototype in HTML. The most annoying part is coming up with a story. Generated some moods for inspiration.
-
Changed the approach to only get the possible solutions for each next step, which sped up the board-solving from infinity to an instant. The “hardest Sudoku” is now being solved instantly. The only thing that doesn’t really work quickly or at all, is to fill a completely empty board. Not sure if it should, anyways. Will clean up the modules next.
-
The brute-force-method caused a major headache but it works! I can solve all Sudokus in theory, but for more than a couple 0s, it takes longer than a few seconds. I’m generating a list of 0s and their possible numbers, then recursively trying out all possible combinations. So far without “cleaning up” the list as the process happens, so it’s highly ineffective. My next goal would be to manage solving any board in an “awaitable” time.
-
So currently I’m checking the Sudoku board for 0s with only one possible solution. This works for most easy boards, but as soon as it gets medium-hard, it’s not possible to finish the board only by analyzing rows, cols and quads. I don’t know if there are any other algos for solving this in a smarter way (there 100% are), but I didn’t want to just look up a solution before I didn’t do at least a brute force method first.
- Go through all 0s
- Use their first possible number
- As soon as I hit a wall, start from beginning with the next possible number
This sounds heavy but maybe I can reduce the attempts in some way.
-
Simple solving Sudoku works now with multiple solving passes.
-
On the Sudoku-Front: The easier part is done, I can analyze rows of numbers if they are valid (1-9) and if they are “ok”, which means they may contain 0s, but no number is used more than once. Do I go the brute force-approach first? I’m thinking to first collect all 0s and fill out the ones that only have one possible solution. Repeat until there are only 0s with multiple possible numbers left. This approach may finish very easy Sudokus. Then try out all kinds of combinations of possible numbers, until there is no “contradiction” left.
-
Game idea: Unsorted chat bubbles that need to be sorted into the right chronological order. Could be a group chat. Could be combined with photos, videos or images. Would be trivial to prototype with HTML/CSS/JS.
-
I was testing the newish Zed-Editor recently. Some slight details still bother be, so I won’t switch completely for now. (File-tree is not movable to the right side, no good grayscale-theme and syntax) It has pretty good Elixir-support, so I’m using it for the Sudoku. It’s a great editor all around.
-
Messing around with a sudoku–solver in Elixir. I haven’t done Elixir in long time, although I really enjoy it. For hobby-projects and experiments I usually do something with graphics or UI, and Elixir is better suited for “headless” programs. I’d love to dive more into Phoenix and LiveView, too.
-
A nice detail in Godot: In the editor-sidebar, a file will appear bluer, the more recently it has been opened, in terms of how many other files have been opened in the meantime.
-
Already got some systems in place, I can move single steps depending on the angle. The Trek-Game handles diagonal movement as one step resource-wise. Godot-UI is pretty nice, but lacking reactive properties. There are some extensions, but I think for my limited amount it should be fine to go the imperative route.
-
Got back to 97/98 kg since April. Started Gym twice per week and increasing proteins. Feeling pretty good right now. Also I go for a 40 min walk every weekday, while listening to an audiobook.
-
Currently doing a modern version of WinTrek, while learning Godot. I played WinTrek on my old PCs back in Windows 3.1 or ME times.
-
Long time no post. I released the Pico-8 Solitaire: www.lexaloffle.com/bbs/
-
Adding Windows 95 UI is always the best idea.
-
Pico-8 is peaceful
-
The Cpp/Raylib-version of the solitaire-game is kinda on hold. No motivation to do card-images. The Pico-8-Version is just for fun, plus it’s easier for the card-art.
subscribe via RSS