Oh wow this is cute as hell and looks cute as hell!
Millie Squilly
Creator of
Recent community posts
EX5 time! Last issue of the EX series! https://zine.milliesquilly.com/ex/ex5.html

Hi,
So basically what you'll need is some code to change the palette when you go to that specific card, and change it back when you leave. This could be done in the button code or in the "on view" of the card. The "all about color" deck does have a bit of example code for doing this on the palette transitions page.
My palettefade module may be handy too, although it's primarily designed for doing fancy fade in/out transitions it does have some helpful utility functions for changing the palette. Hopefully should all be in the documentation but I'll try to go over some examples here.
So if you're using palettefade and you've added the module to your deck, you can get the current palette as a list of 16 integers by running pf.currentpalette[deck] in the Listener. Generally I'll take the output of that and make them like global constants e.g. in the deck-level script I'll have palette1:(16777215,16776960,16737536.... and so on for the various palettes I have.
Then when I want to change to a certain palette I'll use pf.setpalettte[deck palette1] and that'll change the palette. So I can have that in my "change to a new card" button or just in the "on view" so that however you got to the card it'll be at the correct palette.
If you want to get fancy then you could use the blackdip function in palettefade, that does a nice smooth fade to black and then fades up with the new palette, e.g. pf.blackdip[deck card2 30 palette2]. Or you can do something with transitions like in the all about colour deck example.
I hope at least some of this makes sense. Let me know if you're getting stuck though.
Basically, when your drawing mode is set to "color" then images will import in colour, using the nearest colour in the palette. If the drawing mode is set to black and white (which is the default) images import in black and white, dithered. Often the best results however for colour image importing is using an external tool to dither to the desired palette before importing. The "All About Color" deck has a lot of details about how this works and what you can do with it! https://beyondloom.com/decker/color.html
In terms of iPad OS, I don't think there's a version of Decker that runs natively for it - the builds on the itch page are targeted towards desktop Windows and MacOS (or Linux users can build from source). If you're using an iPad or an Android tablet then you are basically stuck with the web app. The web and native versions are pretty much feature-identical for what it's worth.
The menus basically just use the "menu" font built into Decker. It is possible to edit this font or the other built-in fonts (using for example the editor in the example fonts.deck) and these changes will be saved along with the deck.
If you've got a separate Decker font and want to use it to replace the default fonts, I'd assume this is possible somehow but I'm not sure the best way to do it.
Although if it's eyestrain that's the issue, it could be worth looking into changing the palette instead?
If you have a widget on the same card you can just access it by name
So like if you have a field called field1 you can just use field1.text or whatever you need.
If a widget is on a different card (e.g. card1) you can access it like card1.widgets.field1.text for example.
You may want to check the Decker reference manual in the "Interfaces" section where it lists all the different properties of each widget type.
Hope this answers your question :)
I realise it's not exactly a solution, but have you tried recording sound separately (in like Audacity for example) and then importing into Decker? I've found even when the audio editor is working I get better results this way since I can adjust the levels and such in Audacity before converting down into Decker's format
Sorry, took me a while to get to this but I think the loading times aren't too bad, as IJ said it's not much compared to other in-browser game engines.
The full-colour dithered art style does tend result in decks being on the bigger size in my experience. It sounds like you're on the right track in terms of keeping the size down though - basically, avoiding duplicating the same backgrounds is what should help the best. So using canvas widgets to add elements without having to duplicate the rest of the background, or enabling/disabling buttons depending on what interactions you should be able to do and such.
So when you make a new card in Decker, it's a totally new blank card, without anything on it.
If you're wanting multiple copies of the wigglypaint drawing card, then what you might need to do is make a copy of the blank wigglypaint card and then paste that in, using the copy card / paste card feature.
But if you're just looking at saving your wigglypaint drawings, depending where you're planning on using them, one thing you can do is make a copy of the wiggly canvas widget (i.e. going into widget mode) and then that can be pasted into a new card or a different deck or what have you.
I hope this makes sense? It might help to know what your end goal is with where you're using the drawings.
Yeah, Decker can definitely chug a bit with larger file sizes. I don't think there's a hard limit necessarily, but there's definitely a practical limit. With my own work I'd ended up with an almost 200mb deck that REALLY chugged when you saved it and wouldn't even load properly in a web browser, so I had to downscale some of the assets, and then at around 60mb it would at least load in a browser.
I think the pertinent question would be, what are you doing that the file size is so big? I've noticed the bigger Decker decks tend to be from using a LOT of imported dithered art, and unless you're being silly like me and essentially doing FMV, often what tends to make the filesize balloon out like this is having multiple copies of the same card with slight differences, the problem being that each copy has to be saved in full in the deck. Could it be possible to rework things so that instead of different cards you're showing/hiding different widgets?
Quick answer for your first question: If you've got a .deck with a font saved (e.g. if you save a copy of the font editor), you should be able to drag it onto the deck you want the font in (like literally drag the file into an open Decker window), and then use the Font/DA mover that pops up to move the new font into your deck. The same goes for moving around different colour palettes, sounds, contraptions, or modules, when you get that far.
Looking at your second point, yes I think that should work - it's pretty easy to write code that hides or shows a widget based on a click
Hey, I saw you put out an update that looks like it removed a lot of the material, but also added a bunch of other decks, that I should remind you, you're not crediting the creators of and likely haven't asked permission. That's really not cool.
I think it's fine if you want to archive decks you find for personal use, although keeping them as separate files may be a better idea since that way they won't break and any deck-level code won't conflict. But it's not a good idea to distribute them like this.
Hey, so it looks like you're basically just bundling up various other decks into one. What raises an eyebrow for me is that the credits don't actually, well, credit any of the people whose decks you've borrowed from. Which seems a bit uncool
It's a bit unclear what the purpose is. Some of these tools don't really make sense accessed through this sort of interface. Like, PublicTransit (which is an out-of-date version here) isn't particularly useful as a tool that you'd access through a menu like this, the point is more to use the transitions in your own work. And Data Pipes is really more of a proof of concept rather than a tool, I'd say. And including the WigglyKit library is, again, odd, since that's more of a component for someone's own decks rather than a tool in its own right. Ditto for the fonts preview, there's not much benefit in just viewing them.
Additionally, it seems that a lot of the tools have broken when they were copied into your deck. Valentine-er doesn't seem to actually generate the card in the end. I'm guessing there were some bits you didn't copy or maybe the card arrangement made things messy? The link to data pipes doesn't even go to the right place, it goes to the spirograph card! Before asking other people to test, it might be a good idea to test yourself.
I'm not really sure what you're trying to achieve here. You're basically bundling together broken and outdated tools in a context that doesn't really make sense. I feel like it would make more sense, if you want access to various decker resources, to link to the live versions from the original creators rather than haphazardly bundling a bunch of cards together in a broken fashion.
Edit: I feel I should also point out that a couple of the art pieces included in the valentine-er app are ones I made, and like I gave IJ permission to use them in valentine-er but I don't seem to recall being asked by you if you could include them here so that's really not cool tbh.
I've been working on a launcher for this written in Decker. Thanks to some of the newer danger zone decker features I've managed to get something working. It looks something like this, the buttons lead you into a directory listing all the decks in a certain folder where you can launch them from.

I've whacked it up on github if you'd like to poke around. As a note, this is pretty specific to my setup and will require a custom danger build of native decker to work, so getting it going for your own purposes may take some effort but hopefully it can inspire some other works. https://github.com/micpp42/deck-kiosk-launcher/
There's a few things I can probably still do with it, like listing the names of decks a bit friendlier or patching in a nicer quit function (for now I've just got my desktop environment set up to auto-relaunch decker after you alt-f4 it) or some solution to hardcoding in the folder names to make it easier to add stuff but for an initial version I'm pretty happy with this.
Edit: there's a quick video of it in action on social media: https://bsky.app/profile/milliesquilly.com/post/3maxln5s5nk2i
here is the blog post in question https://milliesquilly.com/deck-kiosk-mostly-done-at-least-hardware-wise/


























