emoji-award-capyhacker
Unable to load image

Calling on @Aevann to Approve MarseyFX!

I am humbly calling upon @MURDERVANN to merge my MarseyFX pull request (it's finished now).

!codecels

FAQ

1. Is it backwards compatible? What about the emotes already posted, will those be broken?

It's mostly backwards compatible. Emotes that have already been posted have already been rendered and as such will not be effected by the new rendering engine. In terms of new posts, emotes are essentially the same, except that you'll need a dot . before modifiers: :marseylove: becomes :marsey.love:

2. What about the preview stuff?

The preview is not up-to-date, so it won't be able to render the new MarseyFX stuff. Options currently are to transpile the MarseyFX parser from Python to JS using something like JavaScripthon; run the python code in the browser through something like PyScript; send the data back to the server in order to be rendered; implement a subset of the renderer in JS; or leave it out entirely.

32
Jump in the discussion.

No email address required.

Is MFX fully backwards compatible? Will :marseyzoomerpatgenocidelove!::marseyzoomerpatgenocidelove!::marseyzoomerpatgenocidelove!: still work?

Jump in the discussion.

No email address required.

It is fully backwards compatible in the sense that existing emotes which have already been posted will continue to work just fine. In terms of new emotes, there is a small change:

:marseyzoomerpatgenocidelove!: becomes :!marseyzoomer.pat.genocide.love:

Jump in the discussion.

No email address required.

but will I still be able to do :marseyzoomerpatgenocidelove!:? if not, then this is a significant breaking change to how people use marseys, which will be a fairly hard sell for Aevann and the rest of the rdrama userbase, especially for a relatively small list of upgrades.

you know, you could always keep the old renderer and only use the new renderer if someone has "."s in the emoji. that wouldn't be too frustrating, imo, and could lead to a gradual, gentle adoption of the new system over time.

Also, you'll probably want to write some documentation on the Formatting help page as well.

Jump in the discussion.

No email address required.

I would have to argue that adding a dot . doesn't constitute a "significant" breaking change, but if le capybara wants it I can have it auto-insert a dot for "legacy" modifiers.

Jump in the discussion.

No email address required.

that would be an okay compromise, but is there really no way to have the old marseys "just work"?

Jump in the discussion.

No email address required.

From the user standpoint, it "just works" -- the dots are auto-inserted when parsing the comment.

Jump in the discussion.

No email address required.

Honestly, the periods are worthless clutter. I don't want to type more to do the same thing.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.