Thanks! I'll put my module up on GitHub when it's dev-ready!

Well apparently they both use the same text format, so it should be good.

Unless it's been changed, I don't think the two use the same syntax for most special tokens (L1 for TokenIDE and {L1} for SC3 for example). <shamelessplug>But IES uses TokenIDE syntax out of the box for consistency, and comes with inline sprite editor and stuff</shamelessplug>

Also, this is a nice idea. Something that might be relevant: the Our Projects board is now a bit reorganized with a subboard called Discontinued Projects, which may come in handy (?)

I'd be interested for helping with any computer projects. I still don't know enough about calc programming to assist for calc projects, but I can definitely help for projects written in C/C++, Java, or Python.

My Github: https://github.com/Scipi

I got bored today, so I tried out a different algorithm for moving the snowflakes around in Dodge (our current project).

The main upsides of this new algorithm are that it seems to be faster, all snowflakes move at the same time (which looks neater/more organized), and that it seems to slow down a lot less when the number of snowflakes increases (when handling a lot of them, it 'laggs' a bit when rendering the bottom line, but the movement happens at the same speed).
But the algorithm also has a major downside though: it only works when moving the snowflakes up, not down. It's also a lot slower on a MathPrint OS in MathPrint mode, though it works fine in Classic mode.

Here's a comparization of the new algorithm (left) and the old algorithm (right):


So, should I update the code on GitHub to use this new 'engine'? Or is the change just too big?

For those interested, the source file of the test program using the new algorithm is currently 203 bytes.

I got bored today, so I tried out a different algorithm for moving the snowflakes around in Dodge (our current project).

The main upsides of this new algorithm are that it seems to be faster, all snowflakes move at the same time (which looks neater/more organized), and that it seems to slow down a lot less when the number of snowflakes increases (when handling a lot of them, it 'laggs' a bit when rendering the bottom line, but the movement happens at the same speed).
But the algorithm also has a major downside though: it only works when moving the snowflakes up, not down. It's also a lot slower on a MathPrint OS in MathPrint mode, though it works fine in Classic mode.

Here's a comparization of the new algorithm (left) and the old algorithm (right):


So, should I update the code on GitHub to use this new 'engine'? Or is the change just too big?

For those interested, the source file of the test program using the new algorithm is currently 203 bytes.

Looks a lot nicer! I think we might use a separate file, I'm copying the old one down.

I think it deserves the change!

(though I personally like the different-falling because of confusion
I'm telling T.Wang (the other original author) about the changes

Do you have a GitHub account?

I sent an invite.
Welcome to the team.