That's pretty neat. Seems to work a lot better with the correct library paths :)
I just thought I'd mention an alternative to putting each component in a shared library- the shared library approach works fine, but i'm worried about portability of dlopen(). You could have a 'main' app, like the current pgOrganizer, and make each module a separate binary. The main app would create a public container that the components could attach to, and you could use pgAppMessage to communicte between the main app and the modules. Just an idea... not sure whether it would work better than the shared lib implementation or not. Keep up the good work! Quoting Carpman <[EMAIL PROTECTED]>: > Right before the PIM sketches came out, I started working on an > organizer program myself. It consists of a framework application that > loads shared object modules for the different organizers (such as a > contacts module, a database module, a todo module, etc...). The two > projects might be compatable. I have a working framework and a couple > of test modules, and so far everything runs without crashing. It's not > > up yet, but I will have a page for it up at > www.voidptr.org/software/pgorganizer.php . Expect the site up sometime > > today. Let me know what you think. > > _______________________________________________ > Pgui-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/pgui-devel > -- Only you can prevent creeping featurism! _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
