Over the past year, my photography has seen a dramatic improvement. I just went back to an old post of mine and realized that most of the links were broken because I had deleted them from my deviantART gallery because the pictures did not seem any good to me anymore.

I’m lazy at post processing, so I usually don’t upload a photo until a few months after it was taken; heck, there are still tons of unprocessed shots in my library that I think are worthy for uploading.

But for the finished ones, here are some I am proud of, though as /r/photocritique has shown me, they all have their flaws:

Recommendations

Beginners: Use nxtRICedit.Advanced users:Use nxtRICeditV2, as RICcreator is still under development. Once it’s stable, you should use RICcreator. UPDATE: Use RICcreator; it’s pretty awesome now.

nxtRICeditV3 may or may not come out soon. It is intended to address the bugs in nxtRICeditV2. When it comes out, you can get rid of nxtRICeditV2. (If you decide not to use the awesome RICcreator, that is!)

Sure, you can always MM_get() them, and manually execute the operations, but that’s no fun! :)

Actually, all of this should be hidden behind a “parser” (it’s more like an interpreter), so you won’t have to worry about it at all; you’ll simply call MM_parse() to do all the work for you. You’ll just need to input a string with the code into the function. This is what I’m going for:

As you can see, all the type conversions like long to double are handled “implicitly” (although I’ll add explicit functionality too, of course). All the memory allocation/operations/etc are handled for you, as if you were programming in NXC… inside NXC. You’ll be able to integrate your code into itself (does that make any sense?). I may also add support for a compiler directive (MM_PARSE_SYSTEM) which will allow you to execute “system commands” like NumOut() inside the parser.

If you’re worried about all that typing, you can always use #defines to make the function names shorter: