Jameson: Snap! for hackers

Hello! I’m PPPDUD, and I’d like to introduce you folks to a project of mine that’s called Jameson.

Jameson (live instance) is a fork of Snap! that adds all sorts of cool features:

  • An addon system that lets you write userscripts for Jameson
  • A Silver theme modeled after early Snap!'s UI
  • Libraries for working with ZIP files, UltraBox tunes, and even immediate-mode GUIs (thanks @codingisfun2831t!)
  • Santa hats all year 'round…
  • And so much more!

Jameson exists because vanilla Snap! was built largely for educational use. This means that while it’s quite powerful as a teaching tool, it’s lacking in quality-of-life features that would make it useful for hobbyists and hackers alike.

And that’s not all! Jameson’s a community project, so we’re always looking for help. You don’t even need to be good at JavaScript! You could write new libraries and addons and submit them to be included in Jameson, you could provide marketing help, or even just provide ideas!

(This post was edited in November 2026 because of changes in Jameson’s project direction. Below is this post as it was on November 6th, the day before the edits were applied.)

Old post

Hello! I’m PPPDUD (I previously used the @KingOfChickens account, but have moved here to prevent confusion). I’m a former Scratch user and current Snap! enthusiast best known for assisting in the development of Crackle and later Sparkle.

I’m here today to tell you about Jameson, which is a fork of Snap! designed to improve extensibility with the help of an integrated addons system (docs). The idea is to consolidate development efforts for other Snap! forks (like @d016’s Split!) into one place and make their features available as optional addons, which are supplied from a built-in addons store and can be sideloaded.

My hope is that by doing this, I can help reduce the amount of “forkcruft” that’s been building up over the years. From watching this category, I’ve noticed that a lot of fork developers simply wish to add a few blocks or redesign existing ones in ways that Snap!'s library system doesn’t fully accomodate for. This is where Jameson’s addon system comes into play.

If someone wants to make heavy modifications to Jameson, instead of needing to develop a separate fork and deal with the associated maintenance (particularly when you stop developing and end up diverging from upstream in ways that are painful to resolve), they can simply write a Jameson addon. Addons that are likely to be used by others and follow Jameson’s contribution policies can be introduced into the Jameson addons store and become available to tons of users who wouldn’t otherwise notice.

For fork developers, merging with Jameson gives them a larger userbase and a free account with my Nova Code Forgejo instance (which is neccessary for submitting changes, as I am banned from GitHub). As an added bonus, I periodically monitor Snap!'s development and I tend to pull from upstream pretty frequently, so your users won’t have to wait forever to receive updates.

@niki650 @theaysnap You two seem to be interested in forking Snap!. Would you like to merge with Jameson? I would be especially interested to see that fancy sound reporter displaying that you folks have come up with integrated into Jameson.

@d016 Your username with Nova Code is d016 and your password is your Snap! username followed by “isthebest” with no spaces, encoded in Base 64. (I’m not going to paste it here so that I make life harder for attackers, but Forgejo will prompt you to change it after the fact.)

Your email is d016@example.com since you didn’t provide one. (This doesn’t need to be a real email, it’s just what Forgejo uses on your profile and optionally your Git commits.)

P.S. Since my trust level is pretty low right now, I can’t post more than 1 reply in the same topic, so I had to move here. Sorry about that.

done!

Awesome! Welcome to Nova Code! I’ve gone ahead and added you to the Jameson team at mojavesoft.

@codingisfun2831t I realize that we’ve had our fair share of differences, but would you like to help out too?


@alessandrito123 Would you like to merge Snavanced! with Jameson?

Something I’m worried about this whole Jameson thing is cross-compatability with the addon mod things. How do I load a Snavanced Project if I only have the Asterisk plugin, and how will Split! render the new input and block shapes?

In Jameson, I’m trying to keep all of the primitives in extensions.js and only use addons for UI changes and whatnot, so that projects will be compatible with Jameson by default. Addons for merged forks would be for user-visible changes, like with Split!. As for the new input and block shapes, that’s a good question. I suppose that you and the Asterisk devs could probably collaborate on porting their stuff to the Split! addon, and in the meantime we could leave that part out of the merger.

Yeah, that’s what I thought for Split! Integration.

Thanks for the info!

Also, I guess Jameson would have a way for custom blocks to appear alongside primatives, right? Just to make things look nicer when importing things like Asterisk

Do you mean blocks introduced by an addon or blocks built by the user?

blocks by an addon, I meant

What merging do you mean? Merging Nexus! with Jamseon?

I would like if Snavanced! was updated in the first place, eh, no at the first moment, I am still busy with my university training and also Snavanced! has many bugs (even it is developed for older computers) and I have splitted it almost a year before in my local computer without knowing about it until today. So, it would be problematic if I bring the merging right now, so it will be done many after. I am so sorry. :(

Ehh.. I just don’t thinking having just another fork that happens to have the add-ons and nothing else not the best. One big thing is that you HAVE to update it whenever a new Snap! version comes out. But with a extension or bookmarklet or JS function block, most of the function should carry over (Snap! doesn’t change its API that much). It also allows anyone who may have GitHub blocked to just use the JS function block which should be useable no matter what.

apparently jameson is hosted on pppdud’s mojavesoft.org domain, so I don’t think github blocking should be an issue. Plus, since everything is an addon, it shouldn’t be that hard to transfer the foundation of jameson over to a new snap version

:(

what does “categorized as Parked” even mean???

Anyways, I see the issue now. perhaps jameson will function like a userscript on top of snap? (like what I want for split)

Jameson 3.0 does more than just addons. It also includes extra primitives and more libraries. The addons are just a nice addition. (This is as opposed to Jameson 2.0, which was built entirely around addons.)

What is “it” in this context? The fork or addons?

What??? This has nothing to do with GitHub, and in fact Jameson 3.0’s addon store is actually bundled with the IDE, so it fetches from whoever’s hosting it (not a Git forge) and the addons are guaranteed to work properly with that setup.

P.S. Sorry for the slow response. Snap!'s forums use the most noob-hostile security mechanisms known to man, and one of them is aggressively ratelimiting comments apparently.

^^^

No, it’s a Snap! fork. But I sync it with upstream regularly, so it’s almost never out of date.

The fork.

As in, use the addon loader without mojavesoft.org being blocked for whatever reason. However the fact that the add-ons themselves might ALSO be blocked is worrying.