Recent Entries: |
|
|
|
|
|
|
Cross Platform Code for Handheld Devices (Part 1)
|
The first two companies that I worked at out of college were both multimedia game companies where the importance and cost savings of cross platform code were highly stressed. Both of the companies' core business was around "Edutainment" titles for Windows and Macintosh, and I learned a lot about hardware abstraction and many of the ways that C++ allows you to write cross-platform code. (I'll go more into that in a later article.)
There are many, many articles littered around the web about the hows and whys of writing cross-platform code, so I won't go into those here.
Well, both of the companies that I worked for ended up being dot-com-bubble-burst casualties, and my wife was pregnant, so I was forced to join Corporate America. Anyway, I landed a job working for GE Security where they hired me to be their lead PDA developer. This introduced me first to the Palm OS, next WindowsCE, and eventually to Symbian development. Over that time, I became somewhat familiar with the different development communities, and I discovered that the idea of cross-platform code is generally a foreign concept to handheld developers. (The sole exception to that seems to be in game development.)
This brings me to the crux of my post for today which is that I firmly believe that cross-platform is possible in handheld development. From my experience, you need to be willing to invest in a framework abstraction of your core code, but once you have done that, you can quickly get a return on that investment by being able to write application code that can simply be recompiled to a different OS. Of course there is a rigor that needs to be followed by not introducing non-portable code into the application code, but with practice and a solid code base, it is pretty easy to do. To illustrate what/how this might look, I have built a simple Mandelbrot viewer using my framework and compiled it for the Palm OS and for the MS Smartphone platform. You can take a look at the application code here if you want to see how much code we're talking about. Oh, and the binaries are (PalmOS) here and (Smartphone) here. What do you think? Am I nuts? Is this old hat to you? Let me know.
-Jon
|
Submitted by bosshogg on Sunday the 27th of November 2005, at 04:16 pm
|
New WiFi-Where Release With Bug Fixes
|
There is a new release of WiFi-Where that includes the following fixes/features:
1. Fixed the bug that crashes when you try to connect to an AP via WiFi-Where
2. Adjusted the signal strength indicator values to better reflect reality.
3. Changed the functionality of the "Clear" button so that you can either
clear all or clear unsaved AP's.
4. Added different tones for open vs. encrypted networks
5. Changed the AP details screen so that you can edit/change saved names
without having to delete them first.
That's about it. I still have one major feature that I want to add and that's the ability to export AP information in a format that can be uploaded to the major Wardriving sites. However, I'm having trouble figuring out exactly which one I should do. People have pointed me at NetStumbler's format, but that's a binary format and would be hard to get from your Palm to your PC without an SD card. Because of that, I would like to find one that is text only. If you have any knowledge/insight into these, drop me a line.
Oh, and you can get the latest binary here.
-Jon
|
Submitted by bosshogg on Wednesday the 23rd of November 2005, at 09:07 pm
|
|
 
|
|