Tom Welch wrote:
I don't have a lot of specifics in mind but here are some very general bullet points.

    * Needs to support both scout tracking with an option to add "Duty
      to God".  I understand that not everyone using this software would
      be a member but if we make this a "plugin" or option in the
      preferences to turn it on, that would be cool.
    * Model the software so it could easily be modified to support
      personal progress.
    * Have an online/offline mode so that people can run it locally but
      optionally synch up to a master repository.
    * optionally have a web interface to the data.

I'm not a major scouting kind of guy so I'm not that familiar with all of the specifics a scouting program should have. From a technology perspective, I was thinking that java would be the way to go.
From a personal perspective, this would be my preference.

We could use the JPF (Java Plug-in Frameowkr found at http://jpf.sourceforge.net) for an arcitecture to allow us to make this system more modular.
I am not seeing where scout tracking would need plug-in capability. Given the fact that the BSA changes advancement requirements periodically, hard-coding advancement criteria would seem to be short-sighted, and my inclination would be to go with a database driven approach.

However, the requirement to support both thin clients and thick clients, would argue in favor of this type of framework.

I've not used this framework so it may not be suitable. For the database, we could use Derby or One$DB. Again, I'm totally open to other ideas here.
I would recommend that we ship with specific, small database, such as the two you refer to, but that as a design principle, we validate that we can easily install and run on one or more of the commercial caliber DB's such as MySQL.

I believe that there needs to be two different discussions. One from a technology perspective (which platform, technology, DB, etc) and then a "Features" discussion (look & feel, type of information to track, etc). I'm in the process of setting up a wiki wherein we could all collaborate on these types of documents. I need another month for this to be complete.
A mailing list may be faster to set up and would free up the bandwidth on this list. Could such a list be set up on the same server as this one?

--
A. Rick Anderson

_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss

Reply via email to