Duh. It's an application with a different file extension. Not that big of a deal.
[ 4/08/2004 05:38:48 PM ] [ ]
Wednesday, April 07, 2004
Struct vs. Class: Class wins?
I have a simple data structure for storing geospatial information, just 4 numbers. Latitude, longitude, altitude, and time. Simple, right? It would be way, way overkill to use an full on class to do this, so I implemented a nice little C struct to do it: typedef struct _TrackPoint { double latitude; /* Latitude */ double longitude; /* Longitude */ double altitude; /* Altitude */ double time; /* Time */ } TrackPoint; typedef TrackPoint *TrackPointPointer; typedef TrackPoint *TrackPointArray;
Of course, it's objective-c I'm using this data structure with. Apple does this all the time, treating structs like NSPoint and NSRect as if they were objects, when they are not. While I have tried to follow the example of Apple and GNUStep in implementing my simple data structure, Xcode isn't allowing me to treat it like it does NSRect. This is annoying the hell out of me. Now I'm going to have to make an object like the above structure, of which I expect to have arrays of hundreds or thousands... that's not cool.
Why can't I just do it as Apple and GNUStep do? I've searched for other examples of structs posing as classes/objects, but no luck. Update Sure, as soon as I post this I find the answer on [CocoaDev], which I had already searched a number of times! [ 4/07/2004 06:54:21 PM ] [ ]
Tuesday, April 06, 2004
Gibberish
Apparently GPSBabel only deals with waypoints on the Garmin, not tracks. What a Forerunner really needs is track support. The thing is, GPSBabel advertises it supports tracks - when in fact it seems to barely support waypoints. When loading anything from the Forerunner it shows protocol errors, and when loading tracks it segfaults right before it should be finishing. Why? It depends on another open source library (JEEPS) for communicating with a Garmin GPS. The JEEPS source hasn't been updated since 2000, which could be a factor. I took a look at another library for talking to Garmin receivers, but it's heavily dependent on IO mechanisms on Linux, not POSIX or BSD. Porting it over to MacOS X would involve a lot more than just pointing it to the correct header files. It would be a major pain.
Yes, I'm working on an application that would support the Forerunner under MacOS X.... shhhhh..... [ 4/06/2004 12:16:26 AM ] [ ]
