Rägnar O'ock

A screenshot of a city builder prototype showing a grid based map with various tiles identified by emojis and decorated by pixel art textures adapting to the type of the surrounding tiles. The backdrop of the map is a dirt texture, tiles have various backgrounds such as grass, water, asphalt and cobblestone. The cobblestone texture stands out from the other textures by its contrasting color and the lining of smaller stones shown on the outside edge of the group of tiles.

A screenshot of a city builder prototype showing the background textures of a grid based map with various tiles decorated by pixel art textures adapting to the type of the surrounding tiles. The backdrop of the map is a dirt texture, tiles have various backgrounds such as grass, water, asphalt and cobblestone. The cobblestone texture stands out from the other textures by its contrasting color and the lining of smaller stones shown on the outside edge of the group of tiles.

A screenshot of a city builder prototype showing the background textures of a grid based map with various tiles decorated by pixel art textures adapting to the type of the surrounding tiles. The backdrop of the map is a dirt texture, tiles have various backgrounds such as grass, water, asphalt and cobblestone. The cobblestone texture stands out from the other textures by its contrasting color and the lining of smaller stones shown on the outside edge of the group of tiles. The game board is tilted slightly away from the camera to make it look like it is placed on a table viewed from the side. Because it's a prototype the edges of the map are clipped in view of the screen making the setup feel bodged together.

I made more textures for the game, it looks a lot better in 3d now too (which is how I hope to make it in the end). And no, there's no canvas for rendering.

That cobblestone texture took me forever to draw and it revealed an issue with how the textures are rendered and I can't unsee it
( è - é )

colon/src/components/dual-cell.vue at 85534c563e8aa0e8f8991fa78c14e26b6a21d35f · Ragnar-Oock/colon A crude recreation of the Colon Catan card game in VueJS, totally a WIP - Ragnar-Oock/colon

As usual the code is available on GitHub :

Perma link : github.com/Ragnar-Oock/...

A screenshot of a grid based city builder where a grass texture fills the space where no tile has been placed yet. The texture transitions cleanly at the edge of placed tiles with a hand drawn dither effect. A code editor window is overlayed on top of the game board showing the code responsible for selecting the right texture for each cell of the grid.

A screenshot of a grid based city builder where a grass texture fills the background where tile has been placed. The texture transitions cleanly at the edge of placed tiles with a hand drawn dither effect. A code editor window is overlayed on top of the game board showing the code responsible for selecting the right texture for each cell of the grid.

One cool trick I discovered with the way I arranged the textures in the atlas is that inverting how the texture is sampled (i.e. having a background where there's a tile vs having a background where there is no tile) is as easy as flipping the check in the sampler

Screenshot of a grid based city builder with somewhat random tile types scattered everywhere to showcase how the background textures connect cleanly when 2 nearby grid cells are filled with a tile. The background texture is a pixel art grass pattern and the tiles at the edges have an artistic feathering to transition between the grass texture and the blank background of the map. The tiles use emojis to illustrate their type. A set of 7 cards lay in an arc at the bottom ready to be placed on the board.

Today I have worked (shortly) on adding textures to my game. Because I'm lazy and didn't want to draw too many textures I used a dual grid to make it possible to have nice looking connected textures.

I wouldn't have thought it to be this easy to implement.

The issue isn't the legacy syntax, it's the rgb(a), hsl or oklch are so much better and intuitive.

(Disclaimer I haven't watched the video yet)

I tried that long ago, now I have over to a hundred tabs open and there's tasks that I have even forgotten about.

Soooo... I've been working on and off on the small game I posted about last time. I've added a bunch of interactivity and, more importantly, actual gameplay in the form of placement constraints and scoring.

I think I'll work on the graphics next...

Try the game here : ragnar-oock.github.io/colon/

GitHub - Ragnar-Oock/colon: A crude recreation of the Colon Catan card game in VueJS, totally a WIP A crude recreation of the Colon Catan card game in VueJS, totally a WIP - Ragnar-Oock/colon

Source code is available on my GitHub, I will update it regularly and I hope to be able to port make it work with xoram.dev once I'm done with the prototyping phase.
github.com/Ragnar-Oock/...

I needed to try something new for a bit, so I decided to make a board game loosely inspired by Colon Catan. So far I have the board, the things that go on it and a way to control which tile can be placed where.

This silly thing is built with Vue and I wouldn't have thought it such a good fit. >>>

a screen shot of a benchmark result showing : - Wrapped function : Operation per second : 48637, average run time: 0.021ms - Function proxy : Operations per second : 49287, average run time: 0.020ms

an in FF it's basically the same (I don't think the difference is significant here)

I got a new job about a month and a half back. And it's both funny and deeply depressing that now that I have 2 "actual experiences" on my CV (yes, I already updated my CV), I get so many more cold calls from recruiters. I went from 2 in 6 months to 8 in 5 weeks.

And I don't like that fact at all

And regarding attending, I'll be at work at that time so no can do sadly.

I'll take that as a no then 😆

CSS Grid Workshop: Friday September 19th at 4pm UTC / 12pm Eastern time / 9am Pacific time

Last week I did a quick live session in my Discord community, and it worked well enough that I've decided to do monthly workshops there.

The first one will be next Friday, with a CSS Grid crash course of sorts.

You can join the community here: discord.gg/bRVypdE9?eve...

so... is there anything about the grid shorthand in it 👀
(no I'll never stop xD)

Me: Technology has peaked, it's only downhill from here. There's no way we can make it better.
Me after looking at the rest of the thread: nevermind...

I use cropped Fullscreen capture when I stream, i feel like it's a lot more versatile than anything else I tried. It would be nice to be able to lock the crop to the size of a given window (so stuff displayed on top would still show) but it never bothered me enough to warrant a fix.

I have a setup like this on my G9 using PowerToys FancyZones. I have it set up with 4 8:9 zones, and fancy zones allow you to snap a window into multiple adjacent zones. So I can have 2 "full-width" windows or a centered full-width surrounded by "half-width" ones with no configuration change.

Unfortunately, standards work may be a function of who has the biggest platform for social media polls (that pre-judge the outcome).

I’m hoping those who work in or near #accessibility can offer some feedback to more fundamental, not pre-judged, questions here:
bsky.app/profile/aard...

#a11y

I personally don't have any issue with IDREFs that would warrant any changes to the spec and seeing valuable contributor time being potentially wasted on it is worrying.

... if this is the element we're looking for".
When the complexity of DOM element linking is not straight up dismissed on the ground of being annoying :/

I just gave a quick read to that GitHub discussion and I understand why you're worried. To me the whole discussion starts from the flawed assumption that IDREFs are at fault but all the propositions I found in the discussion trade the "it's hard to have a unique id value" with "we aren't sure...

- what I like about them? Meh... They're alright...

- what design constraints [...] ? Nothing comes to mind.
- What is the user impact [...] ? From what? Things work ok currently when you stop 5s to think about how to make something work with tools with a good DX like Vue or Svelte.

- For the times I had issues with making something accessible the issue always stemmed from a poor understanding of either the html attributes or aria attributes uses. Never from the IDREF itself.

For example which element should have which attribute (can't remember which one it was sarry)

Vue has useId that guarantees equality between frontend and backend and can be used to get a random opaque value to set as the id where needed.

- I never found myself in a case where a random uuid or a framework provided tool didn't solve the issue.

But I can remember only a single time it made things a bit challenging to do when I was working on a menu and menuitem abstraction layer in Vue.

- Usually when I need to get an id I either use a random uuid in js or a framework provided helper when doing stuff from the backend.

- The only pain point I can think of is not really one honestly, it's the whole page uniqueness. That's a bit tricky to satisfy in some rare situations because the different elements linked by the IDREF are not in the same component.

[1/3]

Asking the questions from this Masto post so you can respond to me here and I’ll carry them over:
eigenmagic.net/@sundress/11...

Think of `<label for="IDREF">` and other places you use an IDREF.

1. What are the specific pain points around using IDs?

#HTML #accessibility #a11y

I use whichever syntax the tool I used to pick the color supports so C... So that means there can be more than one syntax used in the same file.
But if I have to type it out i do comas, with deg and percents.

A form labeled Gender with four options: * Female * Male * Female-to-Male (FTM)/Transgender Male/Trans Man * Male-to-Female (MTF)/Transgender Female/Trans Woman

SIGH