Sprig of Yew in falling snow that I captured on a dangerously cold day
At long last, and after tons of not quite boilerplate, but tedious code, I have added the ability to Visions VTT to both create a new character and edit Candela Obscura characters.
Boy howdy this is tricky, but the use of reducers greatly reduced the amount of boilerplate mess. Thanks to @Two9A from the #React community for the advice to go that direction.
I'll be recording a demo video introducing my VTT tomorrow.
There's #ratatui #dioxus #yew #leptos and so on and so forth...
You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).
Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.
Or a view that I can embed to have a full WYSIWYG editor?
For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.
Early this week, I had a live stream in which I explained drag-and-drop within a web page, and I wrote two Yew components which can turn almost anything into a draggable item, or into a droppable target.
After several days of unraveling a lot of mess within the GM view of Visions VTT, I've finally been able to merge those two components! Here is how you implement such components in Yew:
In this evening's episode of Coding Together, I'm going to change pattern from my normal exploratory coding to something more structured.
Today I'm going to build out Yew components that can turn other components into Drag Sources and Drop Targets. This evening I will use these components as examples of how to build components with Yew.
If you are not familiar, Yew is nearly identical to React, but designed for the Rust programming language instead of Typescript. Lessons here will generally translate to React. Come join me if you are a beginner to React or want to learn more about using Rust to program for the web.
Handmade Yew pendant with Eihwaz rune on the backside. I love yew wood, with it's beautiful dark core :)
This pendant is for sale, 24.50 euros excluding shipment, PM me if you are interested or find it in my (Dutch) webshop https://suzannespirit.nl/winkel/handgemaakte-sieraden-en-hangers-kopen/taxus-ketting-hanger-eihwaz-rune/
#handmade #crafts #pendant #eihwaz #yew #jewelry #runes #seidr #forsale #pagan
Yew (Taxus baccata), traditionally used for making longbows and suicides.
The entire plant is highly toxic except for the red fruit (but don't eat the seed inside).
A yew can grow quite large (15m diameter) and very old (1600 years).
#rust developers, have any of you ever built automated tests, headless browser tests, for components in a WASM application?
In my case, it's a #yew application and I'm trying to write my first component test for it. The documentation is a bit scattered, and I'm not sure exactly what I should be following. But what I do have is this command:
```
wasm-pack test --headless --firefox
```
My webdriver.json looks like this:
```
{
"moz:firefoxOptions": {
"prefs": {
"media.navigator.streams.fake": true,
"media.navigator.permission.disabled": true
},
"args": []
}
}
```
And I have wasm-bindgen-test 0.3 in my dev-dependencies.
The overall output is very long and I don't really know much of what I'm looking at, but this is a screenshot of a salient area where I think the error is occurring. My main issue, though, is that I don't know what I'm doing because I've never put together this particular group of technologies.
Do any of you have any advice or know somebody who might?