Someday. Someday, when I have found a way to fit 18 hours of class, 10 hours of programming, and 12 hours of sleep into a single day, you may see a real, downloadable Mac 3D app here. This is not vaporware: it actually exists, in the form of about 10,000 lines of buggy C++, with an equal quantity remaining to be written. Right now, I'm still working of the preliminaries to coolness (multithreading; tight, reliable, quick graphics routines; UI standardization; platform independence), while occasionally indulging myself and writing one of the really cool things we all dream about programming (like a little, functional 'net app).
My girlfriend is an avid writer, and enjoys corrosponding with fellow
writers via the internet with her world-builders newsgroup. The problem
is, however, that she doesn't have a computer. Luckily I the boyfriend
came to the rescue with...
It's small, it's fast, and best of all, it runs on the Mac 128K I had lying around.
It's a shockingly simple program which does nothing other than turn the printer port of your Mac/PowerMac into a VT100 terminal, perfectly suited for surfing the 'net. Best of all, it's free. You can get the source code of the guts of the emulator.
Encryption has been a fascination of mine lately, and hence I wrote
a 30K app that runs in 35K of memory which can password-encrypt 250K of
data per second on my Mac IIsi. It's also accellerated for PowerMac (heck,
it only added 8K to the file- why not), but since I don't have a PowerMac,
I can't test it out. I'd appriciate it if you'd download it, because it's
quick, secure, and in need of PowerMac testing. So just click here if you'd
like to download...
And don't worry-- it's not "guiltware" (shareware); it's "reputationware". It's only a 30K download, so please take it. Instructions: drag a file or files to the encryptor. Let go.
You can check out the body of the encryption code (C++) by following this link. See: it's secure enough that I'll publish the algorithm. I'd appriciate your comments, suggestions, etc. on this code, and may incorporate any changes into the next version. I'd particularly like to hear about security holes (the remainder of the program is not directly encryption-related: it deals with reading in the dropped file or files piece-by-piece and writing out the data).