rmrichesjr wrote:It seems to me that having the data local on your own machines should solve the security issue (if you manage your machines properly). Why then would you want it hosted on somebody else's machines?
It wouldn't make any sense to me to build this as a web app AND host the data locally. The point of a web a is so that I can access my information from any internet connected computer anytime I want. If the data is stored locally I can only access my data from my computer. Hosting the data locally would be used if the app is a desktop app.rmrichesjr wrote:It seems to me that having the data local on your own machines should solve the security issue (if you manage your machines properly). Why then would you want it hosted on somebody else's machines?
Unfortunately, I think most people would advocate what they are most familiar with. I think you should stay with a solid, portable, industry tested technology like PHP or Java.nimebe wrote:If building it as a web app what language would we use? I only advocate PHP, mySQL, because it's what I'm used to. PHP lends itself nicely to integrate Java Script, XML, AJAX an other technologies of which I am not so familiar. I'm open to learning new technologies so I'm wondering what everyone is thinking of as far as the technologies most appropriate to accomplish the objectives for this project?
I don't know if there is an official policy but based upon this question and answer on the Web site, I would not hold my breath.nimebe wrote:Tom, what's the church's policy on wifi's in the building? I'm only half serious. The tech half says yes the other half just furrows its brow.
The scriptural text and footnotes are there, just need to figure out the file format and come up with a more powerful viewer.rmrichesjr wrote:If the Church's CD-ROM-based product would work...
Great, I'll go to source forge and try to get added to the project. Thanks!thegordo wrote:For those interested in helping to develop this project, I have started a source forge project called Scripture Study Plus. It took almost a full week to get approved. When the Copyright and permissions office is open, I seem to forget to call about the concerns i have with potential copyright issues. I will post here the results of that call once I make it and get an answer as to what exactly we can do.
And from the SourceForge project site:thegordo wrote:In order to use it offline I would have to get the Churches permission to store the HTML stripped files locally since the material is copyrighted. I'm not sure if that would happen. If they didn't allow it, the project might as well be an online only thing - if we can take the files and store them locally, we could make both offline and online, at least after an initial setup of getting all of the scripture text from the website online.
It looks like you are leaning toward the online only thing. However, with a little processing of the text on the front end, the same viewer could be used for both the lds.org version and the CD version.This Software helps study the Scriptures and other online materials that are found available through http://www.lds.org