Hi Robert,
the wiki has some database problems. Even I cannot write new articles there.
We are trying to fix the problem. I just hope it does not require us to
re-install the
whole thing.
Thanks for the notice.
Elpidio
On 5/7/07, Robert Meggle <[EMAIL PROTECTED]> wrote:
Hello Daniele,
As long I'm working fort his project I saw sometimes really the need of
rewriting whole modules. I saw the quite nice ideas from the beginning and
that some parts got a kind of uncontrolled growth like in each other
sector
of OSS.
But care2x is not so bad at all, it is a great opportunity! I think it is
a
good idea to look forward for this project and foster the development to
the
next generation of a fertile HIS for everyone everywhere. Care2x must be
adaptable for each requirement and we have to think about who is willing
of
using it.
When I look back to the development customaries we did for East Africa and
the quite big resonance that there is really the need for we should focus
for that. But care2x has some rated break points and it is covered in your
small summary.
When we look just to your first requirement idea of building compatibility
to PHP > 5 there is quite a lot of work to be done.
> - Use of Php version >= 5
What is the main reason for our headache here? It is that PHP has changed
it
to real OOP what was sloppy done in previous PHP versions (4.whatever).
There was the way of OOP but just on the basis and not having
accessibility
modifiers like public (it was the default and no other way), protected and
private. Similar to the implementation of interfaces (GUI or database
abstraction layer) these rules are really purely for the convenience of
the
programmer?
IMHO we should focus the later versions of PHP and following higher level
of
OOP. To specify the visibility of our class members brings more safety by
protecting it from "outside" influence.
So when we start here from scratch we should bring a real, clear
structured
API to the object model. In my vision there should be a way for users to
implement their own requirements based on the object model and there is no
need for uncontrolled growth.
> - Use of some kind of development framework (for example Zend Framework)
... A nice consistent Framework, and easily rollout web, gui, and back end
applications all using the same framework.... that is our aim, yes? :-)
To have a framework is a quite good idea but for security aspects we
should
take care that there is no lack in security issues and to make sure that
there will no lack given. And it fits to eclipse.
So IMHO: Yes, I ACK with 100% for such framework for rel. 3.
> - Modularity: we need a small core which can be easily extended with
> modules
> and plugins. All modules must follow the same behaviour and must have
the
> same way to access the core functionalities
That would be no problem when there is a valid object model, a proper used
framework and disciplined programmers :-)
> - Database indipendence
That is always the old story. The current version tries it to cover that
requirement with adodb what is a quite good way. But the way how it is
used
and to cover all these cases what makes quite a lot of work for
developers.
Also for me, I do not have here e.g. a Oracle database running and cannot
test it. Then all these "slangs" and interpretations of SQL makes this
line
quite interesting.
So when there is a quite interesting abstract class for sql queries what
could translate to the used database, as it is solved in the current
class_core, then it would be an interesting method for such an solution.
What's funny for the current project: According to the current used object
model a person is a "core". That's somehow funny when OOP should describe
a
case like in nature.
IMHO to set up a new intelligent object model there is a brainstorm
needed.
Out of it there should be painted to an UML model that we have a quite
nice
idea to build it new. When we are planning it in such a way of rewriting
it
completely new, we should make it better as it currently is.
> - Common rules in writing the code
> - Better documentation
> - More and better comments in the code
We have rules, we have a way of documentation and there is always the
possibility to comment each line of code. Best documentation is given by
Elpidio, later developments done by others has quite a lack of
documentations. Also, blame on me, I'm not the best documentaries writer;
it
is mostly some small words but not such an excellent API description done
by
Elpidio in the beginning.
Be the way, I have here from time to time quite interesting studies done
by
myself or cooperating companies. But there was no way of adding new topics
in the current wiki.
So for me: When there are new concepts, new ideas what makes sense, then
it
would be a nice challenge. But it is quite a lot of work to be done and
this
is not easy. But for me... I'm doing my best to use, propagate and
contribute to open source projects. For me this is a great opportunity to
do
so in a very challenging international setting.
Just as an additionally idea: How about the idea when we're more focus on
PHP with AJAX? So no use of browser's back button or history, just an
empty
window what looks like an application. Barrier free it could also prepared
for smaller clients like pda's and just optimized data transmissions...
just
as an idea to introduce the idea of web 2.0 to this workout :-)
Robert
P.S. By the way, please check the current wiki pages. There is a strange
"Can't open file: 'c2x21objectcache.MYI'".. :-)
> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] [mailto:care2002-
> [EMAIL PROTECTED] Im Auftrag von Daniele Palmas
> Gesendet: Sonntag, 6. Mai 2007 22:06
> An: care2002-developers@lists.sourceforge.net
> Betreff: Re: [Care2002-developers]Building 3th Generation of care2x EMR
-
> roadmap to version 3.0
>
> Dear all,
>
> for the 3th generation of Care2x I suggest a total rewrite because it is
> easy
> to start from a new version that to patch the old version. In my
opinion,
> from a technical point of view, these are some requirements that have to
> be
> achieved in order to have a professional software:
>
> - Use of Php version >= 5
> - Use of some kind of development framework (for example Zend Framework)
> - Modularity: we need a small core which can be easily extended with
> modules
> and plugins. All modules must follow the same behaviour and must have
the
> same way to access the core functionalities
> - Database indipendence
> - Common rules in writing the code
> - Better documentation
> - More and better comments in the code
>
> Regards,
> Daniele Palmas
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Care2002-developers mailing list
> Care2002-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/care2002-developers
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Care2002-developers mailing list
Care2002-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/care2002-developers
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Care2002-developers mailing list
Care2002-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/care2002-developers
