I'm developing a commercial-grade common code and user interface library (aptly named Common/UI) and I wouldn't even consider developing the same using Shared Libs. GLib may be unsupported, but it's far more useful (IMO) than the krufty Shared Libs. Several things come to mind:
- Globals. Especially useful when my library handles plugin management, automatic display resizing, and more - all of which require a large number of resident linked lists. - Resources. Resources in a GLib are loaded onto the resouce 'stack' before the application's, thus allowing you to change or make use of fall-through resource requests (common dialogs in the 9000-9999 range, for example). - Simplicity. GLibs require no visible support code on the client application's side. You link against the library, and it works. The error message if the GLib is not loaded could be prettier, though. ;) - Customizability. Changing the stock GLib preloader to, say, check expansion cards (/Palm/Launcher) and load from there should be fairly easy to do. I'll be making this modification, as well as displaying a prettier error dialog if the GLib is not found. Add to that version resource checking, and you're away to the races. - Support. Though not /officially/ supported, GLib libraries are known to work on any version of PalmOS 2.0 (possibly 1.0) and above. Not so with Shared Libs. - "It is extremely easy to convert a static library into a GLib shared library, as well as to link an application to the GLib library." -- http://www.isaac.cs.berkeley.edu/pilot/GLib/GLib.html - GLibs work without host application globals. - No systraps are called to jump to a GLib function. - GLibs help you easily get around 32K-jump problems. There are probably more, but once more I'm witnessing a sunrise from the wrong direction. 'Ning all! - Matthew P.s. if you search the archives you can probably find several posts of mine which contain example GLibs with a very smooth make process. One function per file automatic inclusion in the project, etc. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rodney Smith Sent: Saturday, May 29, 2004 7:33 AM To: Palm Developer Forum Subject: GLib vs Palm OS shared library? What are the pros & cons of using GLib vs a Palm OS shared library? GLib's look great, but I read one line that said they are 'unsupported'. Access to globals in the library is a good benefit. Do any commercial quality apps use GLibs, and should I even be considering it? thx -r -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
