[CS-FSLUG] Church Management Software

[EnzoAeneas]

no not at all. We have control over the version of everything we use.
Besides, if we simply adapt pre-existing software for most
functionality, we are simply providing glue code.

But you are not wrong at all. Just perspective different from mine.
We can go that direction to simplify initial implementation, and
maintain a separate codebase for other ideas.
Both could be maintained. In either case, we need to plan well and
keep all of our end users in mind.
I appreciate that you have been doing that through my techno ranting :-)

Kevin

On Wed, Apr 9, 2008 at 12:21 AM, Fred A. Miller <fmiller at lightlink.com> wrote:
> EnzoAeneas wrote:
>  > My previously mentioned approach doesn't require internet access at all
>  > Everything runs locally. And can be contained and control by the
>  > application as parts of it.
>  > The end user never has to deal with it. I would upgrade the same as OO.
>
>  Isn't there a decent change of a problem when you add too many "layers,"
>  that is a combo of apps. when one gets updated and doesn't want to play
>  nice with something else? I'm just suggesting we take a long hard look
>  at how complex we make this. MOST of the people who are going to use it
>  AREN'T very 'puter literate nor have anyone in the church who is......as
>  many of us have said here already. That's why I like the idea of a
>  single app. or suite.
>
>  Maybe I'm wrong..........just adding food for thought.
>
>  --
>
>
> Fred  "Molon Labe"
>
>  A: Because it messes up the order in which people normally read text.
>  Q: Why is top-posting such a bad thing?
>
>  _______________________________________________
>  ChristianSource FSLUG mailing list
>  Christiansource at ofb.biz
>  http://cs.uninetsolutions.com
>