There is a page that will have the acronyms that are used, though since I don't know if that is up yet, API means Application Program Interface. It short it is a set of routines that are provided to the public to interface with a program. In the terms of a website, the routines are usually GET or POST data that the program will send to the server. The results are usually returned as an XML file.

An example let us say there was a website that had an API to find anyone.You would connect to the server with your program and send

eldercurtis wrote:Could someone define API for me. I guess I have an idea of what it is by visiting the website references left by cboyack. However, I would like to know what it stands for exactly. Thank you.

From Wikipedia article:[INDENT]"An application programming interface (API) is a source code interface that a computer system or program library provides in order to support requests for services to be made of it by a computer program."[/INDENT]Tom

JamesAnderson wrote:I like the side-by-side languages idea, and not just English/Spanish, but like German/French too. That way, not only could one learn the language, but missionaries that know they are going to learn a language other than their own, and not just from English to whatever, can actually familiarize themselves wth what is in the Triple.

With the Church growing in languages other than English, and the distinct possibility that we will have missionaries learning languages other than English that speak natively languages other than English, this could prove invaluable to them.

The LDS Scriptures CD does exactly that ... I love it. It seems that the same application could be extended to the web paradigm as well, making it available to a much wider audience.

It would be nice to see an API come out that supportedJSON, along with an XML option . . .

I have been using JSON in my projects and love thatit is so easy to process via javascript! Not to mentionhow lite it is. I had been having serious issues processingXML in a timely fashion that I doubt I could ever go back.

For those looking for a Scripture application idea, take a look at Elder David A. Bednar's talk at the Feb 4th CES fireside. Scroll down a little over half way until you find the paragraph that starts with "If you promise not to laugh, I will tell you about one of the simple ways I search for scriptural themes."

It certainly sounds like a idea ripe for implementation electronically rather then colored pencils and scissors.

RussellHltn wrote:For those looking for a Scripture application idea, take a look at Elder David A. Bednar's talk at the Feb 4th CES fireside. Scroll down a little over half way until you find the paragraph that starts with "If you promise not to laugh, I will tell you about one of the simple ways I search for scriptural themes."

It certainly sounds like a idea ripe for implementation electronically rather then colored pencils and scissors.

That would make for a really neat scripture study experience (especially having the help of an application/website with a well done interface). I imagine it could be just as interactive as doing the paper method Elder Bednar used, but results would be produced much quicker.

I drag and drop type of approach into seperate piles are and auto-cut which just goes after anything you've marked in that color. A verse are a part of the verse. Anyway I think it would be a great idea. Anyone up to making an open source project? (Could be tied into [thread=113]the Scripture Study Program[/thread])

mkmurray wrote:That would make for a really neat scripture study experience

I think it would be neat to allow that on the results of a search. That way you can have the program help you find the passages that you categorize.

I think one of the great advantages to doing it electronically is that each quote maintains it's identity. You won't have to scribble on each slip of paper what book and chapter it came from. It can also maintain it's footnotes and other links.