Just to address each of these so far:
- Background music: v1.3 introduces basic support for looped background audio. I have some ideas for making this more general/flexible in the future, but it may take some time to get the design right.
- Adjustable contrast settings for imported images: This is potentially complex, but it could be useful; I'll consider adding something like this eventually. In the meantime, you can use external tools to prepare images before import.
- Pop-up windows: The alert[] function can provide several types of modal dialog already- plain alerts, prompts for the user to enter text, etc. It is also possible to make your own modal-like functionality with scripting, by dynamically adding canvases or other widgets to cards. There are many possible variations/requirements, so this would be a great area for multiple people to explore with Modules (see below).
- More stroke styles: There's no technical barrier to adding more brush types, though it would require some UI redesigns. I consider this very low-priority.
- More fill styles: adding more pattern types to Decker is not as straightforward. It is possible, however, to customize the patterns used in a given deck via scripts, and even import customized palettes into other decks via the Font/DA mover. Making a "pattern editor" tool similar to the font editor example might be a fun project.
- GIF support: I might someday provide a way to display an animated GIF on a card without writing any code. In the nearer term, I may at least generalize read[] to be able to import the individual frames of an animated GIF, which could make it much easier for people to set up animations via scripting. (As well as other interesting possibilities.)
- Palette support: If you consult the documentation for the patterns interface, you will see that Decker secretly has a 16-color palette which can be used via scripting. The size of the palette is fixed, but like the 1-bit patterns, the colors themselves are also customizable on the fly via scripts. For example, try this in the listener:
patterns[colors.white]:"%h" parse "000000" patterns[colors.black]:"%h" parse "FFAA00"
- A Textbox: I have no idea what this suggestion means. Field widgets can already be multiline, with optional scrollbars, rich text, and code-editing features.
- Multi Card Display: This sounds tricky. If you aren't already aware, you can use the cursor keys on your keyboard as a fast way of flipping through cards.
- Snippets: It's a great idea for the community to share and collect useful script snippets. If code is reused frequently, you might benefit from Modules. You can import a module into your deck from another deck just like a font or a sound, and they can bundle together handy utility functions. I've released several example decks with modules, including Plot, a module that draws charts and graphs, and the "Rect" module included in All About Draggable.
