I think eclipse is the first class example of how current and future application should function. It consists of of a few low level modules/plugins/libraries and a very clear way of how to write plugins for it. Each plugin publishes the functionality it can/wants to share with other in an plugin.XML, a visa versa. Each plugin attaching itself to the functionalties of other plugins should state in it's plugin.xml what functionality he wants to benefit from(or listen to), and a pointer to it's own source-code that reacts on these functions. I have even started a few months back to create a HIS based on eclipse which should consist of a lot of plugins. [patient-plugin, labo-plugin, billing-plugin, ...] But doing it on my own would take me ages, And secondly it was a Client-Server program. I prefer to work on a web-based HIS. All this to say that building a flexible application should indeed focus on providing a framework allowing different plugins to interact together.
And as to the statement of Elpidio about to much API to study. I personally don't think that working with a lot of plugins puts so much burden on the developers. Developers using plugins are not interested in the internals of a single or multiple plugins. They just have to take a look at each plugin's public API/listeners, and only attach to the things they are interested in. And indeed if they would start listening to 13 other modules it would be much more work than working on 3 modules. Put that would definitely also be the case in the current setup. You can expect to make a more evolved module with the same amount of knowledge/study as for a simple non-interacting module. >From what i have seen the plugins that have currently been developed [are usefull >though] do not seem to interact with the HIS-data. my 2 cents Roel > > Subject: Re: Fwd: Re: [Care2002-developers] Comparing Care2x to other > EPR/HIS/GP - 1 > Date: Tue, 8 Jun 2004 09:20:10 +1000 > From: Horst Herb <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > > On Tue, 08 Jun 2004 16:00, Elpidio Latorilla wrote: > > It seems to me that OSCAR is more directed towards doctors and the > > processing of medical findings, Care2x is more directed towards hospital > > organisation and management of departments, requests and staff. > > > > Ideally, one had the best of both system united in one system ! > > UNIX is so more powerful *and* robust because it is built on a large number > of small programs that each do one job very well, but can interact nicely > with all others - instead of depending on unwieldy and unflexible monoliths. > > I don't envision one application that is everything to everybody. I envision > a modular environment where OSCAR's appointment module can interact freely > and efficiently with Care2x' lab module and gnumed's prescribing module and > .... so forth. > > We really should each focus on designing a small module with a well defined > scope, implement it well, and publish a platform/language independent RPC API > for it. If we could work out a common *framework* in which such independent > modules can exist and cooperate efficiently (and pain free for the > developers), we would well deserve our place in the history of health > informatics. > > Horst ===== God invented SCO to give people a company to hate more than Microsoft. ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
