>On the technical part use JSP (or whatever) modules which do the whole stuff > for you, e.g. template systems which only get the content to merge it into a > static layout. This helps a lot, because other people which are better than > you in HTML design can make the pages and you fill in the content with your > scripts.
I have only mildly been watching this thread, but to date it seems like almost all conversation has focused on the 'client'. I would like to interject that the backend should be done in something that is very portable and available to a lot of paid hosting solutions. If you want lots of people to propogate this work, you will need to construct it in a way that is accessible for them to install and make available to their user base. I assume that fulfilling the great commission is the goal and so getting something like this in hands of as many willing to host as possible is optimal? If this is merely a web interface for crosswire.org site, then of course the backend doesnt matter one bit. Just food for thought. (I only mention because at one time JavaServerPages was used for SWORD stuff) while its good stuff, it isnt highly available to the masses that would host stuff like this, in the way C, Perl, PHP and such are. -- Derek Neighbors <[EMAIL PROTECTED]> GNU Enterprise
signature.asc
Description: This is a digitally signed message part