At 07:15 PM 6/9/2003 +0200, Aaron Ardiri wrote:
> It would be a shame for this utility class to remain private because of a > few bad apples. I would appreciate your input on this issue!
well, my binary of |HaCkMe| is OS5 compliant - all i have to do is release it :) i dont see a reason for this source code to be public at all - why do you want to release it?
I haven't looked at HaCkMe, Aaron, but unless you were also going to release its source code with a free license, it's not the same as what I propose. My intention is a class for developers to compile into their own source code, and not for a binary that end users would execute on a device like HaCkMe would be.
As for why to make the source code public and free, I see two factors:
1) Reusability / maintainability. This class took me a good deal of time to put together and to debug. If other users of this class report bugs in it, I can fix them and make it more stable. Plus, it saves other developers time so that they don't have to reinvent the wheel.
2) Instruction. This DlkUserInfo resource is not documented at all, but I have seen requests on this forum from time to time on how to set or get Hotsync information on the handheld, such as the user name or the hotsync log -- this is all covered by my class. Also, this provides a great, working example of how to deal with the alignment and padding issues of ARM and 68K data, to which users may be referred when they ask such questions (such as myself, about two weeks ago).
use it for yourself, keep it private.
Indeed, but I could also share it with the rest of the developer community to save them time, and to improve the stability of my own code through bug reports. Granted this is a very specific utility that probably won't get much traffic, I still like to think it might help someone.
-Jeff Ishaq
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
