To be honest, this day wasn't a very productive regarding Crystal Kingdom. I wanted to take a little break and had other things that needed to be done.
Tomorrow, however, I will continue making Crystal Kingdom with renewed energy, tons of stuff needs to be done. :)
If you would like to support Crystal Kingdom, please consider liking its facebook page and following it on twitter.
Yesterday's update can be found here.
In a case of any questions or suggestions, don't hesitate to contact me here or on twitter. ;)
Just some more server plumbing stuff on NodeJS.
Javascript has been pissing me off lately been contemplating some stuff using c modules to do the heavy lifting.
Though I'm not sure how much of a bitch it is to get NodeJS to play nice with those.
I lost a bit of my streak there eh?
Yesterday, I got 'else/else if' cases compiling properly. Today I started on implementing the 'loop' keyword, which will essentially act as a 'foreach' for looping over an array or allow counted iterations, ie. 'loop 2' will render the layout items twice.
Before I can do something like 'loop $Posts as $Post', I decided to implement simple echoing of backend variables in the layout, which is done much like Silverstripe, simply with '$Varname'.
I've also got a side project to this, which is a mobile-touch editor for Game Maker rooms. This editor will be built into the GM code and auto-read objects to place so you might see a few posts about that too.
Went through and added TODO markers for all incomplete words. Made stubs for several subroutines. Implemented MUL & DIVMOD as well as untested >CFA & INTERPRET.
I think I mentioned this before, but the one thing I dislike about MSP430 assembly is the lack of multiplication & division mnenomics. That said, the naive multiply function is trivial:
/* Arguments are passed in r12 & r13, r15 is used to store the result */ clr r15 1: add r12, r15 /* ignores overflow */ dec r13 jnz 1b /* To comply with the MSP430 GCC calling convension, the result would be put back into r12 */
Division is a bit more complicated, but still didn't seem too bad. I'm not posting that because I haven't done any verification of it yet. This one at least had minimal testing in isolation.