Hi all!
I was very excited when I recieved this email about the new codebase. I've
been using care since the early 2000s and have done an improved appointment
module (fit for a callcenter), Rheumatology EMR and a couple of
administrative reports, and I also telephony integration.
I think the new code base is a great idea, and I would like to know if
there is any kind of architectural document of the whole project.
In my opinion, we should this document should be the first deliverable for
the new project, this will not only keep us who want to contribute
codewise to the project aligned with the vision of the product everybody
had, but it also will help with responsability assignment and schedule
tracking.
I would say we need at least a class diagram, some sequence diagrams (so
the class diagram is validated) and all the use cases we can come up with.
I also believe that we should not only consider ZF2, but we should also
bring an ORM into the project, so we can have a truly database agnostic
application (and it also helps keep the code cleaner, with less sql lying
around). In my experience there are only two decent ORMs for PHP, Doctrine
and Propel. Of these, Doctrine is the most widely used with ZF2.
Please let me know when the google hangout is going to be, I'm definitely
in.
David S.
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
_______________________________________________
Care2002-developers mailing list
Care2002-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/care2002-developers
