I've been given the task of customizing one of our existing Palm apps for a specific customer's needs. Since these modifications won't be shipped to our general customer base, I'd like to know how best to implement these changes.
Can I put these specific changes into a library (shared or static) that can be "turned on" by those who purchase the add'l functionality (including new forms and extended data structures)? Should I branch the app and create a separate product? (This approach would seem to be the least desirable, since it would require maintaining multiple products when core functionality changed.) Or build the changes into the original app and turn them on by the user when purchased? Thank you! -Mike -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
