{"id":58719,"date":"2023-03-25T03:01:39","date_gmt":"2023-03-24T17:01:39","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=58719"},"modified":"2023-03-24T18:43:47","modified_gmt":"2023-03-24T08:43:47","slug":"emoji-sequence-game-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/emoji-sequence-game-primer-tutorial\/","title":{"rendered":"Emoji Sequence Game Primer Tutorial"},"content":{"rendered":"
\"Emoji<\/a>

Emoji Sequence Game Primer Tutorial<\/p><\/div>\n

It’s another layer of cloning happening today with our new “Emoji Sequence Game” on top of the cloning with yesterday’s Number Sequence Game Primer Tutorial<\/a>, but there was a minor improvement to the “middleperson” clone before “Hello<\/font> Dolly<\/a>” appeared!<\/p>\n

We normally involve …<\/p>\n


\nencodeURIComponent()<\/a> ... to encode data on the way out of the originator web application ... before that data reaches the ...
\ndecodeURIComponent()<\/a> ... to decode at the destination web application
\n<\/code><\/p>\n

… in both the clientside wooooorrrrllllddd of Javascript and lots of the time in the serverside wooooorrrrllllddd of a language such as PHP, though our plan to improve, below, takes ideas from PHP base64_encode<\/a> and base64_decode<\/a> (though “atob” is not as good as base64-decode) alternative ideas.<\/p>\n

We don’t use them much but …<\/p>\n


\nbtoa<\/a> ... to encode data (in a base 64 way) on the way out of the originator web application ... before that data reaches the ...
\natob<\/a> ... to decode (in a base 64 way) at the destination web application
\n<\/code><\/p>\n

… has a twofold improvement, to our mind, with that minor improvement to the “middleperson” clone<\/i> work …<\/p>\n