Hi Andrew,
> Just to add further complexity to the mix, I have been working on a port of
> OIO to Java on Palm OS. The idea is to run a version of OIO on Java first
> on Palm and then perhaps on a Java-based application server (e.g. Enhydra).
Sounds good.
> As I mentioned previously, the essence of these "medical" projects is not
> dependent on the choice of implementation language - as I am certain that
> OIO on Java will most likely not be the last and final implementation of
> OIO. The reason that OIO is doing a port to Java is not because Java is
> "better" than Python/Zope, but rather Zope does not run on Palm and Java
> (ME) does.
>
> Thus, if anyone is interested after reviewing the functions and
> goals/architecture of the OIO AND prefer to code in Java rather than
> Python/Zope, I could really use your help with OIO on Java. As you know, it
> is much easier and productive to implement a system when there is already a
> working prototype.
Be sure I will keep an eye on OIO/FreePM/LittleFish.
Of course I am interested in further exchanging experiences and perhaps work
together somehow. For now I will be busy with working myself into the code.
I guess I have talked much enough for everybody lately ;-)
> David Forslund and I have discussed adding a module to OIO so that OIO can
> interoperate with CORBA components. I really think there is significant
> synergy between our projects. Therefore, we should really take a look at
> what David's group already have and what OIO has. I am sure that in the
> area of CORBA functionalities, OIO should be able to use existing code from
> OpenEMed (even if we are talking about OIO on Zope). On the other hand, the
> user-interface and "plug-and-play" web-forms from the OIO may help
> OpenEMed reach a wider population of users.
True. But I can't judge about that yet as I don't know the code well.
I will always be open for potential reuse of existing stuff but give me
(a lot of) time to get to know the code base of OpenEMed first and OIO later.
--
Kind regards,
Christian
