I've just published the source code to a port of Quake to the Android platform. This is something I did a while ago as a internal test application. It's not very useful as a game, because there hasn't been any attempt to optimize the controls for the mobile phone. It's also awkward to install because the end user has to supply the Quake data files on their own. Still, I thought people might enjoy seeing a full-sized example of how to write a native code video game for the Android platform. So there it is, in all its retro glory. (Porting Quake II or Quake III is left as an exercise for the reader. :-)
What's different about this particular port of Quake?
Converted the original application into a DLL
Android applications are written in Java, but they are allowed to call native languge DLLs, and the native language DLLs are allowed to call a limited selection of OS APIs, which include OpenGL ES and Linux File I/O.
I was able to make the game work by using Java for: The Andro…
I frequently switch between Mac and Linux, and it's been troublesome to remember to type Command-whatever on the Mac, but Control-whatever on Linux. (For copy-and paste, for example.) I did a quick web search and found out that it's easy to make Ubuntu Linux recognize the Command keys as an extra set of control keys: Choose menu: System : Preferences : Keyboard Select the Layouts tab Choose "Layout Options" Open the "Alt / Win Key Behaviour" tab Check the "Control is mapped to the Win-keys" checkbox.
This is a BitTorrent client. There are many like it, but this one is mine.-- the BitTorrent Implementer's Creed For fun I've started writing a command-line BitTorrent client in Google's go programming language. The program, Taipei-Torrent , is about 70% done. It can successfully download a torrent, but there are still lots of edge cases to implement. Go routines and channels are a good base for writing multithreaded network code. My design uses goroutines as follows: a single main goroutine contains most of the BitTorrent client logic.each BitTorrent peer is serviced by two goroutines: one to read data from the peer, the other to write data to the peer.a goroutine is used to communicate with the trackersome "time.Tick" goroutines are used to wake the main goroutine up periodically to perform housekeeping duties.All the complicated data structures are owned by the main goroutine. The other goroutines just perform potentially blocking network I/O using channels, netwo…