شكراً ليك كتير على الرسالة ..
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging
Hi Tim,
> I wasn't thinking of a one man development team, but one man leading it.
>
Basically that kind of project management is often used in OSS sector.
And yes, HIS or MRS is a quite complex part of software and we have to
think in that way but not impossible.
> My experience in open sourc
Hi Tim,
well, yes and no. there are simple things that can be decided by one man.
and the template engine is one of those, plus other small things.
but when it comes to deciding the namespaces or the overall db desing or
the architecture, well this is - at least as i think it - collegial
decision.
Hi Gjergj,
I wasn't thinking of a one man development team, but one man leading it.
My experience in open source projects is that when you have a community
discussion you get a wide variety of ideas. Often complete opposites.
Try starting a discussion on what templating engine should be used. Y
Hi Tim, Mark,
you have grasped exactly my ideas.
i'd like to point something here. although the one-man-dictatorship
concept my produce more uniform code, it's only - in my opinion -
suitable for small things - cms and such.
when you start to think on all the requirements a functional
his system h
Mark Alan wrote:
> Gjergj Sheldija wrote:
>
>> this is exactly my idea.
>>
>
> Healthcare Information Systems (HIS) are complex systems.
>
> The software used to support HIS tends to also get complex.
>
> Some proven ways to deal with complexity are:
> - code modularity;
> - dropping non
Tim Schofield wrote:
> Gjergj Sheldija wrote:
>
>
>> as you see the decision cannot be taken from one person alone...
>>
>>
>
> Whilst that is true, if too many people are involved a decision will
> never be made. Sometimes a dictatorship is the best form of government :-)
>
>
complet
Gjergj Sheldija wrote:
> as you see the decision cannot be taken from one person alone...
>
Whilst that is true, if too many people are involved a decision will
never be made. Sometimes a dictatorship is the best form of government :-)
Tim
Gjergj Sheldija wrote:
> this is exactly my idea.
Healthcare Information Systems (HIS) are complex systems.
The software used to support HIS tends to also get complex.
Some proven ways to deal with complexity are:
- code modularity;
- dropping non core code from the core application (for instanc
Hi Tim,
this is exactly my idea.
but this is going to be a decision that only all of us can make together.
just an example for the modules, how are they going to be installed and
managed ?
via xml files ? via db tables ? module repositories something like
JSR-170 ?
this is just one of the simpl
Hi Gjergj,
I think one of the problems c2x has is that there has been a
fragmentation of the project. There seems actually to be many different
versions of c2x, in different countries. Maybe it should be redesigned
in a manner that enables support of these different versions around a
central p
شكراً ليك كتير على الرسالة ..
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging
شكراً ليك كتير على الرسالة ..
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging
Hi Mark,
the article is very interesting,
but i think that c2x now has some more urgent needs.
some of them i've tried to describe in the last mail. some others i
hoped that will come
along a discussion in the mailing list, but since no one replied it made
me think that
no one is interested anym
14 matches
Mail list logo
