Will you be changing to machine code or assembly language??
No. That would actually make bug fixing & porting KidSafe to other platforms harder.
Some other language?
will you completely re write the program?
Right on both counts!
I'm rewriting KidSafe in C++ to use the raw Windows API.
* Instead of loading an entire framework (the REALbasic framework), KidSafe will only need to load a couple of system DLLs. This should improve RAM usage and shrink the size of the KidSafe executable.
* Instead of needing to have various DLL files, all of KidSafe's internals will be linked directly into KidSafe.exe. No more DLLs.
* REALbasic doesn't have 64-bit support yet, but C++ does. KidSafe should be able to take full advantage of that 64-bit support.
* We're dealing with the raw Windows API, not routing system calls through a framework, so bug finding & fixing should be easier.
It's a pretty big job, especially since it's my first major C++ project, but it's coming reasonably well. Still, it's slow work since I don't have nearly the skill of an experienced C++ programmer. If anybody wants to help with KidSafe's development, I'd be delighted to have the help.
Anyway, I'll post some screenshots in a few days. (Don't be deceived by appearances; most of the screenshots will look like the KidSafe we all know, but most of the under-the-hood stuff is missing. Once I get the GUI fully working, I'll begin the under-the-hood stuff to connect it all together.)