hi M. long time no see :)

quick replies ...
when we talked about zend ,we ment zend framework..not the guard
product...
http://framework.zend.com/

regarding the translation...
there are things easier than using google documents, in the following
weeks we
are gonna put it online..and you are welcome to make your suggestions..

regarding modularity..zf 1.10 has a perfect support for modules..
as per distributing them we thought of using PEAR channels...

regarding the db tables..
you're completely right..in the second the module specific tables
and the core ones will show up ...

btw...we have some key positions in which your help would be
most valuable.. and you are welcome :)

gj.

On 01/05/2010 20:07, plasticdoc wrote:
> On 01-05-2010 10:41, Gjergj Sheldija wrote:
>   
>> me and robert are doing lately some changes in the source code that will
>> ( hopefully ) lead at having a modular version someway around
>> dec 2010 - jan 2011 based on zend framework.
>>    
>>     
> Care2x is an HIS supporting SW environment.
>
> Any HIS, because it stores real human health data has associated:
>   - morbility (someone may get hurt in consequence of a bug in the code, 
> or in the greneral workflow of the sw package)
>   - mortality (someone may die because of such non-intended software 
> effects).
> As such the usefulness of a HIS supporting SW results manly from keeping 
> it SIMPLE and SECURE.
>
> I do not want to start one of those endless "my baby is betters than 
> yours" discussions about the better way to support HIS software.
> But Zend is neither simple, nor has it been proved to be safe in 
> supporting Health IT SW in its many years of existence (and of several 
> aborted tentatives of making it support real life Health IT SW).
>
> Some souls may be tempted by Zend's claim described at: < 
> http://www.zend.com/en/products/guard/>, mainly "protects your 
> applications from reverse engineering and unauthorized customization by 
> providing encoding and obfuscation.  It further protects from unlicensed 
> use and redistribution by providing comprehensive licensing support."
>
>   
>> 1. ease the translation documentation of care2x
>>      a. move the current translation handling to gettext and create a
>>      web based translation tool ( gj )
>>      b. move the help files to a wiki based system,
>>    
>>     
> OpenEMR, a fellow open source HIS SW , has achieved this with simplicity 
> using the free google Docs/Groups framework < 
> http://www.openmedsoftware.org/wiki/OpenEMR_Internationalization_Development>.
> It uses the free Google framework and Google translation service.
> Suddenly, there is every language to every user, the work to do becomes 
> to round up the semantics.
>
>   
>> ) ( r )
>> 2. start moving files around in an mvc fashion
>>      a. create a simple mvc fw to ease the transformation of c2x from the
>> current
>>      structure to the new mvc one ( volunteers ? )
>> 3. start the final move to zend framework ( volunteers ? )
>>    
>>     
> And Gjergj, we have already talked about this, do try to reduce the 
> number of needed tables: keep it simple and secure
>
>   
>> for the other phases we'd welcome any suggestions...
>>    
>>     
> I have read somewhere in this mailing list that it is being considered 
> to move the project's page into Drupal CMS .
> That would be a major improvement.
> But while being at it, did you noticed the similarities between a 
> properly done and supported CMS like Drupal and a a good HIS supporting 
> SW package?
> Have you noticed how the Drupal framework easily and transparently 
> supports different DBMS like MySQl, PostgreSQL and others?
> Have you noticed how Drupal framework easily supports user created 
> modules? And how easy it is to install any module (by just copying the 
> code snippets into Drupal and click update)?
> Have you noticed how easily Drupal keeps a close eye on its code and on 
> the LAMP environment, keeping you informed about problems and 
> recommending the appropriate upgrades?
>
> Best regards,
>
> M.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Care2002-developers mailing list
> Care2002-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/care2002-developers
>   

------------------------------------------------------------------------------
_______________________________________________
Care2002-developers mailing list
Care2002-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/care2002-developers

Reply via email to