https://tech.churchofjesuschrist.org/wiki/api.php?action=feedcontributions&user=Aebrown&feedformat=atomTechWiki - User contributions [en]2024-03-28T20:13:51ZUser contributionsMediaWiki 1.39.6https://tech.churchofjesuschrist.org/wiki/index.php?title=E-books&diff=71024E-books2015-04-24T17:20:13Z<p>Aebrown: Remove pointless bolding on header cells (style already includes bold)</p>
<hr />
<div>'''E-books''' are electronic formatted text that can be read on devices such as e-readers, tablets, smartphones, and computers. Currently the Church is developing ePub-formatted e-books that can be found at [https://www.lds.org/manual/epub?lang=eng EPUB Manuals] on [https://www.lds.org/?lang=eng LDS.org].<br />
<br />
== Church-supported e-book formats ==<br />
There are many formats for e-books available. The Church is currently supporting three specific formats that cover a wide range of devices; specifically ePub, Mobi, and KF8.<br />
<br />
:{| border="1" cellpadding="3" cellspacing="0"<br />
|+ '''Current e-book formats the Church is looking to create and support'''<br />
! Format <br />
! Devices That Use This Format<br />
|-<br />
|ePub<br />
|B&N Nook, Sony reader, Kobo, iOS devices, Android devices, most smartphones and tablets<br />
|-<br />
|Mobi<br />
|E-Ink Kindles, Kindle Fire <br />
|}<br />
<br />
== New Projects ==<br />
<br />
===New Teachings of Presidents of the Church Manual Coming Soon===<br />
We will be posting ePub and mobi (Kindle format) versions of the Teachings of Presidents of the Church manual for 2014 soon. <br />
<br />
As always, we are looking for testers for these e-books. You will also be able to download these e-books directly from the Amazon Kindle Store, iTunes iBookstore, Kobo eBookstore, Google Play, and Barnes & Noble.<br />
<br />
We ask that you leave your technical feedback [https://docs.google.com/spreadsheet/viewform?formkey=dG5kekZLRkNaV0Y1VHFkQmp2QTNHQ1E6MQ here] to make sure and fix any bugs that might arise.<br />
<br />
===Current 3rd Party Publishing Channels===<br />
*[http://www.amazon.com/s/ref=ntt_athr_dp_sr_1?_encoding=UTF8&field-author=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&search-alias=digital-text&sort=relevancerank Amazon Kindle Store ]<br />
*[https://itunes.apple.com/us/artist/church-jesus-christ-latter/id522965373?mt=11 iTunes iBookstore ]<br />
*[http://store.kobobooks.com/en-US/Search?query=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&fcsearchfield=Author Kobo eBookstore ]<br />
*[https://play.google.com/store/books/author?id=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&hl=en Google Play eBookstore ]<br />
*[http://www.barnesandnoble.com/c/the-church-of-jesus-christ-of-latter-day-saints Barnes & Noble ]<br />
<br />
===Download Links===<br />
*[http://Media.ldscdn.org/epub/lds-scriptures/holy-bible/holy-bible-eng.epub Holy Bible - ePub ]<br />
*[http://Media.ldscdn.org/epub/lds-scriptures/triple-combination/triple-combination-eng.epub Triple Combination - ePub ]<br />
*[http://Media.ldscdn.org/epub/lds-scriptures/book-of-mormon/book-of-mormon-eng.epub Book of Mormon - ePub ]<br />
*[http://Media.ldscdn.org/mobi/lds-scriptures/holy-bible/holy-bible-eng.mobi Holy Bible - Kindle ]<br />
*[http://Media.ldscdn.org/mobi/lds-scriptures/triple-combination/triple-combination-eng.mobi Triple Combination - Kindle ]<br />
*[http://Media.ldscdn.org/mobi/lds-scriptures/book-of-mormon/book-of-mormon-eng.mobi Book of Mormon - Kindle ]<br />
<br />
===Amazon Kindle Store===<br />
*[http://www.amazon.com/Holy-Bible-ebook/dp/B00BMWE99S/ref=sr_1_6?ie=UTF8&qid=1362151173&sr=8-6&keywords=holy+bible+lds+scriptures Holy Bible ]<br />
*[http://www.amazon.com/Mormon-Doctrine-Covenants-Pearl-ebook/dp/B00BMWEEJ8/ref=sr_1_1?s=digital-text&ie=UTF8&qid=1362151383&sr=1-1&keywords=Book+of+Mormon+%7C+Doctrine+and+Covenants+%7C+Pearl+of+Great+Price+lds+scriptures Triple Combination ]<br />
<br />
===iTunes iBookstore===<br />
*[https://itunes.apple.com/us/book/holy-bible/id609027028?ls=1 Holy Bible ]<br />
*[https://itunes.apple.com/us/book/the-book-of-mormon/id609027608?ls=1 Book of Mormon ]<br />
<br />
===Using Calibre to Transfer E-Books to Your Device===<br />
[http://calibre-ebook.com Calibre ] is an excellent free software tool to transfer e-books to your device.<br />
<br />
For Kindle users, *do not use the ePub format, instead use either mobi or Kindle format. Otherwise the conversion from epub to a readable Kindle format will not perfectly render properly.<br />
<br />
E-books are currently only available on [https://www.lds.org/manual/epub?lang=eng LDS.org] and [https://tech.lds.org/wiki/Gospel_Library_for_ePub LDSTech]. We are in the process of creating and publishing more e-books in the three formats listed above.<br />
<br />
:{| border="1" cellpadding="3" cellspacing="0"<br />
! Channels <br />
! eBookstore Links<br />
<br />
|-<br />
|iTunes<br />
|https://itunes.apple.com/us/artist/church-jesus-christ-latter/id522965373?mt=11<br />
<br />
|-<br />
|Amazon<br />
|http://www.amazon.com/s/ref=ntt_athr_dp_sr_1?_encoding=UTF8&field-author=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&search-alias=digital-text&sort=relevancerank<br />
<br />
|-<br />
|Google Play<br />
|https://play.google.com/store/books/author?id=The+Church+of+Jesus+Christ+of+Latter-day+Saints<br />
<br />
|-<br />
|Kobo Bookstore<br />
|http://store.kobobooks.com/en-US/search?query=The%20Church%20of%20Jesus%20Christ%20of%20Latter-day%20Saints&fcsearchfield=Author&fclanguages=all<br />
<br />
|-<br />
|Barnes & Noble<br />
|http://www.barnesandnoble.com/c/the-church-of-jesus-christ-of-latter-day-saints<br />
|}<br />
<br />
<br />
===Cost per download===<br />
There is an associated cost to readers to download e-books from some of these third party stores. Amazon and Barnes & Noble require a minimum of $0.99-$2.99 (depending on the file size) to distribute e-books in their respective stores. E-books in the iTunes iBookstore will be available for free. This is not because we favor one distributor over another, but what the minimum requirements for each store are.<br />
<br />
== New Projects ==<br />
<br />
== E-book Files for Testing ==<br />
<br />
* [http://Media.ldscdn.org/epub/scripture-and-lesson-support/book-of-mormon-teacher-manual/2012-11-00-book-of-mormon-teacher-manual-eng.epub Book of Mormon Teacher Manual]<br />
* [http://Media.ldscdn.org/epub/scripture-and-lesson-support/book-of-mormon-student-manual/2012-11-00-book-of-mormon-student-manual-eng.epub Book of Mormon Student Manual]<br />
* [http://Media.ldscdn.org/epub/lds-manuals/gospel-teaching-and-learning/2012-11-00-gospel-teaching-and-learning-eng.epub Gospel Teaching and Learning]<br />
* [http://Media.ldscdn.org/epub/scripture-and-lesson-support/preach-my-gospel-a-guide-to-missionary-service/2012-18-00-preach-my-gospel-a-guide-to-missionary-service-eng.epub Preach My Gospel]<br />
* [http://Media.ldscdn.org/epub/lds-manuals/teachings-of-the-presidents-of-the-church-lorenzo-snow/2012-06--teachings-of-the-presidents-of-the-church-lorenzon-snow-eng.epub Teachings of the Presidents of the Church: Lorenzo Snow]<br />
<br />
'''Please leave feedback [https://docs.google.com/spreadsheet/viewform?formkey=dG5kekZLRkNaV0Y1VHFkQmp2QTNHQ1E6MQ here].'''<br />
<br />
<br />
[[Category:ePublishing]]<br />
[[Category:e-books]]<br />
[[Category:epub]]<br />
[[Category:mobi]]<br />
[[Category:KF8]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Main_Page&diff=70961Main Page2015-04-10T15:24:25Z<p>Aebrown: Undo revision 70960 by Dauthudvbt2 (talk)</p>
<hr />
<div>{{Other languages/Main Page}}<br />
<div style="margin: 5px 0px 0px 0px;"><br />
<div style="text-align: center;"><br />
==Welcome to the LDSTech Wiki==<br />
</div><br />
<div style="font-size: 1.15em;">The purpose of this wiki is for the Church and community members to collaborate on various documents and technology projects sponsored by the Church. We invite all to participate. '''New users''', please review the [[Community Project Handbook]] for information on getting started, and the [[LDSTech:Guidelines|Wiki guidelines]] for information on editing the wiki.</div><br />
{| width="100%"<br />
<br />
| width=33% align="center" | <br />
<span style="font-size: 1.15em;">'''[[LDSTech | LDSTech Projects]]'''</span><br /><br />
<div class="borderedimage">[[image:ldstechhome.jpg|style="homepageimage"|220px|link=LDSTech]]</div><br />
<br />
| width=33% align="center" | <br />
<span style="font-size: 1.15em;">'''[https://tech.lds.org/wiki/Clerk_Wiki_Redirect Clerks]'''</span><br /><br />
<div class="borderedimage">[[image:clerkshome.jpg|220px|link=https://tech.lds.org/wiki/Clerk_Wiki_Redirect]]</div><br />
<br />
| width=33% align="center" | <br />
<span style="font-size: 1.15em;">'''[[LDS.org applications| LDS.org applications]]'''</span><br /><br />
<div class="borderedimage">[[image:Ldsorgapplications.png|220px|link=LDS.org_applications]]</div><br />
<br />
|-<br />
| width=33% align="center" | <br />
<span style="font-size: 1.15em;">'''[http://mhtech.lds.org Meetinghouse Technology]'''</span><br /><br />
<div class="borderedimage">[[image:mhhome.jpg|220px|link=http://mhtech.lds.org]]</div><br />
<br />
| width=33% align="center" | <br />
<span style="font-size: 1.15em;">'''[[Family_Safety | Internet and Family Safety]]'''</span><br /><br />
<div class="borderedimage">[[image:cybersafetyhome.jpg|style="homepageimage"|220px|link=Family_Safety]]</div><br />
<br />
| width=33% align="center" | <br />
<span style="font-size: 1.15em;">'''[[:Category:LDSTech_Administration|Wiki Administration]]'''</span><br /><br />
<div class="borderedimage">[[Image:ldstech-guidelines.png|style="homepageimage"|220px|link=Category:LDSTech_Administration]]</div><br />
<br />
|-<br />
| width=33% align="center" | <br />
<span style="font-size: 1.15em;">'''[[LDS Java Stack | LDS Java Stack]]'''</span><br /><br />
<div class="borderedimage">[[Image:Lds-java-stack.png|style="homepageimage"|220px|link=LDS Java Stack]]</div><br />
<br />
| width=33% align="center" | <br />
<span style="font-size: 1.15em;">'''[[LDS .NET Stack | LDS .NET Stack]]'''</span><br /><br />
<div class="borderedimage">[[Image:LDS_.NET_Stack.png|style="homepageimage"|220px|link=LDS .NET Stack]]</div><br />
<br />
| width=33% align="center" | <br />
&nbsp;<br />
<br />
|}<br />
<br />
__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
[[Category:Portals]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Gospel_Library_Java_ME_installation_videos&diff=70903Gospel Library Java ME installation videos2015-03-16T17:11:11Z<p>Aebrown: Add category; change external link to wikilink</p>
<hr />
<div>[[Gospel Library for JavaME|Return to Gospel Library for JavaME]].<br />
<br />
Please add appropriate videos here demonstrating other methods of installing the Gospel Library app on feature phones.<br />
<br />
[http://www.youtube.com/watch?v=lax_UEBkdFU Android (Nexus 4) to feature phone (Sony Ericsson w580i) video]<br />
<br />
<br />
== Android to feature phone steps (as transcribed from above video) ==<br />
<br />
'''Step 1.''' (On the Android phone) Do a google search for "gospel library javame download"<br />
<br />
The first result should take you here: https://tech.lds.org/wiki/Gospel_Library_JavaME_download<br />
<br />
'''Step 2.''' Download the jad and the jar. For English: Jad: http://bit.ly/glengjad Jar: http://bit.ly/glengjar<br />
<br />
Some phones require the jad and the jar and other phones only require the jar.<br />
<br />
'''Step 3.''' Turn bluetooth on in the Settings of the Android phone. Make it visible to all nearby bluetooth devices.<br />
<br />
'''Step 4.''' On the feature phone, Under Connectivity, select BlueTooth. Make sure it is turned on.<br />
Go to 'My Devices' Click 'New Device" Click Add <br />
<br />
It will search for the Android phone and when it finds it, select it. <br />
<br />
Enter a passcode on the feature phone and then enter the same passcode on the Android phone. <br />
<br />
'''Step 5.''' On the android phone click on Downloads (look for the Files application), select both the Jad and Jar file. Then click on the dotted line icon that looks like a less than symbol<br />
"<" , then click on Bluetooth, Look for the feature phone in the list on the Android phone and select it.<br />
<br />
'''Step 6.''' On the feature phone, accept the incoming download if prompted to do so. If it says operation failed that is okay, it just means that you don't need that file. <br />
<br />
'''Step 7.''' After it has finished downloading, you can save it to a folder like Applications. <br />
<br />
'''Step 8.''' Launch the application and see if it works.<br />
<br />
[[Category:Gospel Library for JavaME]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Tech.churchofjesuschrist.org&diff=70896Tech.churchofjesuschrist.org2015-03-15T00:22:37Z<p>Aebrown: Previous edit inappropriately included the editor's skills, when the article should contain a general description of skills needed for projects.</p>
<hr />
<div>Any tasks or issues relating to any of the community tools found at tech.lds.org, such as Joomla, Forum, Wiki, Jira, or Subversion.<br />
; '''Summary'''<br />
; Project Manager : Dennis Keating<br />
; Dev Lead : Tim Riker<br />
; Meeting Schedule:<br />
: Mon, Wed, Thurs, Fri. 9:30am-9:45am mst<br />
: Tues, weekly staff meeting 10am-11am via VIDYO<br />
<br />
==Purposes of tech.lds.org==<br />
Many people know of the resources for ward clerks and technology specialists on tech.lds.org. The forum and wiki contain myriad conversations and a knowledge base for technology related ward and stake issues that cannot be found anywhere else. Tech.lds.org is an indispensable resource to those seeking technology support in their demanding and difficult callings.<br />
<br />
Tech.lds.org also serves as an avenue to facilitate community participation in development of Church technology projects. The Church has many technology [[Community_Projects|projects]] to complete to meet the needs of an ever-growing, world-wide church. The Church seeks the help of the tech.lds.org community with this tremendous undertaking.<br />
<br />
==Project Objectives==<br />
The purpose of this project is to continue to improve the '''self-support''' services provided through tech.lds.org. It is also to expand the ability to '''partner''' with the tech.lds.org community on Church technology projects.<br />
<br />
===Self-Support===<br />
The '''forum and wiki''' are the tools for '''self-support''' on the site. The wiki provides a codified knowledge base for officially approved uses and scenarios for Church related technology. In the forum, users can post questions and get answers from other forum users. They can also search previous remarks from users. Problems that aren't answered in the wiki can be researched in the forum.<br />
<br />
===Community Involvement===<br />
The Church invites participants to review the list of [[Community_Projects|projects]] and '''volunteer''' where they have time and inclination.<br />
<br />
==Community Collaboration==<br />
Tech.lds.org provides a collection of tools, held together by glue and sawdust, to enable community collaboration.<br />
<br />
===Issue Tracking===<br />
'''JIRA''' is used to track issues on community projects. After joining a project users will have access to that project in JIRA.<br />
<br />
===Source Control===<br />
Tech.lds.org currently has source control available with Subversion ('''SVN'''). Git support may be added in the near future. Users have access to the source through the project page. Users do not automatically receive commit access to Subversion, but should contact a project manager to obtain access. Users can create JIRA issues and attach patches to those JIRA tickets.<br />
<br />
===Skills Profile===<br />
Users of tech.lds.org can identify which technologies they are comfortable with or interested in learning. This aids project managers in identifying people who will be able to contribute to their project. It is '''not necessary to fill out the skills profile''' to join projects.<br />
<br />
===Projects===<br />
The list of available community projects is visible to those who sign the '''contributor agreement'''. Projects are created by sponsors internal to The Church. Community members can join projects they are interested in and participate at a level they are comfortable with. After joining a project, users will be able to comment on and add JIRA tickets related to that project. They'll also be able to submit patches to the project through JIRA. Volunteers can leave a project at any time.<br />
<br />
====Contributor Agreement====<br />
Those willing to contribute to Church technology projects must sign the '''contributor license agreement''' before they will be able to start.<br />
<br />
===Content Management===<br />
'''Joomla''' is used to manage and maintain the site, the users and the projects.<br />
<br />
===LDSTech Development Virtual Machine===<br />
We have created a VirtualBox Appliance that contains functioning instances of the LDSTech web sites so that developers can get started quickly. There are additional details on the [[LDSTech Development Virtual Machine]] wiki page.<br />
<br />
==Key Information==<br />
===Communication===<br />
<br />
====Weekly Meeting====<br />
An open meeting is held '''weekly on Fridays, 9:30am-9:45am Mountain Time'''.<br />
<br />
'''How to Join:'''<br />
<br />
Our weekly meeting has been moved to [[IRC]]—Channel: #ldstech<br />
Server: freenode.net (for a U.S. Server: chat.us.freenode.net)<br />
<br />
Join using your IRC client, or use the freenode browser interface: http://webchat.freenode.net/<br />
<br />
History of IRC Located: http://infobot.rikers.org/%23ldstech/ https://tech.lds.org/irc/%23ldstech/<br />
<br />
====IRC====<br />
The preferred method of communication regarding all LDSTech projects is in #ldstech channel on irc.freenode.net. [http://colloquy.info/ Colloquy] is a good IRC client for Mac and [http://www.trillian.im/ Trillian] is a good one for PC. See [[IRC]] for more details.<br />
<br />
====Google Groups====<br />
'''Announcement group''' https://groups.google.com/a/tech.lds.org/group/ldstech-announce<br />
<br />
'''Discussion group''' https://groups.google.com/a/tech.lds.org/group/ldstech<br />
<br />
'''Commits group''' https://groups.google.com/a/tech.lds.org/group/ldstech-commits<br />
<br />
===Source code===<br />
The code for tech.lds.org is available:<br><br />
https://code.lds.org/svn/ldstech/trunk.<br />
<br />
===Issue tracking===<br />
Issues, tasks, and bugs can be found in the LDSTech instance:<br><br />
https://tech.lds.org/jira/browse/LDSTECH<br />
<br />
===Test system===<br />
The dev site: http://cdev.lds.org/ldstech/joomla/<br />
<br />
The test site uses [[Coda_Application|CODA]] to provide fake user credentials for testing purposes. http://cdev.lds.org/coda/<br />
<br />
The following users exist and can be used for testing. The password is 'password' for all of them.<br />
<br />
* aaron<br />
* alonzosl<br />
* bruno<br />
* cholder<br />
* ChungBond<br />
* dowdyls<br />
* HarlandBooker<br />
* ian_lees<br />
* JaneDoe<br />
* JaneyDoe<br />
* JimmyDoe<br />
* JohnDoe<br />
* JohnnyDoe<br />
* kaneyb<br />
* KurtBlunt<br />
* luci<br />
* mata<br />
* motleyte<br />
* nonmember<br />
* Octavio<br />
* olmsteadas<br />
* OToole<br />
* pholder<br />
* PorterBadger<br />
* RusselAdam<br />
* vholder<br />
* Бартли<br />
* 逆さ逆さ<br />
* ♠♥♦♣<br />
<br />
===Wireframes===<br />
The old wireframes: https://cdev.lds.org/ldstech/wireframes/<br />
<br />
===Internal Team Members===<br />
* [[user:smootar|Alan Smoot]]<br />
* [[user:timriker|Tim Riker]]<br />
* [[user:ekeating|Elder Dennis Keating]]<br />
<br />
===Release Steps===<br />
* note current release in case we want to role back<br />
* review required sql patches<br />
* confirm regular mysql backups are working<br />
* short news blurb that upgrade is in progress on home and irc<br />
* backup ldstech directory<br />
* svn up<br />
* apply sql patches<br />
* enter and re-save ldap/talentpool/etc modules in administrator if needed<br />
* test joomla, wiki and forum<br />
* remove or update short news blurb and irc topic<br />
* when all tested, remove backup directory<br />
<br />
==Requirements==<br />
* XAMPP - PHP/MySQL Development (or similar) - http://www.apachefriends.org/en/xampp.html<br />
<br />
[[Category:Tech.lds.org]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Gospel_Library_JavaME_download&diff=70892Gospel Library JavaME download2015-03-13T18:22:58Z<p>Aebrown: Change external link to wikilink</p>
<hr />
<div>[[Gospel Library for JavaME|Return to Gospel Library for JavaME]].<br />
<br />
== '''New Beta Download page:''' [http://tech.lds.org/dl/gljme/ http://tech.lds.org/dl/gljme/] ==<br />
<br />
This article explains how to download the [[Mobile Gospel Library]] to a Java ME phone.<br />
<br />
== '''Current Version: Beta 1.0.0''' ==<br />
WARNING: This is a beta version, and may function in an unexpected way on your phone.<br />
<br />
'''For questions and bug reports, please email [mailto:glfp@ldsmail.net glfp@ldsmail.net].'''<br />
<br />
== Download links ==<br />
'''NOTE:''' Some Java ME phones require a JAD/JAR pair. Some require only a JAR file.<br />
<br />
Here are the download links for the appropriate files:<br />
<br />
'''WARNING: BETA VERSION '''<br />
<br />
'''Most popular '''<br />
{|border="1" cellspacing="0" cellpadding="2" <br />
! BETA 1.0.0 !! Gospel Library JAD !! Gospel Library JAR ONLY<br />
|-<br />
| English ||align="center" | '''http://bit.ly/glengjad''' ||align="center" | http://bit.ly/glengjar<br />
|-<br />
| Español (Castellano)||align="center" | '''http://bit.ly/glspajad''' ||align="center" | http://bit.ly/glspajar<br />
|-<br />
| Português ||align="center" | '''http://bit.ly/glporjad''' ||align="center" | http://bit.ly/glporjar<br />
|}<br />
{{-}}<br />
<br />
'''Alphabetical '''<br />
{|border="1" cellspacing="0" cellpadding="2" <br />
! BETA 1.0.0 !! Gospel Library JAD !! Gospel Library JAR ONLY<br />
|-<br />
| Bahasa Indonesia ||align="center" | '''http://bit.ly/glindjad''' ||align="center" | http://bit.ly/glindjar<br />
|-<br />
| Cebuano ||align="center" | '''http://bit.ly/glcebjad''' ||align="center" | http://bit.ly/glcebjar<br />
|-<br />
| Česky ||align="center" | '''http://bit.ly/glcesjad''' ||align="center" | http://bit.ly/glcesjar<br />
|-<br />
| Dansk ||align="center" | '''http://bit.ly/gldanjad''' ||align="center" | http://bit.ly/gldanjar<br />
|-<br />
| Deutsch ||align="center" | '''http://bit.ly/gldeujad''' ||align="center" | http://bit.ly/gldeujar<br />
|-<br />
| Eesti ||align="center" | '''http://bit.ly/glestjad''' ||align="center" | http://bit.ly/glestjar<br />
|-<br />
| English ||align="center" | '''http://bit.ly/glengjad''' ||align="center" | http://bit.ly/glengjar<br />
|-<br />
| Español (Castellano)||align="center" | '''http://bit.ly/glspajad''' ||align="center" | http://bit.ly/glspajar<br />
|-<br />
| Faka-Tonga ||align="center" | '''http://bit.ly/gltonjad''' ||align="center" | http://bit.ly/gltonjar<br />
|-<br />
| Français ||align="center" | '''http://bit.ly/glfrajad''' ||align="center" | http://bit.ly/glfrajar<br />
|-<br />
| Gagana Samoa ||align="center" | '''http://bit.ly/glsmojad''' ||align="center" | http://bit.ly/glsmojar<br />
|-<br />
| Icelandic ||align="center" | '''http://bit.ly/glisljad''' ||align="center" | http://bit.ly/glisljar<br />
|-<br />
| Ilokano ||align="center" | '''http://bit.ly/glilojad''' ||align="center" | http://bit.ly/glilojar<br />
|-<br />
| Italiano ||align="center" | '''http://bit.ly/glitajad''' ||align="center" | http://bit.ly/glitajar<br />
|-<br />
| Kreyòl Ayisyen||align="center" | '''http://bit.ly/glhatjad''' ||align="center" | http://bit.ly/glhatjar<br />
|-<br />
| Magyar ||align="center" | '''http://bit.ly/glhunjad''' ||align="center" | http://bit.ly/glhunjar<br />
|-<br />
| Malagasy ||align="center" | '''http://bit.ly/glmlgjad''' ||align="center" | http://bit.ly/glmlgjar<br />
|-<br />
| Nederlands ||align="center" | '''http://bit.ly/glnldjad''' ||align="center" | http://bit.ly/glnldjar<br />
|-<br />
| Norsk ||align="center" | '''http://bit.ly/glnorjad''' ||align="center" | http://bit.ly/glnorjar<br />
|-<br />
| Português ||align="center" | '''http://bit.ly/glporjad''' ||align="center" | http://bit.ly/glporjar<br />
|-<br />
| Română ||align="center" | '''http://bit.ly/glronjad''' ||align="center" | http://bit.ly/glronjar<br />
|-<br />
| Shqip ||align="center" | '''http://bit.ly/glsqijad''' ||align="center" | http://bit.ly/glsqijar<br />
|-<br />
| Suomi ||align="center" | '''http://bit.ly/glfinjad''' ||align="center" | http://bit.ly/glfinjar<br />
|-<br />
| Svenska ||align="center" | '''http://bit.ly/glswejad''' ||align="center" | http://bit.ly/glswejar<br />
|-<br />
| Tagalog ||align="center" | '''http://bit.ly/gltgljad''' ||align="center" | http://bit.ly/gltgljar<br />
|-<br />
| Tiếng Việt ||align="center" | '''http://bit.ly/glviejad''' ||align="center" | http://bit.ly/glviejar<br />
|-<br />
| Монгол ||align="center" | '''http://bit.ly/glmonjad''' ||align="center" | http://bit.ly/glmonjar<br />
|-<br />
| Русский ||align="center" | '''http://bit.ly/glrusjad''' ||align="center" | http://bit.ly/glrusjar<br />
|-<br />
| Українська ||align="center" | '''http://bit.ly/glukrjad''' ||align="center" | http://bit.ly/glukrjar<br />
|-<br />
| 한국어 ||align="center" | '''http://bit.ly/glkorjad''' ||align="center" | http://bit.ly/glkorjar<br />
|-<br />
| 中文 ||align="center" | '''http://bit.ly/glzhojad''' ||align="center" | http://bit.ly/glzhojar<br />
|-<br />
| 日本語 ||align="center" | '''http://bit.ly/gljpnjad''' ||align="center" | http://bit.ly/gljpnjar<br />
|}<br />
{{-}}<br />
<br />
== Installation ==<br />
To install on your Java ME phone, there are several methods:<br />
* Download directly to your phone using your phone's Internet browser (enter the above link into your phone's browser, and it should install appropriately).<br />
* Download to a PC then copy the files to your phone using Bluetooth. Then find the files in the appropriate folder, and click on them to install.<br />
* Use a custom APP installer that is based on your particular phone.<br />
* Download to a PC then copy the files to your phone using a USB Cable. Then find the files in the appropriate folder, and click on them to install.<br />
* Download to PC then copy files to a micro SD card (micro SD card capable phones). Create kjava directory on the card, copy jar file, and jad file if needed, to card. Insert card in phone, go to app giving access to card directories (may be "My Stuff" or something similar), click on the jar file to install.<br />
<br />
== See also ==<br />
[[Book of Mormon JavaME download]]<br />
<br />
[[Category:JavaME applications]]<br />
__NOTOC__</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=List_of_devices_(Gospel_Library_for_JavaME)&diff=70891List of devices (Gospel Library for JavaME)2015-03-13T18:21:50Z<p>Aebrown: Change external link to wikilink</p>
<hr />
<div>[[Gospel Library for JavaME|Return to Gospel Library for JavaME]].<br />
<br />
== Devices it works on ==<br />
*Samsung S5230N (Book of Mormon only)<br />
* Samsung GT-S3350<br />
*LG GS290<br />
*LG 800G (Book of Mormon JavaME) <br />
*LG 800G w/ 4-gig micro-card installed (both Book of Mormon and full Gospel Library JavaME )<br />
*Pantech Impact P7000 (Both work. Requires SD card and must be installed via Internet, cannot be side-loaded)<br />
*Cingular Sony Ericsson z520a (bluetooth, only jar needed)<br />
*Sony Ericsson 580i<br />
*Sony Ericsson w810<br />
*Nokia X6 (emulation mode)<br />
*Nokia N8 (emulation mode)<br />
*MicroEmulator J2Me Emulator<br />
<br />
(from an email)<br />
<br />
The methods I've used to install the Feature Phone Gospel Library app are:<br />
<br />
1) Bluetooth (the most common), Tracfone LG 420, 430, 440, 620, cingular Sony-Ericsson, AT&T Nokia,<br />
<br />
2) USB file transfer, cingular Sony-Ericsson, AT&T Nokia,<br />
<br />
3) Wi-fi file transfer, cingular Sony-Ericsson, AT&T Nokia.<br />
<br />
== Devices it WON'T work on ==<br />
*Anything from Verizon<br />
*A T-Mobile Samsung phone (need model #)<br />
*So far I can't get a T-Mobile Motorola Renew model W233 to work (no bluetooth) (small chance of working using Web Access, but didn't have data plan to try it) (ojhurst)<br />
<br />
<br />
[[Category:Gospel Library for JavaME]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Device_and_carrier_considerations_(Gospel_Library_for_JavaME)&diff=70890Device and carrier considerations (Gospel Library for JavaME)2015-03-13T18:20:36Z<p>Aebrown: Change external link to wikilink</p>
<hr />
<div>[[Gospel Library for JavaME|Return to Gospel Library for JavaME]].<br />
<br />
== Any carrier ==<br />
<br />
=== Devices ===<br />
<br />
'''Nokia X6-00:''' Bluetooth, USB, Wifi<br />
<br />
'''Sony-Ericsson W810i, , W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Cingular ==<br />
<br />
=== Devices ===<br />
<br />
'''Sony-Ericsson W810i, W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Tracfone, NET10, Total, Straight Talk, SafeLink, Telcel América, Simple Mobile, Page Plus Cellular ==<br />
<br />
Phone must have at least one minute of time remaining. Okay if Service Days have expired. Only the JAR file is needed for installation. When installing, users must "buy" the application, however, as the price is set to zero minutes, no minutes will be deducted from minutes available.<br />
<br />
=== Devices ===<br />
<br />
'''LG 420G, 430G, 440G:''' Bluetooth<br />
<br />
'''LG 620G:''' Bluetooth, USB<br />
<br />
[[Category:Gospel Library for JavaME|Device and Carrier Considerations]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Button_translations_(Gospel_Library_for_JavaME)&diff=70879Button translations (Gospel Library for JavaME)2015-03-11T05:50:11Z<p>Aebrown: More appropriate category</p>
<hr />
<div>Please edit this page and insert the appropriate language translations:<br />
<br />
(the extra rows of English are in there for ease of lining up the other languages. Please leave them in place)<br />
<br />
These are for button titles on the app:<br />
*Select: means to select the currently highlighted option. On some spanish apps, people call this "Ir a" or go to.<br />
*Back: return to the last screen<br />
*Info: Shows the information screen. This has legal information and help contact on it.<br />
*Exit: Close and exit the app<br />
<br />
<br />
{|border="1" cellspacing="0" cellpadding="4" <br />
! Language !! !! !! !!<br />
|-<br />
| '''English''' || Select || Back || Info || Exit<br />
|-<br />
| '''Español''' || Ir a || Volver || Info || Salir<br />
|-<br />
| '''Português''' || Ir para || Voltar || Informações || Deixar<br />
|-<br />
| '''Français''' || Aller à|| Retour || Infos || Laisser<br />
|-<br />
| '''Deutsch''' || Wählen || Zurück || Informationen || Ende<br />
|-<br />
| '''Italiano''' || Selezione|| Ritorno || Info || Esci<br />
|-<br />
| '''Gagana Samoa''' || || || || <br />
|-<br />
| '''Cebuano''' || || || || <br />
|-<br />
| '''English''' || Select || Back || Info || Exit<br />
|-<br />
| '''中文''' || || || || <br />
|-<br />
| '''Bahas Indonesia''' || || || || <br />
|-<br />
| '''日本語''' || || || || <br />
|-<br />
| '''한국어''' || 선택 || 뒤로 || 정보 || 나가기<br />
|-<br />
| '''Монгол''' || || || || <br />
|-<br />
| '''русский''' || || || || <br />
|-<br />
| '''English''' || Select || Back || Info || Exit<br />
|-<br />
| '''Tagalog''' || || || || <br />
|-<br />
| '''Faka-Tonga''' || || || || <br />
|-<br />
| '''Tiếng Việt''' || tuyển trạch || trở lại || Thông tin || ra<br />
|-<br />
| '''English''' || Select || Back || Info || Exit<br />
|}<br />
{{-}}<br />
<br />
== See also ==<br />
[[Book of Mormon JavaME download]]<br />
<br />
[[Category:Gospel Library for JavaME]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Button_translations_(Gospel_Library_for_JavaME)&diff=70877Button translations (Gospel Library for JavaME)2015-03-11T05:49:37Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Button Translations to Button translations (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>Please edit this page and insert the appropriate language translations:<br />
<br />
(the extra rows of English are in there for ease of lining up the other languages. Please leave them in place)<br />
<br />
These are for button titles on the app:<br />
*Select: means to select the currently highlighted option. On some spanish apps, people call this "Ir a" or go to.<br />
*Back: return to the last screen<br />
*Info: Shows the information screen. This has legal information and help contact on it.<br />
*Exit: Close and exit the app<br />
<br />
<br />
{|border="1" cellspacing="0" cellpadding="4" <br />
! Language !! !! !! !!<br />
|-<br />
| '''English''' || Select || Back || Info || Exit<br />
|-<br />
| '''Español''' || Ir a || Volver || Info || Salir<br />
|-<br />
| '''Português''' || Ir para || Voltar || Informações || Deixar<br />
|-<br />
| '''Français''' || Aller à|| Retour || Infos || Laisser<br />
|-<br />
| '''Deutsch''' || Wählen || Zurück || Informationen || Ende<br />
|-<br />
| '''Italiano''' || Selezione|| Ritorno || Info || Esci<br />
|-<br />
| '''Gagana Samoa''' || || || || <br />
|-<br />
| '''Cebuano''' || || || || <br />
|-<br />
| '''English''' || Select || Back || Info || Exit<br />
|-<br />
| '''中文''' || || || || <br />
|-<br />
| '''Bahas Indonesia''' || || || || <br />
|-<br />
| '''日本語''' || || || || <br />
|-<br />
| '''한국어''' || 선택 || 뒤로 || 정보 || 나가기<br />
|-<br />
| '''Монгол''' || || || || <br />
|-<br />
| '''русский''' || || || || <br />
|-<br />
| '''English''' || Select || Back || Info || Exit<br />
|-<br />
| '''Tagalog''' || || || || <br />
|-<br />
| '''Faka-Tonga''' || || || || <br />
|-<br />
| '''Tiếng Việt''' || tuyển trạch || trở lại || Thông tin || ra<br />
|-<br />
| '''English''' || Select || Back || Info || Exit<br />
|}<br />
{{-}}<br />
<br />
== See also ==<br />
[[Book of Mormon JavaME download]]<br />
<br />
[[Category:JavaME applications]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Talk:UI_text_translation_(Gospel_Library_for_JavaME)&diff=70875Talk:UI text translation (Gospel Library for JavaME)2015-03-11T05:47:07Z<p>Aebrown: Aebrown moved page Talk:Gospel Library for JavaME: UI Text Translation to Talk:UI text translation (Gospel Library for JavaME): st</p>
<hr />
<div>German translation of 'Sel' and 'Clr' must have four letters or it does not make sense. --[[User:Sanktsimon|Sanktsimon]] 19:22, 29 September 2011 (UTC)</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=UI_text_translation_(Gospel_Library_for_JavaME)&diff=70873UI text translation (Gospel Library for JavaME)2015-03-11T05:47:07Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: UI Text Translation to UI text translation (Gospel Library for JavaME): st</p>
<hr />
<div>__NOTOC__<br />
{{GLJMEDevLinks}}<br />
We need your help in translating some text for menus. If you can help, please jump in and help to translate the following phrases.<br />
<br />
{|border="1" cellspacing="0" cellpadding="2"<br />
! !! [[#Select| Select]]|| [[#Sel| Sel]] !! [[#Clr| Clr]] !! [[#OK| OK]] !! [[#Font_Size| Font Size]] !! [[#Font_Style| Font Style]] !! [[#Colors| Colors]] !! [[#Next_Book| Next Book]] !! [[#Previous_Book| Previous Book]] !! [[#Next_Chapter| Next Chapter]] !! [[#Pg_Up| Pg Up]] !! [[#Pg_Down| Pg Down]] <br />
|-<br />
| Español (Castellano)|| || || || OK || Tamaño de texto || Estilo de Texto || Colores || Libro Siguiente || Libro Anterior || Capitulo Siguiente || Pag Arriba || Pag Abajo<br />
|-<br />
| Português|| || || || || || || || || || || ||<br />
|-<br />
| Français || Choisir || Chr || Dfr = Défaire or Anl = Annuler || OK || Taille du Texte || Style du Texte || Couleurs || Livre Suivant || Livre Précédent || Chapitre Suivant || Pg Préc || Pg Suiv<br />
|-<br />
| Deutsch || Auswählen || Wähl || Entf || OK || Schriftgröße || Schriftart || Farben || nächstes Buch || Buch zurück || nächstes Kapitel || S. hoch || S. runter<br />
|-<br />
| Italiano || || || || || || || || || || || ||<br />
|-<br />
| Swedish || Välj || Val || ??? || OK || Textstorlek || Textstil || Färger || Nästa bok || Föregående bok || Nästa kapitel || Sid upp || Sid ned<br />
|-<br />
| Tagalog || || || || || || || || || || || ||<br />
|-<br />
| || || || || || || || || || || || ||<br />
|-<br />
| || || || || || || || || || || || ||<br />
|}<br />
{{-}}<br />
<br />
== Context for Text ==<br />
<br />
=== Select ===<br />
This is used to label a button as being able to select an option.<br />
<br />
=== Sel ===<br />
This is used to label a button as being able to select an option. But needs to be a three letter or smaller abbreviation<br />
<br />
=== Clr ===<br />
This is used to label a button that clears or takes back actions. Needs to be a three letter or smaller abbreviation<br />
<br />
=== OK ===<br />
This is used to label a button for users to press to indicate agreement. Needs to be three letter or smaller abbreviation<br />
<br />
=== Font Size ===<br />
User will select this from a series of menu options.<br />
<br />
=== Font Style ===<br />
User will select this from a series of menu options.<br />
<br />
=== Colors ===<br />
User will select this from a series of menu options. It will lead to a list displaying different color schemes for text display.<br />
<br />
=== Next Book ===<br />
This is used to label a button. When pressed, user will be taken to the next book in the Book of Mormon (for example-- moving from Mosiah to Alma)<br />
<br />
=== Previous Book ===<br />
This is used to label a button. When pressed, user will be taken to the previous book in the Book of Mormon (for example--moving from Alma to Mosiah)<br />
<br />
=== Next Chapter ===<br />
This is used to label a button. When pressed, user will be taken to the next chapter (for example--moving from Alma 4 to Alma 5)<br />
<br />
=== Previous Chapter ===<br />
This is used to label a button. When pressed, user will be taken to the previous chapter (for example--moving from Alma 5 to Alma 4)<br />
<br />
=== Pg Up ===<br />
'''Page Up:''' This is used to label a button. When pressed, user will be moved up one page's worth of text. It should be as small as possible, and can be abbreviated.<br />
<br />
=== Pg Down ===<br />
'''Page Down:''' This is used to label a button. When pressed, user will be moved down one page's worth of text. It should be as small as possible, and can be abbreviated.<br />
<br />
[[Category:Translation]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Talk:Hardware_versions_(Gospel_Library_for_JavaME)&diff=70871Talk:Hardware versions (Gospel Library for JavaME)2015-03-11T05:46:16Z<p>Aebrown: Aebrown moved page Talk:Gospel Library for JavaME: Hardware Versions to Talk:Hardware versions (Gospel Library for JavaME)</p>
<hr />
<div>Are you planning to develop the content on this page, or should it be removed? --[[User:Johnsonth|Tom Johnson]] 22:27, 19 March 2012 (UTC)</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Languages_supported_(Gospel_Library_for_JavaME)&diff=70867Languages supported (Gospel Library for JavaME)2015-03-11T05:45:52Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Languages Supported to Languages supported (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>{{GLJMEDevLinks}}<br />
Easy Languages to Support (content in LDSWebml format already):<br />
* English<br />
* Spanish<br />
* Portuguese<br />
* French<br />
* German</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Data_structure_(Gospel_Library_for_JavaME)&diff=70865Data structure (Gospel Library for JavaME)2015-03-11T05:45:28Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Data Structure to Data structure (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>{{GLJMEDevLinks}}<br />
Current anticipated format:<br />
<br />
== Tiny Text Format ==<br />
<br />
Simple separate stripped down XML files that look like this:<br />
<div style="border: 1px dashed black; padding: 10px; margin: 10px; background-color: #FAFBF2"><br />
<source lang="xml"><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<chapter><br />
<head><br />
<tn>Chapter 1</tn><br />
<i/><br />
</head><br />
<body><br />
<h>Abraham seeks the blessings of the patriarchal order—He is persecuted by false priests in <br />
Chaldea—Jehovah saves him—The origins and government of Egypt are reviewed.</h><br />
<v n="1">In the land of the Chaldeans, at the residence of my fathers, I, Abraham, saw that it <br />
was needful for me to obtain another place of residence;</v><br />
<v n="2">And, finding there was greater happiness and peace and rest for me, I sought for the <br />
blessings of the fathers, and the right whereunto I should be ordained to administer the same; <br />
having been myself follower of righteousness, desiring also to be one who possessed great knowledge,<br />
and to be a greater follower of righteousness, and to possess a greater knowledge, and to be a father<br />
of many nations, a prince of peace, and desirin to receive instructions, and to keep the commandments<br />
of God, I became a rightful heir, a High Priest, holding the right belonging to the fathers.</v><br />
</body><br />
</chapter><br />
</source><br />
</div><br />
<br />
== Small Text Format ==<br />
Small XML files that look like this:<br />
<div style="border: 1px dashed black; padding: 10px; margin: 10px; background-color: #FAFBF2"><br />
<source lang="xml"><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<chapter><br />
<head><br />
<tn>Chapter 1</tn><br />
<i/><br />
</head><br />
<body><br />
<h>Abraham seeks the blessings of the patriarchal order—He is persecuted by false priests in<br />
Chaldea—Jehovah saves him—The origins and government of Egypt are reviewed.</h><br />
<v n="1">In the land of the <n r="a">Chaldeans</n>, at the residence of my fathers, I, <n r="b">Abraham</n>,<br />
saw that it was needful for me to obtain another place of <n r="c">residence</n>;</v><br />
<v n="2">And, finding there was greater <n r="a">happiness</n> and peace and rest for me, I sought for the<br />
blessings of the fathers, and the right whereunto I should be ordained to administer the same; having been <br />
myself a follower of <n r="b">righteousness</n>, desiring also to be one who possessed great <br />
<n r="c">knowledge</n>, and to be a greater follower of righteousness, and to possess a greater knowledge,<br />
and to be a father of many <n r="d">nations</n>, a prince of peace, and <n r="e">desiring</n> to receive<br />
instructions, and to keep the commandments of God, I became a rightful heir, a <n r="f">High Priest</n>,<br />
holding the right belonging to the fathers.</v><br />
</body><br />
<notes><br />
<sn r="1a"><br />
<p><sr b="abr" c="1" v="20" cx="20-30">Abr. 1:20 (2-30)</sr>; <br />
<sr b="abr" c="2" v="4" cx="1,4">2:4 (1, 4)</sr>.</p></sn><br />
<sn r="1b"><br />
<p><sr b="gen" c="11" v="26" cx="10-26">Gen. 11:26 (10-26)</sr>; <br />
<sr b="hel" c="8" v="18" cx="16-19">Hel. 8:18 (16-19)</sr>.</p></sn><br />
<sn r="1c"><br />
<p><sr b="acts" c="7" v="3" cx="2-4">Acts 7:3 (2-4)</sr>.</p></sn><br />
<sn r="2a"><br />
<p><sr b="tg" t="happiness">TG Happiness</sr>; <br />
<sr b="tg" t="priesthood-qualifying-for">Priesthood, Qualifying for</sr>;<br />
<sr b="tg" t="rest">Rest</sr>; <sr b="tg" t="righteousness">Righteousness</sr>.</p></sn><br />
<sn r="2b"><br />
<p><sr b="tg" t="god-the-standard-of-righteousness">TG God, the Standard of Righteousness</sr>.</p></sn><br />
<sn r="2c"><br />
<p><sr b="prov" c="19" v="2">Prov. 19:2</sr>; <sr b="dc" c="42" v="61">D&amp;C 42:61</sr>.</p></sn><br />
<sn r="2d"><br />
<p><sr b="gen" c="12" v="2">Gen. 12:2</sr>; <sr b="gen" c="17" v="6">17:6</sr>; <br />
<sr b="gen" c="18" v="18">18:18</sr>.</p></sn><br />
<sn r="2e"><br />
<p><sr b="gen" c="13" v="4">Gen. 13:4</sr>.</p></sn><br />
<sn r="2f"><br />
<p><sr b="tg" t="high-priest-melchizedek-priesthood">TG High Priest—Melchizedek Priesthood</sr>; <br />
<sr b="tg" t="priesthood-history-of">Priesthood, History of</sr>; <br />
<sr b="tg" t="priesthood-melchizedek">Priesthood, Melchizedek</sr>.</p></sn><br />
</notes><br />
</chapter><br />
</source><br />
</div><br />
<br />
== Tiny TOC Format ==<br />
This will be parsed by the app to obtain a "menu"<br />
<div style="border: 1px dashed black; padding: 10px; margin: 10px; background-color: #FAFBF2"><br />
<source lang="xml"><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<toc l="Pearl of Great Price"><br />
<n l="Introduction" p="1.xml"/><br />
<n l="Moses" p="moses/"><br />
<n l="1" p="moses/1.xml"/><br />
<n l="2" p="moses/2.xml"/><br />
<n l="3" p="moses/3.xml"/><br />
<n l="4" p="moses/4.xml"/><br />
<n l="5" p="moses/5.xml"/><br />
<n l="6" p="moses/6.xml"/><br />
<n l="7" p="moses/7.xml"/><br />
<n l="8" p="moses/8.xml"/><br />
</n><br />
<n l="Abraham" p="abr/"><br />
<n l="1" p="abr/1.xml"/><br />
<n l="2" p="abr/2.xml"/><br />
<n l="3" p="abr/3.xml"/><br />
<n l="4" p="abr/4.xml"/><br />
<n l="5" p="abr/5.xml"/><br />
</n><br />
<n l="Joseph Smith-Matthew" p="js-m/1.xml"/><br />
<n l="Joseph Smith-History" p="js-h/1.xml"/><br />
<n l="Articles of Faith" p="a-of-f/1.xml"/><br />
</toc><br />
</source><br />
</div><br />
<br />
== Small TOC Format ==<br />
This will be parsed by the app to obtain a "menu"<br />
<div style="border: 1px dashed black; padding: 10px; margin: 10px; background-color: #FAFBF2"><br />
<source lang="xml"><br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<toc l="Pearl of Great Price"><br />
<n l="Introduction" p="1.xml"/><br />
<n l="Moses" p="moses/"><br />
<n l="Chapter 1" p="moses/1.xml"/><br />
<n l="Chapter 2" p="moses/2.xml"/><br />
<n l="Chapter 3" p="moses/3.xml"/><br />
<n l="Chapter 4" p="moses/4.xml"/><br />
<n l="Chapter 5" p="moses/5.xml"/><br />
<n l="Chapter 6" p="moses/6.xml"/><br />
<n l="Chapter 7" p="moses/7.xml"/><br />
<n l="Chapter 8" p="moses/8.xml"/><br />
</n><br />
<n l="Abraham" p="abr/"><br />
<n l="Chapter 1" p="abr/1.xml"/><br />
<n l="Chapter 2" p="abr/2.xml"/><br />
<n l="Chapter 3" p="abr/3.xml"/><br />
<n l="Chapter 4" p="abr/4.xml"/><br />
<n l="Chapter 5" p="abr/5.xml"/><br />
</n><br />
<n l="Joseph Smith-Matthew" p="js-m/1.xml"/><br />
<n l="Joseph Smith-History" p="js-h/1.xml"/><br />
<n l="Articles of Faith" p="a-of-f/1.xml"/><br />
</toc><br />
</source><br />
</div></div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=UI_flow_(Gospel_Library_for_JavaME)&diff=70863UI flow (Gospel Library for JavaME)2015-03-11T05:44:51Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: UI Flow to UI flow (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>{{GLJMEDevLinks}}<br />
[[File:BoMFF.png]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Gospel_Library_for_JavaME:_Device_and_Carrier_Considerations&diff=70857Gospel Library for JavaME: Device and Carrier Considerations2015-03-11T05:41:19Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Device and Carrier Considerations to Device and carrier considerations (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>#REDIRECT [[Device and carrier considerations (Gospel Library for JavaME)]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Device_and_carrier_considerations_(Gospel_Library_for_JavaME)&diff=70856Device and carrier considerations (Gospel Library for JavaME)2015-03-11T05:41:19Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Device and Carrier Considerations to Device and carrier considerations (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>== Any carrier ==<br />
<br />
=== Devices ===<br />
<br />
'''Nokia X6-00:''' Bluetooth, USB, Wifi<br />
<br />
'''Sony-Ericsson W810i, , W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Cingular ==<br />
<br />
=== Devices ===<br />
<br />
'''Sony-Ericsson W810i, W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Tracfone, NET10, Total, Straight Talk, SafeLink, Telcel América, Simple Mobile, Page Plus Cellular ==<br />
<br />
Phone must have at least one minute of time remaining. Okay if Service Days have expired. Only the JAR file is needed for installation. When installing, users must "buy" the application, however, as the price is set to zero minutes, no minutes will be deducted from minutes available.<br />
<br />
=== Devices ===<br />
<br />
'''LG 420G, 430G, 440G:''' Bluetooth<br />
<br />
'''LG 620G:''' Bluetooth, USB<br />
<br />
[[Category:Gospel Library for JavaME|Device and Carrier Considerations]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Gospel_Library_for_JavaME&diff=70855Gospel Library for JavaME2015-03-11T05:40:33Z<p>Aebrown: Fix links</p>
<hr />
<div>{{GLJMEDevLinks}}<br />
<br />
== [http://broadcast.lds.org/ICS/techtalk2014/2014-01-10.html LDSTech presentation on this project] == <br />
<br />
<br />
'''New Beta Download page:''' [http://tech.lds.org/dl/gljme/ http://tech.lds.org/dl/gljme/]<br />
<br />
'''Our goal:''' We will make the Book of Mormon accessible to a greater percentage of the world than ever before.<br />
<br />
<br />
Our desire is to have a Book of Mormon Reader app that will be customized to run on any phone, in every language we have translations for, publicly available for download, and available on every cell carrier in the world.<br />
<br />
== TRANSLATION HELP NEEDED!!! ==<br />
<br />
[[Gospel Library for JavaME: Button Translations | Button Translations]]<br />
<br />
[http://youtu.be/9CBkKlt21Co A message from President Ezra Taft Benson]<br />
<br />
== Supported devices ==<br />
[[List of devices (Gospel Library for JavaME)|List of devices]]<br />
<br />
[[Device and carrier considerations (Gospel Library for JavaME)|Device and carrier considerations]]<br />
<br />
== How to Install ==<br />
<br />
=== Downloads ===<br />
* [[Gospel Library Java ME download]]<br />
* [[Book of Mormon Java ME download]]<br />
<br />
=== Installation Instructions ===<br />
<br />
[[What Type of Device is This | How do I know if this is a feature phone?]]<br />
<br />
[[Gospel Library Java ME installation videos | Videos of how to install]]<br />
<br />
Phones that run this app will accept .jar files and may also need a .jad file. The important thing is to copy these files to your device, then select via the phone's menu. This will install the app. The phone will likely query the desired location for the installed app (such as Games or Applications or Other)<br />
<br />
* Downloads the app to your laptop or desktop or internet capable phone<br />
* Copy the app to your feature phone through a bluetooth or using a USB cable<br />
* Find the files via the phone's menu and select them to install.<br />
* Run the apps to check if it properly installed<br />
* scroll through each chapter of the book mormon <br />
* start using app<br />
* Click [https://docs.google.com/spreadsheet/viewform?formkey=dHpCZmVwMkEwbFI2WW5kVFdySFd6YWc6MQ#gid=0 here] to let us know you installed the app<br />
<br />
== Project Information ==<br />
=== Requested skills and experience ===<br />
If you have any experience in making or releasing applications for feature phones (non-smart phones, may be a good description of these phones) then your help would be appreciated. Skills needed include:<br />
<br />
Programming Skills:<br />
* Java (Java ME)<br />
* Symbian<br />
* Brew<br />
<br />
Distribution Skills:<br />
* Knowledge of phone carriers<br />
* Knowledge of phone app download sites<br />
<br />
Testing Skills:<br />
* A mobile feature phone upon which you can put your own apps.<br />
<br />
If you have abilities in the above areas, and are willing to help, please sign up for this [https://tech.lds.org/?option=com_talentpool&controller=projects&view=joinproject&Itemid=39&Projectid=95 project], and send an e-mail to [mailto:h.rushton@ldschurch.org h.rushton@ldschurch.org] with a note on how you would like to help.<br />
<br />
[[Feature Phone App Loading]] (Under Construction -- coming soon)<br />
[[Category:Official LDS Apps]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Gospel_Library_for_JavaME&diff=70854Gospel Library for JavaME2015-03-11T05:38:07Z<p>Aebrown: slight format fix</p>
<hr />
<div>{{GLJMEDevLinks}}<br />
<br />
== [http://broadcast.lds.org/ICS/techtalk2014/2014-01-10.html LDSTech presentation on this project] == <br />
<br />
<br />
'''New Beta Download page:''' [http://tech.lds.org/dl/gljme/ http://tech.lds.org/dl/gljme/]<br />
<br />
'''Our goal:''' We will make the Book of Mormon accessible to a greater percentage of the world than ever before.<br />
<br />
<br />
Our desire is to have a Book of Mormon Reader app that will be customized to run on any phone, in every language we have translations for, publicly available for download, and available on every cell carrier in the world.<br />
<br />
== TRANSLATION HELP NEEDED!!! ==<br />
<br />
[[Gospel Library for JavaME: Button Translations | Button Translations]]<br />
<br />
[http://youtu.be/9CBkKlt21Co A message from President Ezra Taft Benson]<br />
<br />
== Supported devices ==<br />
[[Gospel Library for JavaME: List of Devices | List of devices]]<br />
<br />
[[Gospel Library for JavaME: Device / Carrier Considerations | Device / Carrier Considerations ]]<br />
<br />
== How to Install ==<br />
<br />
=== Downloads ===<br />
* [[Gospel Library Java ME download]]<br />
* [[Book of Mormon Java ME download]]<br />
<br />
=== Installation Instructions ===<br />
<br />
[[What Type of Device is This | How do I know if this is a feature phone?]]<br />
<br />
[[Gospel Library Java ME installation videos | Videos of how to install]]<br />
<br />
Phones that run this app will accept .jar files and may also need a .jad file. The important thing is to copy these files to your device, then select via the phone's menu. This will install the app. The phone will likely query the desired location for the installed app (such as Games or Applications or Other)<br />
<br />
* Downloads the app to your laptop or desktop or internet capable phone<br />
* Copy the app to your feature phone through a bluetooth or using a USB cable<br />
* Find the files via the phone's menu and select them to install.<br />
* Run the apps to check if it properly installed<br />
* scroll through each chapter of the book mormon <br />
* start using app<br />
* Click [https://docs.google.com/spreadsheet/viewform?formkey=dHpCZmVwMkEwbFI2WW5kVFdySFd6YWc6MQ#gid=0 here] to let us know you installed the app<br />
<br />
== Project Information ==<br />
=== Requested skills and experience ===<br />
If you have any experience in making or releasing applications for feature phones (non-smart phones, may be a good description of these phones) then your help would be appreciated. Skills needed include:<br />
<br />
Programming Skills:<br />
* Java (Java ME)<br />
* Symbian<br />
* Brew<br />
<br />
Distribution Skills:<br />
* Knowledge of phone carriers<br />
* Knowledge of phone app download sites<br />
<br />
Testing Skills:<br />
* A mobile feature phone upon which you can put your own apps.<br />
<br />
If you have abilities in the above areas, and are willing to help, please sign up for this [https://tech.lds.org/?option=com_talentpool&controller=projects&view=joinproject&Itemid=39&Projectid=95 project], and send an e-mail to [mailto:h.rushton@ldschurch.org h.rushton@ldschurch.org] with a note on how you would like to help.<br />
<br />
[[Feature Phone App Loading]] (Under Construction -- coming soon)<br />
[[Category:Official LDS Apps]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Cross_platform_and_multi-language_(Gospel_Library_for_JavaME)&diff=70852Cross platform and multi-language (Gospel Library for JavaME)2015-03-11T05:36:02Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Cross Platform and Multi-language to Cross platform and multi-language (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>{{BoMFFLinks}}<br />
<br />
== Maven ==<br />
Maven is being used by many projects at LDS Tech.<br />
[[LDS_Java_Stack]] uses Maven, and links to some useful information on it.<br />
*[http://maven.apache.org/ Maven Home Page]<br />
<br />
== Ant ==<br />
Ant is used in many projects to do complicated builds<br />
*[http://ant.apache.org/ Ant Home Page]<br />
*[http://onlamp.com/pub/a/php/2005/12/20/php_ant.html A nice intro to Ant]<br />
<br />
<br />
== Platforms ==<br />
Java Tiny<br />
*Smallest database possible (Tiny Database)<br />
*smallest app possible<br />
*Broad distribution--should work on anything<br />
<br />
Java Small<br />
*Small database<br />
<br />
Symbian?<br />
<br />
Brew<br />
*Small database<br />
<br />
<br />
== Language Groups ==<br />
'''Standard ASCII:''' <br />
English, Spanish, Portuguese, French, Italian, German, Spanish<br />
<br />
'''Double Byte Languages:'''<br />
Russian, Chinese (simplified), Chinese (traditional)<br />
<br />
'''Right to Left Languages:'''<br />
Hebrew, Arabic</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Interesting_articles_(Gospel_Library_for_JavaME)&diff=70850Interesting articles (Gospel Library for JavaME)2015-03-11T05:35:25Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Interesting Articles to Interesting articles (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>{{GLJMELinks}}This page should be notes and links on interesting articles that could help us determine directions to take the project.<br />
<br />
* [http://www.club-java.com/TastePhone/J2ME/MIDP_Benchmark.jsp;jsessionid=647017B04068429F74F40B311A493C6A a cool list of phones]<br />
* [http://www.developer.nokia.com/Develop/Java/ 1 billion nokia java phones... wow!]<br />
* [http://www.developer.nokia.com/Community/Wiki/Scrollable_Text_in_Java_ME scrollable text sample]<br />
* [http://techcrunch.com/2011/11/28/its-still-a-feature-phone-world-global-smartphone-penetration-at-27/ It's still a feature phone world]<br />
<br />
* [http://en.wikipedia.org/wiki/List_of_Book_of_Mormon_translations list of existing translations]<br />
<br />
* [http://www.enough.de/fileadmin/uploads/dev_guide_pdfs/Developers_Guide_8th.pdf Interesting multiplatform development pdf]<br />
<br />
* [http://articles.cnn.com/2011-01-25/tech/feature.phone.apps_1_feature-phones-app-data-charges?_s=PM:TECH Why feature phones still matter (CNN)]<br />
<br />
* [http://www.developer.nokia.com/Community/Wiki/How_to_install_Java_ME_application_in_mobile_phone Nokia site description of how to install apps on J2ME phones]<br />
<br />
[[Category:Gospel Library for JavaME|Interesting Articles]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Cell_Phone_Carriers_(Gospel_Library_for_JavaME)&diff=70847Cell Phone Carriers (Gospel Library for JavaME)2015-03-11T05:33:45Z<p>Aebrown: Aebrown moved page Cell Phone Carriers (Gospel Library for JavaME) to Cell phone carriers (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>#REDIRECT [[Cell phone carriers (Gospel Library for JavaME)]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Cell_phone_carriers_(Gospel_Library_for_JavaME)&diff=70846Cell phone carriers (Gospel Library for JavaME)2015-03-11T05:33:45Z<p>Aebrown: Aebrown moved page Cell Phone Carriers (Gospel Library for JavaME) to Cell phone carriers (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>{{GLJMELinks}}This page should show a description of all the Cell Phone Carriers in the world, with notes and/or links on how to get apps to users of those Carriers.<br />
<br />
== United States ==<br />
<br />
'''Verizon:''' Verizon has a developer program, and an expensive testing/approval process. It is outlined here: http://developer.verizon.com/jsps/devCenters/wireless/index.jsp<br />
<br />
== Latin America ==<br />
'''Telefonica'''</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Cell_phone_carriers_(Gospel_Library_for_JavaME)&diff=70844Cell phone carriers (Gospel Library for JavaME)2015-03-11T05:33:19Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Cell Phone Carriers to Cell Phone Carriers (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>{{GLJMELinks}}This page should show a description of all the Cell Phone Carriers in the world, with notes and/or links on how to get apps to users of those Carriers.<br />
<br />
== United States ==<br />
<br />
'''Verizon:''' Verizon has a developer program, and an expensive testing/approval process. It is outlined here: http://developer.verizon.com/jsps/devCenters/wireless/index.jsp<br />
<br />
== Latin America ==<br />
'''Telefonica'''</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Phone_types_and_capabilities_(Gospel_Library_for_JavaME)&diff=70842Phone types and capabilities (Gospel Library for JavaME)2015-03-11T05:32:42Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Phone Types and Capabilities to Phone types and capabilities (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>{{GLJMELinks}}This page should contain a description of all phone types and their pertinent capabilities. This will help us know how to design the build process to handle the different phones.<br />
<br />
== Phones and locations we have successfully installed the App ==<br />
*Sony Ericsson W580i<br />
*Sony Ericsson W810<br />
*Nokia N8 (It should work on all Symbian devices)<br />
*Nokia X6<br />
*LG LG600G<br />
*LG 420G (TracFone)<br />
<br />
*Multiple Motorola handsets<br />
<br />
== Phones we can't develop for ==<br />
These phones have no OS: (like Java)<br />
{|border="1" cellspacing="0" cellpadding="2"<br />
! Brand||Model<br />
|-<br />
| Nokia|| 1108, 1100, 2100, 2300 <br />
|-<br />
| Samsung|| C170<br />
|-<br />
| Sony Ericsson|| K220i<br />
|}<br />
{{-}}</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Phone_types_and_capabilities_(Gospel_Library_for_JavaME)&diff=70841Phone types and capabilities (Gospel Library for JavaME)2015-03-11T05:31:40Z<p>Aebrown: Reverted edits by Aebrown (talk) to last revision by Timriker</p>
<hr />
<div>{{GLJMELinks}}This page should contain a description of all phone types and their pertinent capabilities. This will help us know how to design the build process to handle the different phones.<br />
<br />
== Phones and locations we have successfully installed the App ==<br />
*Sony Ericsson W580i<br />
*Sony Ericsson W810<br />
*Nokia N8 (It should work on all Symbian devices)<br />
*Nokia X6<br />
*LG LG600G<br />
*LG 420G (TracFone)<br />
<br />
*Multiple Motorola handsets<br />
<br />
== Phones we can't develop for ==<br />
These phones have no OS: (like Java)<br />
{|border="1" cellspacing="0" cellpadding="2"<br />
! Brand||Model<br />
|-<br />
| Nokia|| 1108, 1100, 2100, 2300 <br />
|-<br />
| Samsung|| C170<br />
|-<br />
| Sony Ericsson|| K220i<br />
|}<br />
{{-}}</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=List_of_devices_(Gospel_Library_for_JavaME)&diff=70839List of devices (Gospel Library for JavaME)2015-03-11T05:30:51Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: List of Devices to List of devices (Gospel Library for JavaME): Standardize title</p>
<hr />
<div>== Devices it works on ==<br />
*Samsung S5230N (Book of Mormon only)<br />
* Samsung GT-S3350<br />
*LG GS290<br />
*LG 800G (Book of Mormon JavaME) <br />
*LG 800G w/ 4-gig micro-card installed (both Book of Mormon and full Gospel Library JavaME )<br />
*Pantech Impact P7000 (Both work. Requires SD card and must be installed via Internet, cannot be side-loaded)<br />
*Sony Ericsson w810<br />
*Sony Ericsson 580i<br />
*Nokia X6 (emulation mode)<br />
*Nokia N8 (emulation mode)<br />
*MicroEmulator J2Me Emulator<br />
<br />
(from an email)<br />
<br />
The methods I've used to install the Feature Phone Gospel Library app are:<br />
<br />
1) Bluetooth (the most common), Tracfone LG 420, 430, 440, 620, cingular Sony-Ericsson, AT&T Nokia,<br />
<br />
2) USB file transfer, cingular Sony-Ericsson, AT&T Nokia,<br />
<br />
3) Wi-fi file transfer, cingular Sony-Ericsson, AT&T Nokia.<br />
<br />
== Devices it WON'T work on ==<br />
*Anything from Verizon<br />
*A T-Mobile Samsung phone (need model #)<br />
*So far I can't get a T-Mobile Motorola Renew model W233 to work (no bluetooth) (small chance of working using Web Access, but didn't have data plan to try it) (ojhurst)<br />
<br />
<br />
[[Category:Gospel Library for JavaME]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Phone_types_and_capabilities_(Gospel_Library_for_JavaME)&diff=70838Phone types and capabilities (Gospel Library for JavaME)2015-03-11T05:29:36Z<p>Aebrown: Add sort key to category</p>
<hr />
<div>{{GLJMELinks}}This page should contain a description of all phone types and their pertinent capabilities. This will help us know how to design the build process to handle the different phones.<br />
<br />
== Phones and locations we have successfully installed the App ==<br />
*Sony Ericsson W580i<br />
*Sony Ericsson W810<br />
*Nokia N8 (It should work on all Symbian devices)<br />
*Nokia X6<br />
*LG LG600G<br />
*LG 420G (TracFone)<br />
<br />
*Multiple Motorola handsets<br />
<br />
== Phones we can't develop for ==<br />
These phones have no OS: (like Java)<br />
{|border="1" cellspacing="0" cellpadding="2"<br />
! Brand||Model<br />
|-<br />
| Nokia|| 1108, 1100, 2100, 2300 <br />
|-<br />
| Samsung|| C170<br />
|-<br />
| Sony Ericsson|| K220i<br />
|}<br />
{{-}}<br />
<br />
[[Category:Gospel Library for JavaME|Phone Types and Capabilities]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Interesting_articles_(Gospel_Library_for_JavaME)&diff=70837Interesting articles (Gospel Library for JavaME)2015-03-11T05:28:27Z<p>Aebrown: Add sort key to category</p>
<hr />
<div>{{GLJMELinks}}This page should be notes and links on interesting articles that could help us determine directions to take the project.<br />
<br />
* [http://www.club-java.com/TastePhone/J2ME/MIDP_Benchmark.jsp;jsessionid=647017B04068429F74F40B311A493C6A a cool list of phones]<br />
* [http://www.developer.nokia.com/Develop/Java/ 1 billion nokia java phones... wow!]<br />
* [http://www.developer.nokia.com/Community/Wiki/Scrollable_Text_in_Java_ME scrollable text sample]<br />
* [http://techcrunch.com/2011/11/28/its-still-a-feature-phone-world-global-smartphone-penetration-at-27/ It's still a feature phone world]<br />
<br />
* [http://en.wikipedia.org/wiki/List_of_Book_of_Mormon_translations list of existing translations]<br />
<br />
* [http://www.enough.de/fileadmin/uploads/dev_guide_pdfs/Developers_Guide_8th.pdf Interesting multiplatform development pdf]<br />
<br />
* [http://articles.cnn.com/2011-01-25/tech/feature.phone.apps_1_feature-phones-app-data-charges?_s=PM:TECH Why feature phones still matter (CNN)]<br />
<br />
* [http://www.developer.nokia.com/Community/Wiki/How_to_install_Java_ME_application_in_mobile_phone Nokia site description of how to install apps on J2ME phones]<br />
<br />
[[Category:Gospel Library for JavaME|Interesting Articles]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Template:GLJMELinks&diff=70836Template:GLJMELinks2015-03-11T05:27:04Z<p>Aebrown: Reverted edits by Aebrown (talk) to last revision by Timriker</p>
<hr />
<div><div style="border: 1px solid black; padding: 10px; margin: 10px; background-color: #F2F3E5; font-size: x-small; float:right;"><br />
<span style="font-size: medium; font-weight: bold">Research Links</span><br />
* [[Gospel Library for JavaME: Phone Types and Capabilities | Phone Types and Capabilities]]<br />
* [[Gospel Library for JavaME:_Cell_Phone_Carriers | Cell Phone Carriers]]<br />
* [[Gospel Library for JavaME:_App_Distribution_Methods | App Distribution Methods]]<br />
* [[Gospel Library for JavaME:_Interesting_Articles | Interesting Articles on Cell Phones and Apps]]<br />
* [[Gospel Library for JavaME:_Cross_Platform_and_Multi-language| Cross Platform and Multi-language Development]]<br />
* [[Gospel Library for JavaME | Gospel Library for JavaME home]]<br />
</div><noinclude>{{tempmain|Gospel Library for JavaME}}<br />
== Purpose ==<br />
This template is an infobox for research-oriented links for [[Gospel Library for JavaME]] articles. It will help readers navigate between related articles.<br />
<br />
== Usage ==<br />
This template has no parameters. The template should be added to relevant articles by inserting {{tl|GLJMELinks}} at the very top of the article code.<br />
<br />
== Categorization ==<br />
Articles that transclude this template will automatically be categorized in [[:Category:Gospel Library for JavaME]].<br />
[[Category:Index box templates|GLJMELinks]]<br />
</noinclude><includeonly>[[Category:Gospel Library for JavaME]]</includeonly></div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Template:GLJMELinks&diff=70835Template:GLJMELinks2015-03-11T05:11:30Z<p>Aebrown: Add sort key to category</p>
<hr />
<div><div style="border: 1px solid black; padding: 10px; margin: 10px; background-color: #F2F3E5; font-size: x-small; float:right;"><br />
<span style="font-size: medium; font-weight: bold">Research Links</span><br />
* [[Gospel Library for JavaME: Phone Types and Capabilities | Phone Types and Capabilities]]<br />
* [[Gospel Library for JavaME:_Cell_Phone_Carriers | Cell Phone Carriers]]<br />
* [[Gospel Library for JavaME:_App_Distribution_Methods | App Distribution Methods]]<br />
* [[Gospel Library for JavaME:_Interesting_Articles | Interesting Articles on Cell Phones and Apps]]<br />
* [[Gospel Library for JavaME:_Cross_Platform_and_Multi-language| Cross Platform and Multi-language Development]]<br />
* [[Gospel Library for JavaME | Gospel Library for JavaME home]]<br />
</div><noinclude>{{tempmain|Gospel Library for JavaME}}<br />
== Purpose ==<br />
This template is an infobox for research-oriented links for [[Gospel Library for JavaME]] articles. It will help readers navigate between related articles.<br />
<br />
== Usage ==<br />
This template has no parameters. The template should be added to relevant articles by inserting {{tl|GLJMELinks}} at the very top of the article code.<br />
<br />
== Categorization ==<br />
Articles that transclude this template will automatically be categorized in [[:Category:Gospel Library for JavaME]].<br />
[[Category:Index box templates|GLJMELinks]]<br />
</noinclude><includeonly>[[Category:Gospel Library for JavaME|{{PAGENAME}}]]</includeonly></div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Device_and_carrier_considerations_(Gospel_Library_for_JavaME)&diff=70834Device and carrier considerations (Gospel Library for JavaME)2015-03-11T05:08:04Z<p>Aebrown: </p>
<hr />
<div>== Any carrier ==<br />
<br />
=== Devices ===<br />
<br />
'''Nokia X6-00:''' Bluetooth, USB, Wifi<br />
<br />
'''Sony-Ericsson W810i, , W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Cingular ==<br />
<br />
=== Devices ===<br />
<br />
'''Sony-Ericsson W810i, W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Tracfone, NET10, Total, Straight Talk, SafeLink, Telcel América, Simple Mobile, Page Plus Cellular ==<br />
<br />
Phone must have at least one minute of time remaining. Okay if Service Days have expired. Only the JAR file is needed for installation. When installing, users must "buy" the application, however, as the price is set to zero minutes, no minutes will be deducted from minutes available.<br />
<br />
=== Devices ===<br />
<br />
'''LG 420G, 430G, 440G:''' Bluetooth<br />
<br />
'''LG 620G:''' Bluetooth, USB<br />
<br />
[[Category:Gospel Library for JavaME|Device and Carrier Considerations]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Device_and_carrier_considerations_(Gospel_Library_for_JavaME)&diff=70833Device and carrier considerations (Gospel Library for JavaME)2015-03-11T05:05:30Z<p>Aebrown: Aebrown moved page Gospel Library for JavaME: Device / Carrier Considerations to Gospel Library for JavaME: Device and Carrier Considerations without leaving a redirect: Remove slash to avoid creation of a subpage</p>
<hr />
<div>== Any carrier ==<br />
<br />
=== Devices ===<br />
<br />
'''Nokia X6-00:''' Bluetooth, USB, Wifi<br />
<br />
'''Sony-Ericsson W810i, , W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Cingular ==<br />
<br />
=== Devices ===<br />
<br />
'''Sony-Ericsson W810i, W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Tracfone, NET10, Total, Straight Talk, SafeLink, Telcel América, Simple Mobile, Page Plus Cellular ==<br />
<br />
Phone must have at least one minute of time remaining. Okay if Service Days have expired. Only the JAR file is needed for installation. When installing, users must "buy" the application, however, as the price is set to zero minutes, no minutes will be deducted from minutes available.<br />
<br />
=== Devices ===<br />
<br />
'''LG 420G, 430G, 440G:''' Bluetooth<br />
<br />
'''LG 620G:''' Bluetooth, USB<br />
<br />
[[Category:Gospel Library for JavaME]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Device_and_carrier_considerations_(Gospel_Library_for_JavaME)&diff=70831Device and carrier considerations (Gospel Library for JavaME)2015-03-11T04:51:38Z<p>Aebrown: Standardize heading formats, add category</p>
<hr />
<div>== Any carrier ==<br />
<br />
=== Devices ===<br />
<br />
'''Nokia X6-00:''' Bluetooth, USB, Wifi<br />
<br />
'''Sony-Ericsson W810i, , W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Cingular ==<br />
<br />
=== Devices ===<br />
<br />
'''Sony-Ericsson W810i, W580i:''' Bluetooth, USB, Wifi - App will not install if another version is already running.<br />
<br />
== Tracfone, NET10, Total, Straight Talk, SafeLink, Telcel América, Simple Mobile, Page Plus Cellular ==<br />
<br />
Phone must have at least one minute of time remaining. Okay if Service Days have expired. Only the JAR file is needed for installation. When installing, users must "buy" the application, however, as the price is set to zero minutes, no minutes will be deducted from minutes available.<br />
<br />
=== Devices ===<br />
<br />
'''LG 420G, 430G, 440G:''' Bluetooth<br />
<br />
'''LG 620G:''' Bluetooth, USB<br />
<br />
[[Category:Gospel Library for JavaME]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User_talk:Wbernal&diff=70796User talk:Wbernal2015-02-24T14:49:25Z<p>Aebrown: format, respond</p>
<hr />
<div>== Access to youth names in other wards ==<br />
Would it be possible on LDS tools app to have the Stake leaders like myself (stake YM's)to have access to the names of the Youth from all wards? Given that most families have pictures up it sure would be nice when visiting new wards to put names with faces to some of the kids that we see and teach. Yes, we need to get out there and introduce ourselves but it makes a good impression on someone when you can walk up to them and call them by name. is there anyway to enable that information? -- [[User:Wbernal|Wbernal]] 14:25, 23 February 2015<br />
<br />
: First of all, questions should be asked in a talk (discussion) page, so I moved your question to your User Talk page.<br />
<br />
: As for your question, hardly anyone will see it here on the wiki. You're much better off posting it in the LDSTech Forum, probably in the [https://tech.lds.org/forum/viewforum.php?f=115# LDS Tools] or [https://tech.lds.org/forum/viewforum.php?f=111# Directory] forum section (the access rules are the same for both the Directory and LDS Tools). You also might want to review existing discussions for this issue, such as [https://tech.lds.org/forum/viewtopic.php?f=111&t=20444 Member Directory] or [https://tech.lds.org/forum/viewtopic.php?p=101081#p101081 Stake YM/YW Visibility to Unit Youth and Calendars]. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 07:49, 24 February 2015 (MST)</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User:Wbernal&diff=70795User:Wbernal2015-02-24T14:40:06Z<p>Aebrown: Aebrown moved page User:Wbernal to User talk:Wbernal: discussions belong in the Talk namespace</p>
<hr />
<div>#REDIRECT [[User talk:Wbernal]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User_talk:Wbernal&diff=70794User talk:Wbernal2015-02-24T14:40:06Z<p>Aebrown: Aebrown moved page User:Wbernal to User talk:Wbernal: discussions belong in the Talk namespace</p>
<hr />
<div>Would it be possible on LDS tools app to have the Stake leaders like myself (stake YM's)to have access to the names of the Youth from all wards? Given that most families have pictures up it sure would be nice when visiting new wards to put names with faces to some of the kids that we see and teach. Yes, we need to get out there and introduce ourselves but it makes a good impression on someone when you can walk up to them and call them by name. is there anyway to enable that information?</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User:Aebrown/Sandbox&diff=70759User:Aebrown/Sandbox2015-02-12T16:02:01Z<p>Aebrown: </p>
<hr />
<div>This is my primary sandbox, where I test out various proposed features or pages, or experiment with wiki syntax.<br />
<br />
== Response when users post to main namespace ==<br />
: First of all, please don't ask questions in the main namespace of the wiki -- that is reserved for actual articles. Questions should only be asked in a Talk (discussion) namespace. So I moved your question to your user talk page.<br />
<br />
: Second, you'll get much better answers if you ask questions like these on the LDSTech Forum. So I'd recommend that you post your question in the [https://tech.lds.org/forum/viewforum.php?f=92 LDS Account] forum section. Many more people will see your question there. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 23:41, 21 January 2015 (MST)<br />
<br />
== Images ==<br />
[[Image:LDS-Account-registration.png|thumb|LDS Account registration screen]]This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...This image should float right by default. But it doesn't currently. This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...<br />
<br />
This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...This image should float right by default. But it doesn't currently. This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...<br />
<br />
== Statistics ==<br />
* Articles: {{NUMBEROFARTICLES}}<br />
* Pages: {{NUMBEROFPAGES}}<br />
* Pages in Projects category: {{PAGESINCAT:Projects}}<br />
<br />
== Parser functions ==<br />
* <nowiki>{{#ifeq: 1 | 1 | yes | no}}</nowiki>: {{#ifeq: 1 | 1 | yes | no}}<br />
* <nowiki>{{#ifeq: 1 | 2 | yes | no}}</nowiki>: {{#ifeq: 1 | 2 | yes | no}}<br />
* <nowiki>{{#ifexist: Main_Page | yes | no}}</nowiki>: {{#ifexist: Main_Page | yes | no}}<br />
* <nowiki>{{#ifexist: Main Page | yes | no}}</nowiki>: {{#ifexist: Main Page | yes | no}}<br />
* <nowiki>{{#ifexist: xyzzy | yes | no}}</nowiki>: {{#ifexist: xyzzy | yes | no}}<br />
<br />
== Sub-sub page ==<br />
[[User:Aebrown/Sandbox/subpage]]<br />
<br />
== Langlink template ==<br />
El {{langlink|es|stake technology specialist|especialista en tecnología}} es responsable de:<br />
<br />
... mantener y apoyar las {{langlink|es|Printing|impresora}} y equipos ...<br />
<br />
=== Translation of system messages ===<br />
* en: {{MediaWiki:Otherlanguages}}<br />
* de: {{MediaWiki:Otherlanguages/de}}<br />
* es: {{MediaWiki:Otherlanguages/es}}<br />
* fr: {{MediaWiki:Otherlanguages/fr}}<br />
<br />
=== Conditional system messages ===<br />
* Link to Spanish page: [[User:Aebrown/es]]<br />
* Link to English page: [[User:Aebrown/en]]<br />
<br />
== Table classes ==<br />
{| class="wikitable"<br />
|+ Test table<br />
! Head 1<br />
! Head 2<br />
|-<br />
| R1C1<br />
| R1C2<br />
|-<br />
| R2C1<br />
| R2C2<br />
|}<br />
<br />
=== Vertical alignment ===<br />
<br />
{| border="1"<br />
|+ Test table<br />
! Head 1<br />
! Head 2<br />
|-<br />
| R1C1<br />
| R1C2<br />
2<br />
3<br />
4<br />
|- valign="top"<br />
| R2C1<br />
| R2C2<br />
2<br />
3<br />
4<br />
|}<br />
<br />
== Linked image ==<br />
<div style="border: 1px solid gray; padding:1px; width: {{#expr:175+4}}px; float:right; margin: 10px;"><br />
<div style="padding: 2px; text-align:center; margin:auto; ">[[File:Firmanualthumb.png|link={{Filepath:FIR Documentation 120329 1.pdf}}|175px]]<br> Click to view the FIR user manual (PDF)</div><br />
</div> This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...This image should float right by default. But it doesn't currently. This is some lengthy text before the image. When in the course of human events it becomes necessary for one people to dissolve the political bands which have connected them with another...</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User:Jessepromise&diff=70753User:Jessepromise2015-02-09T23:03:28Z<p>Aebrown: Constrain photo size</p>
<hr />
<div>===TECH LOVER===<br />
[[file:Jesse.jpg|300px]]<br />
;E-mail<br />
:jessepromise@yahoo.com<br />
;Website<br />
:jessepromise.blogspot.com<br />
<br />
===LOCATION===<br />
Nigeria</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User:Grandpasvedin&diff=70747User:Grandpasvedin2015-02-05T03:25:53Z<p>Aebrown: </p>
<hr />
<div>Walter Stephen Svedin<br><br />
Live in Nampa Idaho<br><br />
Phone # - 208-941-3689<br />
<br />
Real life Job - Horticulturalist (Gardener)</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User_talk:Janicerose&diff=70719User talk:Janicerose2015-01-12T14:39:37Z<p>Aebrown: format and respond</p>
<hr />
<div>I LOVED! being able to do the following on the LDS Scriptures app:<br />
* Highlight text<br />
* Put notes by the text<br />
* Tag paragraphs or scriptures to a topic<br />
* Cross reference scriptures<br />
<br />
When will Gospel Library allow me to do these things?<br><br />
Jan<br />
<br />
: You can do almost all of that right now. The cross-referencing is a bit weak, but the other three things are all in place. I use them all the time on my Android Gospel Library.<br />
<br />
: But in any case, hardly anyone sees discussions on the wiki. You will get a much better discussion if you post on the LDSTech Forum, in the [https://tech.lds.org/forum/viewforum.php?f=101# Gospel Library] forum or one of its subforums, depending on your device. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 07:39, 12 January 2015 (MST)</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=TechWiki_talk:January_Broadcast_2015&diff=70713TechWiki talk:January Broadcast 20152015-01-11T13:30:25Z<p>Aebrown: respond</p>
<hr />
<div>== Apple TV question ==<br />
Viewing the broadcast on 9 Jan, a question was raised regarding Mormon Channel being available for Apple TV.<br />
<br />
I don't believe it was answered satisfactorily. <br />
<br />
From what I understand, you can transmit anything that you can view on your Ipad, to the Apple TV unit. <br />
<br />
You can also achieve the same effect on Android using Chromecast.<br />
-- [[User:Dudleygrantbutt|Dudleygrantbutt]] 04:05, 10 January 2015<br />
<br />
---------------------------------------------------------<br />
: Since your comment deals with a specific broadcast, I moved it from the talk page for the [[LDSTech broadcasts]] page to a talk page for the specific broadcast.<br />
<br />
: Note that the question was asked at the 56:00 mark, if anyone wants to review the question. I'll agree that the answer was not satisfactory -- it wasn't really an answer at all. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 21:49, 10 January 2015 (MST)<br />
---------------------------------------------------------<br />
Cool beans, thank you. It amazing to see the church investing in technology. <br />
For a little more info around the apple TV / Chromecast options, please see the following links<br />
* https://www.apple.com/au/airplay/<br />
* http://www.cnet.com/news/chromecast-vs-apple-tv-vs-roku-3-which-media-streamer-should-you-buy/<br />
* http://www.google.com/chrome/devices/chromecast/<br />
<br />
We are in the process of acquiring some of this kit in our ward.<br />
Android Lollipop also now provides built in Chromecast support.<br />
For just $35 for a Chromecast device, Apple needs to bring it.<br />
--[[User:Dudleygrantbutt|Dudleygrantbutt]] ([[User talk:Dudleygrantbutt|talk]]) 04:12, 11 January 2015 (MST)<br />
---------------------------------------------------------<br />
: Before you make too big of an investment of time into Chromecast, you might want to review this discussion on the LDSTech Forum: [https://tech.lds.org/forum/viewtopic.php?f=51&t=20080 Chromecast not connecting to the internet], which discusses challenges with the Chromecast working with the Meetinghouse Firewall.<br />
<br />
: Also, these wiki talk pages don't get much traffic -- you'd be better off having this discussion on the Forum, since it would involve more people than just you and me. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 06:30, 11 January 2015 (MST)</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=TechWiki_talk:January_Broadcast_2015&diff=70710TechWiki talk:January Broadcast 20152015-01-11T04:49:37Z<p>Aebrown: Format and respond</p>
<hr />
<div>== Apple TV question ==<br />
Viewing the broadcast on 9 Jan, a question was raised regarding Mormon Channel being available for Apple TV.<br />
<br />
I don't believe it was answered satisfactorily. <br />
<br />
From what I understand, you can transmit anything that you can view on your Ipad, to the Apple TV unit. <br />
<br />
You can also achieve the same effect on Android using Chromecast.<br />
-- [[User:Dudleygrantbutt|Dudleygrantbutt]] 04:05, 10 January 2015<br />
<br />
: Since your comment deals with a specific broadcast, I moved it from the talk page for the [[LDSTech broadcasts]] page to a talk page for the specific broadcast.<br />
<br />
: Note that the question was asked at the 56:00 mark, if anyone wants to review the question. I'll agree that the answer was not satisfactory -- it wasn't really an answer at all. -- [[User:Aebrown|Aebrown]] ([[User talk:Aebrown|talk]]) 21:49, 10 January 2015 (MST)</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=TechWiki_talk:January_Broadcast_2015&diff=70709TechWiki talk:January Broadcast 20152015-01-11T04:45:19Z<p>Aebrown: Aebrown moved page Talk:LDSTech broadcasts to LDSTech talk:January Broadcast 2015 without leaving a redirect: Page specific to the referenced broadcast is more appropriate</p>
<hr />
<div>Viewing the broadcast on 9 Jan, a question was raised regarding Mormon Channel being available for Apple TV.<br />
I don't believe it was answered satisfactorily. <br />
From what I understand, you can transmit anything that you can view on your Ipad, to the Apple TV unit. <br />
You can also achieve the same effect on Android using Chromecast.</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User:Swtbentley/Sandbox&diff=70617User:Swtbentley/Sandbox2014-11-25T20:30:41Z<p>Aebrown: Created page with "== Elder Bentley's Sandbox == Test pages in the Sandbox: * Test Page"</p>
<hr />
<div>== Elder Bentley's Sandbox ==<br />
<br />
Test pages in the Sandbox:<br />
* [[User:Swtbentley/Sandbox/Test Page|Test Page]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User:Swtbentley/Sandbox/Test_Page&diff=70616User:Swtbentley/Sandbox/Test Page2014-11-25T20:27:30Z<p>Aebrown: Example of how to create a Sandbox page</p>
<hr />
<div>Elder Bentley's test page.</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Installing_MarkLogic&diff=70545Installing MarkLogic2014-11-14T06:04:38Z<p>Aebrown: Add category</p>
<hr />
<div><br />
== Installing MarkLogic on Windows ==<br />
<br />
(These instructions are for Windows XP, Vista, and 7. Installation and server start-up may differ slightly for other operating systems.)<br />
<br />
# [http://developer.marklogic.com/products Download] the latest version of the MarkLogic Server for your operating system.<br />
#* Upon clicking on the download link, you will need to agree to MarkLogic's Terms of Use.<br />
# Execute the MarkLogic Server installer.<br />
#* Choose a "Typical" setup. This will take about 5 minutes.<br />
# After installation is complete start the Mark Logic Server.<br />
#* (Windows Only) Go to Start > All Programs > MarkLogic Server > Start MarkLogic Server<br />
#** Important! Right-click on "Start MarkLogic Server" and select "Run as administrator". Otherwise, the server may not start.<br />
#** If you get the error message "The application failed to initialize properly...", then see [http://developer.marklogic.com/products/marklogic-server/requirements MarkLogic Server 4.x System Requirements] to download and install the necessary dll for your operating system. Then try starting the server again.<br />
#** If start-up succeeds, you will not see any message.<br />
# Go to the Mark Logic administration console:<br />
#* (Windows Only) Go to Start > All Program > MarkLogic Server > Admin MarkLogic Server.<br />
#* A browser window will open and you will be prompted to enter a license key.<br />
#** If you do not yet have a license, do one of the following:<br />
#*** (Employees Only) Request a license key by emailing [mailto:DL-ICS-MARKLOGIC DL-ICS-MARKLOGIC].<br />
#**** Enter the licensee and the license key, then click "OK". The MarkLogic Server will restart.<br />
#*** (Non-employees Only) You may request a free license for community development by clicking the "Free" button and then entering the required information in the supplied form.<br />
#**** '''Licensee'''. This is '''your''' name.<br />
#**** '''Company'''. ''Do NOT put the name of the Church or any of its business entities in this field.'' You may put "Home" or "Community" in this field if you will be using the MarkLogic Server for personal or community development.<br />
#**** '''Email'''. This is your personal email address.<br />
#**** Choose "Select Community License".<br />
#**** Make a copy of your license information and then click "OK". The MarkLogic Server will restart.<br />
#* Accept the license agreement by scrolling to the bottom of the page and clicking "Accept". The MarkLogic Server will restart.<br />
#* You will now be prompted to install the initial databases and application servers. Click "OK" to continue. When installation is complete. The server will restart.<br />
#* When prompted to enter an Admin username and password, enter "admin" as the user and "admin" as the password. Confirm the password and click "OK" to continue.<br />
#* When prompted, enter the user name and password you supplied. You will then be redirected to the MarkLogic Server administration console.<br />
# Configure an XDBC server<br />
#* Expand "Groups", then expand "Default", and then select "App Servers".<br />
#*; <br/>[[File:marklogic-admin-step1.png]]<br/><br/><br />
#* Click the tab "Create XDBC"<br />
#** Supply an XDBC server name.<br />
#*** For the Stack Petstore project, enter "stack-petstore".<br />
#** Supply a value for the module directory root.<br />
#*** For the Stack Petstore project, enter "/".<br />
#** Supply a value for the port the XDBC server will listen to for connections.<br />
#*** For the Stack Petstore project, enter "8010".<br />
#** For the modules field, choose "Modules" from the list of options.<br />
#** Leave all other fields as they are, and click "OK" at the top of the page.<br />
#*; <br/>[[File:marklogic-admin-step2.png]]<br/><br/><br />
# To try out your Mark Logic installation, go to [http://localhost:8000 <nowiki>http://localhost:8000</nowiki>] and login with your admin username.<br />
<br />
[[Category:MarkLogic]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=What_is_MarkLogic%3F&diff=70544What is MarkLogic?2014-11-14T06:02:39Z<p>Aebrown: Fix category</p>
<hr />
<div><br />
== What is MarkLogic? ==<br />
[http://www.marklogic.com/what-is-marklogic/ MarkLogic] is a [http://www.marklogic.com/what-is-marklogic/inside-marklogic/ '''REST application server''', '''document database''', and '''search engine''']. It is REST through and through. It is built specifically for hypertext documents, links, metadata, URIs, MIME types, and HTTP. It is schema-agnostic because it is automatically aware of the independent structure of each of its JSON and XML documents. It is search-centric because it can search for ''any combination'' of words, values, structures, and links within and across documents. It scales horizontally to hundreds of servers within and between data centers while maintaining ACID-compliant transactions. <br />
<br />
MarkLogic has the following [http://www.marklogic.com/what-is-marklogic/enterprise-nosql/ enterprise features]:<br />
* [http://www.marklogic.com/resources/java-developers-guide/ Java APIs]<br />
* [http://en.wikipedia.org/wiki/Node.js Node.js APIs]<br />
* [http://developer.marklogic.com/learn/2009-07-search-api-walkthrough Search] and [http://developer.marklogic.com/learn/arch/search-and-indexing Query]<br />
* [http://www.marklogic.com/blog/can-you-pass-the-acid-test/ ACID Transactions]<br />
* [http://www.marklogic.com/resources/marklogic-high-availability-and-disaster-recovery/resource_download/datasheets/ High Availability] and [http://docs.marklogic.com/guide/database-replication/dbrep_intro#chapter Disaster Recovery]<br />
* [http://www.marklogic.com/resources/marklogic-flexible-replication/resource_download/datasheets/ Replication within and across data centers]<br />
* [http://docs.marklogic.com/guide/admin/security#chapter Government-grade Security]<br />
* [https://docs.marklogic.com/guide/cluster.pdf Scalability] and [https://docs.marklogic.com/guide/admin/database-rebalancing#chapter Elasticity]<br />
* [https://docs.marklogic.com/guide/ec2/managing#chapter On-premise or Cloud Deployment (especially AWS)]<br />
* [http://www.marklogic.com/resources/marklogic-and-hadoop/resource_download/datasheets/ Hadoop for Storage and Compute]<br />
* [http://www.marklogic.com/resources/marklogic-semantics-mlw14/ Semantics]<br />
<br />
== What is REST? ==<br />
REST is an architectural style that uses a uniform resource identifier ('''URI''') and a web protocol ('''HTTP/HTTPS''') to request and transfer a representation ('''MIME media type''') of the state of a resource ('''document''') at a point in time from a server to a client. <br />
<br />
REST was coined and defined by Roy Fielding in his <br />
[http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm dissertation, ''Architectural Styles and the Design of Network-based Software Architectures'']. REST standardizes and documents the patterns used in the world wide web: self-documenting hypertext with data and metadata (HTML), stateless request/response communication protocol (HTTP/HTTPS), resource locators (URL), multiple representations per URL (MIME types), and downloading code on demand to process resources (JavaScript, CSS, etc.).<br />
<br />
REST consists of three main concepts: <br />
* (RE) Representation<br />
* (S) State <br />
* (T) Transfer <br />
<br />
== Why is MarkLogic RESTful? ==<br />
<br />
=== '''Representation and MarkLogic''' === <br />
* A representation is a document that represents a resource. It has three requirements: MIME media type, URI, and hypertext.<br />
<br />
* '''MIME type:''' Each resource can be represented by one or more types of documents. The MIME media type defines the representation a client requests. A client may request the resource to be represented as JSON, XML, HTML, PNG, PDF, etc. <br />
**'''MarkLogic''' stores any type of document and assigns the appropriate [http://developer.marklogic.com/blog/document-formats-part2 MIME type] to it. It can fully index, query, search, and process JSON, XML, and RDF documents. It meets the REST requirement of being able to transform JSON, XML, and RDF documents into any other MIME type. It knows how to execute JavaScript, XQuery, XSLT, and SPARQL documents. It knows how [http://docs.marklogic.com/guide/cpf/default#chapter to transform into XHTML] the content, formatting, and structure of Microsoft Word, PowerPoint, Excel, textual PDF, DocBook, and CSS documents. (It can also use Microsoft Office to create, edit, and manage content in MarkLogic.) It knows how to [https://docs.marklogic.com/guide/search-dev/binary-document-metadata extract metadata and text from over 138 types of binary documents], such as raster images, vector images, videos, archive files, database files, encoded emails, presentations, spreadsheets, word-processing documents, text formats. <br />
**Few NoSQL databases use MIME types to identify the media type of each document. Most NoSQL databases support only one type of data and it is usually proprietary: columnar, BSON, binary, etc. Most cannot transform from one MIME type to another.<br />
<br />
* '''URI:''' A resource is identified by a globally unique identifier (URI). '''MarkLogic''' identifies each document with a [http://developer.marklogic.com/try/rest/page2 unique URI]. A document in MarkLogic is like a row in a table in a schema in a relational database. A URI is liberating. It provides random access to any resource anywhere. It is like being able to retrieve any row in any table in any schema of a relational database without having to know what table and schema the row is stored in. <br />
**Navigating URL hierarchy is fundamental to REST. MarkLogic understands the hierarchy within a URI, which is represented by slashes "/", such as https://www.lds.org/scriptures/ot/gen/1 MarkLogic treats the items between the slashes as folders. The URI of each document automatically places it in a folder in a folder hierarchy. A URI automatically defines the folder hierarchy. In the example URI above, the document for Genesis chapter 1, is located in the Genesis folder, which is located in the Old Testament folder, which is located in the Scriptures folder on lds.org. '''MarkLogic''' indexes the documents in each folder and its subfolders. This makes it fast and easy to retrieve any or all documents in any folder and/or its subfolders.<br />
**Few NoSQL databases use the URI as the primary key for their documents or data. They also don't index the URI hierarchically to filter documents by folder and subfolder.<br />
<br />
* '''Hypertext:''' A document should contain data that represents the resource. The data should be '''human readable and self-documenting''', like JSON, XML, RDF, and HTML. It should be '''linked data''' (i.e. the "hyper" in "hypertext"). A document should contain ''' metadata links''' about the resource, such as RDF. It should contain '''action links''' to define what further actions can be done with the resource. It should contain '''related links''' to related resources, such as images, audio, video, related documents, etc. Each related link should define what actions can be done with the referenced resource, such as download it, display a link to it, execute a command against it, etc.)<br />
**'''Hypertext''' or '''hypermedia''' documents must have all these features. Hyperlinks are what the "hyper" in hypertext and hypermedia refers to. You can't have REST without ''metadata links'' to define what the data means, ''action links'' to know how to work with the resource, and ''related links'' to connect resources. It should all be human readable and self-documenting so a developer does not have to read documentation to know how to interact with a REST web service and its documents. <br />
** '''MarkLogic''' meets all the requirements for hypertext representation. It is designed around MIME types, URIs, and Linked data. It stores documents with their MIME types as [http://www.w3schools.com/json/ JSON], [http://www.w3schools.com/xml/ XML], [http://www.w3schools.com/webservices/ws_rdf_intro.asp RDF], [http://www.w3schools.com/html/ HTML], etc. These documents are human-readable and self-documenting, which MarkLogic leverages to recognize and index each document's data, data structure, metadata links, action links, and related links. This makes it easy to '''search''', '''query''', '''transform''', and '''deliver''' hypertext documents. MarkLogic can also store any type of binary document and deliver it as a related resource, such as an image, video, or audio. MarkLogic is designed to process simple links and RDF links using [http://en.wikipedia.org/wiki/SPARQL SPARQL] and [https://docs.marklogic.com/xinc XInclude]. MarkLogic can represent links in many formats: [https://docs.marklogic.com/xp XPointer], [https://docs.marklogic.com/guide/semantics/loading#id_97709 RDF/XML], [https://docs.marklogic.com/guide/semantics/loading#id_79194 RDF/JSON], [https://docs.marklogic.com/guide/semantics/loading#id_73211 Turtle], [https://docs.marklogic.com/guide/semantics/loading#id_70596 N-Triples], [https://docs.marklogic.com/guide/semantics/loading#id_61596 N-Quads], and [https://docs.marklogic.com/guide/semantics/loading#id_74485 TriG].<br />
**No other NoSQL database natively indexes and fully processes all the document types required for REST hypertext: JSON, XML, RDF, HTML, CSS, and JavaScript.<br />
<br />
=== '''State and MarkLogic''' === <br />
* State in REST exists on the client and in server documents. It does not exist in the communications protocol or in the server as cached session data. <br />
<br />
* '''Server:''' All information needed to process a request must be presented in the request and processed against documents in the database. State must only be in the request and in database documents: state cannot be anywhere else, such as in a session cache. The documents in the server define the state of the server. A REST server should explicitly create a state machine that defines the acceptable actions that can transacted against documents in specific contexts.<br />
**A REST transaction occurs at a '''point in time'''. The state of the data in the request is unchanging, but the state of the documents and state machines in the database are often changing. Since request state and database state are both required to process the request and since shifting state creates unpredictable results, a REST transaction should run at a point in time with unchanging state. Only an ACID-compliant database can ensure consistent state because it isolates each transaction from every other transaction. The only time REST does not need an ACID-compliant database is when database documents do not change, database state machines do not change, or when clients can live with the resultant level of unreliable and unpredictable results.<br />
**'''MarkLogic''' meets all the requirements for REST state. Its web services are stateless: there is no session cache. It is ACID compliant. It ensures each transaction occurs at a point in time and is isolated from all other transactions. This ensures consistent processing during a transaction -- even across billions of documents. MarkLogic is an [http://en.wikipedia.org/wiki/Multiversion_concurrency_control MVCC] database which provides transaction isolation without slowing the performance of reads -- even when documents being read are being modified simultaneously by other transactions. (Also, like any other ACID database, when multiple updates and deletes compete for the same documents, they will impact each other's performance because change has to be serialized.) <br />
** Most other NoSQL databases are not ACID compliant. They are only suitable for REST services when their documents or data do not change or when the rate of change is slow enough or dispersed enough that it creates an acceptable level of unreliability and unpredictability.<br />
<br />
* '''Client:''' A REST client, such as a web browser or spider, locally maintains transactional state, such as what to do in response to documents and result codes that are returned from server transactions. An application exists only in the client -- not in the server (although, a server may deliver application code to a client, such as when a web server downloads HTML, CSS, and JavaScript to a browser). Client application code decides when to execute web service calls and it ties the results together to accomplish its purpose. This allows multiple authorized applications to reuse web services for a variety of purposes. <br />
**The server helps the client know what web service calls are available by providing action links with each response. Action links are contextual and the context is based on the application account, user account, database documents, links within and between documents, the server state machine, etc. Through action links, the server can inform a client application what web service calls are permissible in any given context.<br />
**'''MarkLogic''' meets the needs of client applications through its built-in ability to process and send action links to clients based on context. MarkLogic supports RDF triples and SPARQL, which enables context to be defined across applications, users, document state, links between documents, server state machine, etc. MarkLogic processes triples very quickly, which enables context to scale to billions of documents, millions of users, etc.<br />
**'''MarkLogic''' also uses application and user permissions to filter which documents are returned to clients. MarkLogic does this automatically and transparently by adding security filtering constraints into every search and query. This ensures no account can access unauthorized documents. This is fast because all security permissions are built-into MarkLogic's indexes -- which allows document-level security to scale across billions of documents.<br />
** Most other NoSQL databases do not provide government-grade, document-level security and they also do not support RDF triples and SPARQL.<br />
<br />
Because MarkLogic can provide both the web service and database in one server, it is easy to use the state of the documents and the <br />
<br />
=== '''Transfer and MarkLogic''' === <br />
* '''Transfer''' in REST is a communication protocol that enables a client to send a hypertext request to a server and receive back a hypertext response. The transfer must be stateless and be a request/response protocol. It must have human readable, self-descriptive headers. The header must contain metadata about the request, such as the requested resource URI, MIME type of the resource, action to perform on the resource (such as get, put, post, patch, and delete). [http://www.w3schools.com/tags/ref_httpmethods.asp '''HTTP'''] (Hypertext transfer protocol) and '''HTTPS''' (secure HTTP) are designed specifically for REST (that is why they have "hypertext" in their name).<br />
<br />
* All '''MarkLogic''' communication is through through HTTP and HTTPS REST services (except for its SQL JDBC feature). This includes all internal cluster communication. MarkLogic provides out-of-the-box REST interfaces for manipulating resources (insert, update, delete, query, search, transform, etc.) and administering MarkLogic (REST app servers, databases, indexes, clusters, etc). MarkLogic makes it very easy to create custom REST services because everything in MarkLogic is built around REST and because they provide simple and powerful application server APIs.<br />
<br />
== MarkLogic Query and Search ==<br />
MarkLogic is unlike relational databases (and a few NoSQL databases) where they use full table scans to retrieve every row in the table unless a query accesses less than 20% of the rows and then they use an index. MarkLogic does not do full table scans. It needs all queries to be resolved out of the indexes. For that reason, it indexes most things and allows you to index more.<br />
<br />
MarkLogic can query and search -- and use both in combination. MarkLogic uses indexes to execute searches and queries. The same indexes are used for both. The difference between search and query is how documents are sorted. Searches sort by relevance and queries sort by values. MarkLogic uses indexes to extract words, values, structures, and links out of documents. <br />
<br />
This enables you to search and query for documents as if they contained only<br />
*'''Words:''' a flat set of words without structure, such as <br><code>["Mary" "had", "a", "little", "lamb"]</code><br />
*'''Phrases:''' a flat set of phrases without structure, such as <br><code>["Mary had", "had a", "a little", "little lamb"]</code><br />
*'''Elements:''' a flat set of elements without values, such as <br><code>["poem", "text", "line"]</code><br />
*'''Element-values:''' a flat set of elements with string values, such as <br><code>"line": "Mary had a little lamb"</code><br />
*'''Element-words:''' a flat set of elements with words, such as <br><code>"line": ["Mary" "had", "a", "little", "lamb"]</code><br />
*'''Element-phrases:''' a flat set of elements with phrases, such as <br><code>"line": ["Mary had", "had a", "a little", "little lamb"]</code><br />
*'''Element-value lexicon:''' a flat set of elements with typed values, such as <br><code>"lineSequence": 3</code><br> or a list, count, or co-occurrence of element values scoped to a database, set of documents, or one document.<br />
*'''XPath-structure-value lexicon:''' a flat set of hierarchical elements with typed values, such as <br><code>poem.text.line.lineSequence: 3</code><br> or a list, count, or co-occurrence of hierarchical element values scoped to a database, set of documents, or one document.<br />
*'''XPath-structure:'''hierarchical structures without values, such as <br><code>poem.text.line</code><br />
*'''XPath-structure-words:''' hierarchical structures with words, such as <br><code>poem.text.line: ["Mary", "had", "a", "little", "lamb"]</code><br />
*'''XPath-structure-phrases:''' hierarchical structures with phrases, such as <br><code>poem.text.line: ["Mary had", "had a", "a little", "little lamb"]</code><br />
*'''XPath-structure-values:''' hierarchical structures with values, such as <br><code>poem.text.line: "Mary had a little lamb"</code><br />
*'''RDF document links''' to other documents, such as <br><code>{"subject": "http://example.org/documents/thisDoc", "predicate": "http://example.org/predicates/relatesSomehowTo", "object": "http://example.org/documents/thatDoc"}</code><br />
*'''RDF abstract links''' to other abstract concepts, such as <br><code>{"subject": "http://example.org/documents/thisDoc", "predicate": "http://example.org/predicates/relatesSomehowTo", "object": "http://example.org/documents/someConceptWithNoDocumentAtTheURI"}</code><br />
*'''RDF data links''' to data, such as <br><code>{"subject": "http://example.org/documents/thisDoc", "predicate": "http://example.org/predicates/ageInYears", "object": 12}</code><br />
<br />
MarkLogic can combine any of these indexes in any way to find matching documents. It can sort the result by relevance or by value. <br />
<br />
The [[MarkLogic Query and Search]] page provides more detail about how MarkLogic's unique indexes work and how they work together.<br />
<br />
[[Category:MarkLogic]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=Glossary&diff=70525Glossary2014-11-10T18:19:48Z<p>Aebrown: Simplify recent edits; remove grammatical errors.</p>
<hr />
<div>{{A2ZTOC}}<br />
== A ==<br />
;Active : Participating on a regular basis, such as attending meetings, observing the principles of the gospel, and accepting Church callings; Under current Church policy, those who attend meetings at least once a month.<br />
<br />
; AD - Active Directory<br />
: Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments. AD (also known as EAD) stores information and settings relating to an organization in a central, organized, accessible database.<br />
<br />
; AF - Ancestral File<br />
: A database containing family history information contributed by members of the Church and others from 1979 to 1999. The file contains millions of names linked in family groups and pedigrees. Ancestral File data may be accessed on FamilySearch.org.<br />
<br />
;Agent Bishop : The Bishop responsible for a meetinghouse when that building has multiple wards.<br />
<br />
; AJAX - Asynchronous JavaScript and XML<br />
: AJAX is a Web development technique for creating interactive Web applications. It exchanges small amounts of data with the server behind the scenes, so that the entire Web page does not have to be reloaded each time the user makes a change.<br />
<br />
; API - Application Programming Interface<br />
: An application programming interface (API) is a source code interface that a computer library provides to support requests to be made of it by a computer program.<br />
: [http://en.wikipedia.org/wiki/Application_programming_interface Wikipedia Definition]<br />
<br />
;Area : A geographical administrative region of many stakes and missions, usually including hundreds of thousands of members. Areas often cover many nations and are presided over by either a General Authority or an Area Authority Seventy.<br />
<br />
;Area Presidency : A Presidency of general or regional leaders who preside over an area of the Church.<br />
<br />
;Area President : A general or regional leader, a General Authority or Area Authority Seventy, who presides over an area of the Church.<br />
<br />
; ASA<br />
: Church-managed Cisco ASA 5505 firewall used for meetinghouse Internet connections.<br />
<br />
; ASCII<br />
: American Standard Code for Information Interchange. A standard definition employing characters that can be read without conversion.<br />
<br />
; ASE - Application Service Engineer<br />
<br />
; ASP - Active Server Pages<br />
: ASP is Microsoft's server-side script engine for dynamically-generated Web pages. Programming ASP Web sites is made easier by various built-in objects.<br />
: [http://en.wikipedia.org/wiki/Active_Server_Pages Wikipedia Definition]<br />
<br />
;Auxiliary Organizations : Organizations in a ward that do not include the priesthood quorums. These organizations include the Relief Society, Primary, Young Women, Young Men, and Sunday School.<br />
<br />
== B ==<br />
; B2B - Business-to-Business<br />
: Business-to-business (or B2B for short) is a marketing strategy that involves the transaction of goods or services between businesses (as opposed to relations between businesses and other groups, such as consumers or public administration).<br />
: [http://en.wikipedia.org/wiki/B2B Wikipedia Definition]<br />
<br />
; B2C - Business-to-Consumer<br />
: B2C (also business-to-customer) describes activities of commercial organization serving the end consumer with products and services.<br />
: [http://en.wikipedia.org/wiki/B2C Wikipedia Definition]<br />
<br />
; B2E - Business-to-Employee<br />
: B2E uses an intrabusiness network that allows companies to provide products and services to their employees. Typically, companies use B2E networks to automate employee-related corporate business.<br />
: [http://en.wikipedia.org/wiki/B2E Wikipedia Definition]<br />
<br />
;Baptism : The initial saving ordinance performed on those who have joined the Church or who have reached the age of eight, characterized by immersing the person completely in water. Baptisms therefore need to be recorded on Membership records.<br />
<br />
; BI - Business Intelligence<br />
: BI is a broad category of applications and technologies for gathering, providing access to, and anlyzing data for the purpose of helping enterprise users make better business decisions.<br />
: [http://en.wikipedia.org/wiki/Business_Intelligence Wikipedia Definition]<br />
<br />
;Bishop : A priesthood leader responsible for the spiritual and temporal welfare of a ward. Bishops preside over most ward functions and activities, interview members of their wards for worthiness, call members of their ward to callings within the ward and oversee efforts to provide for ward members unable to provide for themselves.<br />
<br />
;Block Schedule : A schedule of Sunday meetings that takes place in a three-hour period. The block schedule contains the sacrament meeting and Melchizedek Priesthood, Aaronic Priesthood, Relief Society, Young Women, Primary, and Sunday school meetings. See ''Handbook 2: Administering the Church'', section [http://lds.org/handbook/handbook-2-administering-the-church/meetings-in-the-church 18] for timing and sequence of meetings.<br />
<br />
; Blog - Web Log<br />
: A blog is a Web site where entries are made in journal style and displayed in reverse chronological order.<br />
: [http://en.wikipedia.org/wiki/Blog Wikipedia Definition]<br />
<br />
; BO - BusinessObjects<br />
: Enterprise software that is used for business intelligence.<br />
<br />
; Born in the Covenant (BIC) : A child who is born in the covenant does not have to be sealed to the parents. A child whose parents were sealed to one another in the temple before the child was born is BIC. A child born after the mother's sealing to her husband is canceled is not BIC. A child born after one of the parents is excommunicated is not BIC.<br />
<br />
;Branch : The smallest organized unit of the Church. A congregation not large enough to be made into a ward, or not in an area with enough members to make a stake.<br />
<br />
;Branch Clerk : A priesthood leader responsible for the administrative functions of a branch; generally managing the membership and financial records of a branch.<br />
<br />
;Branch President : The priesthood holder called and set apart to lead a branch.<br />
<br />
;Bulletin : (a k a Ward Bulletin or Sacrament Meeting Program) The printed listing of planned prayers, talks and other sacrament meeting elements passed out at the beginning of each Sacrament Meeting in most LDS congregations.<br />
<br />
== C ==<br />
;CAB : Church Administration Building<br />
<br />
;Calling : An office or assignment in the Church; An invitation to accept an office or assignment in the Church.<br />
<br />
; CCN - Church Communications Network<br />
: The Church's global network.<br />
<br />
;[[CDOL]] : Church Directory of Organizations and Leaders<br />
<br />
; CES - Church Educational System : The '''Church Educational System (CES)''' serves as the umbrella for all education programs of the Church, including Church-owned universities and colleges, institutes of religion, and seminary programs worldwide.<br />
<br />
;CFAR : ''Obsolete''. See CUBS.<br />
<br />
;CHI : ''Obsolete''. See Handbook.<br />
<br />
;CHQ : Church Headquarters<br />
<br />
;Church Handbook of Instructions : ''Obsolete''. See Handbook.<br />
<br />
;Clerk : A priesthood holder responsible for tracking financial and membership information and maintaining the associated records.<br />
<br />
;Clerk's Office : The room in an LDS meetinghouse or stake center that is used by the Clerks. The room where a unit's financial and membership transactions are made and the associated records are kept.<br />
<br />
;COB : Church Office Building<br />
<br />
;Confirmation : An ordinance performed after baptism whereby a person becomes a member of The Church of Jesus Christ of Latter-day Saints. This ordinance is performed under the direction of the bishop. One or more Melchizedek Priesthood holders place their hands on the person’s head and confirm them as a member of The Church of Jesus Christ of Latter-day Saints and use the wording “Receive the Holy Ghost.” May also pronounce a blessing as inspired by the Holy Ghost. Confirmation for eight-year-old [[members of record]] is performed at the baptism. Confirmation for converts is performed at a sacrament meeting on a Sunday following the baptism.<br />
<br />
;[[Consolidated Financial Statement]] : Monthly summary for the stake of all units' financial activity.<br />
<br />
;Convert<br />
: An individual nine years of age or older who is baptized and confirmed a member of the Church, or an eight-year-old whose parents are not members or are being baptized at the same time. Individuals under the age of eighteen must have the permission of both parents before being baptized.<br />
<br />
; COTS - Commercial Off-the-Shelf<br />
: COTS is a term for software or hardware products that are ready-made and available for sale, lease, or license to the general public. They are often used as alternatives to in-house development projects.<br />
: [http://en.wikipedia.org/wiki/Commercial_off-the-shelf Wikipedia Definition]<br />
<br />
;Court : ''Obsolete''. See Disciplinary Council<br />
<br />
; CRM - Customer Relationship Management<br />
: CRM is a broad term that covers concepts used by companies to manage their relationships with customers, including the capture, storage, and analysis of customer information.<br />
: [http://en.wikipedia.org/wiki/Customer_relationship_management Wikipedia Definition]<br />
<br />
;CUBS - Church Unit Banking Services<br />
: Introduced in 2010, a worldwide back office system used by administrative offices for financial record-keeping. Over time, all regions will transition from CFAR or LURBS to CUBS.<br />
<br />
;CUFS : [[Church Unit Financial Statement]] (Bank Statement) This has been replaced by the Unit Financial Statement.<br />
<br />
== D ==<br />
;Disciplinary Council : A council of local leaders and other priesthood holders held to review the inappropriate behavior of a Church member and to decide on appropriate consequences. Councils may also be reconvened after a period of time to see if a member has repented sufficiently to be restored to full fellowship. See chapter 6 of ''Handbook 1: Stake Presidents and Bishops'' for details.<br />
<br />
;District : A district is a smaller version of a stake, organized as the parent unit of branches instead of wards. A district may be organized when there are enough branches in an area to allow easy communication and convenient travel to district meetings. A district president presides over the district and reports to the mission presidency. <br />
<br />
;District Clerk : Person responsible for all clerical activities in a district.<br />
<br />
;District President : The district president presides over the district and is assisted by two counselors. The district president reports to and receives direction from the mission president.<br />
<br />
; DIZ - Development Integration Zone<br />
<br />
== E ==<br />
; EAD - Enterprise Active Directory<br />
: Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments (also known as AD) stores information and settings relating to an organization in a central, organized, accessible database.<br />
: [http://en.wikipedia.org/wiki/Active_Directory Wikipedia Definition]<br />
<br />
; EFD - Exploration Findings Document<br />
: This document is used to identify possible solutions for a specific project.<br />
<br />
;Elders Quorum : A quorum in the Church is a combination of a class, a fraternity of brethren, and a service organization. An elders quorum is a group of brethren in a ward consisting of up to 96 elders. After this number is reached, the quorum may be divided under direction of the stake president.<br />
<br />
;Elders Quorum President : The elders quorum in a ward is presided over by an elders quorum president and two counselors.<br />
<br />
;Endowment : Instruction received in the temple pertaining to the purposes and plans of the Lord in creating and peopling the earth and in exalting his children in the life to come.<br />
<br />
;Equalized Contribution : Refers to the support from the General Missionary Fund that results in each missionary serving from a specific country contributing the same amount irrespective of where in the world they serve.<br />
<br />
;ERC : Employment Resource Center<br />
<br />
; ERS - [http://providentliving.org/content/list/0,11664,1962-1,00.html Employment Resource Services]<br />
<br />
; EUP - End-User Productivity<br />
<br />
== F ==<br />
;Family History Center : A Family History Center is a branch facility of the Family History Library in Salt Lake City. It contains staff to help patrons identify their ancestors through the use of computer programs and microfilms and microfiche that may be ordered from the Family History Library.<br />
<br />
;Fast Offering : Fast offerings are funds freely given monthly by members of the Church to help the needy. As a general guideline members fast for two meals and contribute the cash equivalent of the cost of the two meals to the Church. The use of fast offerings is at the discretion of the bishop under the direction of the stake president.<br />
<br />
; FCH - Family and Church History Department<br />
<br />
;FHC : Family History Center<br />
<br />
; FHL - [http://www.familysearch.org/Eng/Library/FHL/frameset_library.asp Family History Library]<br />
<br />
;[[Financial Clerk]] : Person responsible for financial matters in the unit.<br />
<br />
; FIR - Facility Issue Reporting : The FIR system provides LDS Church leaders, building representatives, and facilities management groups the ability to report and review facility issues electronically. It uses a web interface to streamline reporting, viewing, and resolving of facility issues. <br />
<br />
;FIS : Old DOS-based local unit financial software that is no longer used. See [[MLS]] for current software.<br />
<br />
;FM Group : Facilities Management Group<br />
<br />
; FWIW - For What It's Worth<br />
<br />
== G ==<br />
;General Handbook of Instructions : ''Obsolete''. See Handbook.<br />
<br />
;[[Geo code]] : A code used to group members into geographic areas, usually to analyze how a unit might be divided.<br />
<br />
;GHI : General Handbook of Instructions. ''Obsolete''. See Handbook.<br />
<br />
; GIDS - Global Identity Services<br />
: Project to create LDS Sign-in.<br />
<br />
; GIS - Geographic Information System<br />
: A geographic information system (GIS) is a system for capturing, storing, analyzing, and managing data and associated attributes which are spatially referenced to the earth.<br />
: [http://en.wikipedia.org/wiki/Gis Wikipedia Definition]<br />
<br />
; GSC - [[Global Service Center]]<br />
: The GSC enables Directors of Temporal Affairs and Managing Directors to focus on their most important work by providing efficient transaction processing. They make gospel teachings, resources, and services directly and globally accessible in a self-service, scalable, affordable way. They help with questions and problems related to things such as IT support, Distribution Services, and clerk and leader issues. <br />
<br />
; GSD - Global Service Desk<br />
: Former name for the Global Service Center (GSC).<br />
<br />
== H ==<br />
;Handbook : The policy manual for administering the Church, consisting of two volumes: ''Handbook 1: Bishops and Stake Presidents'' and ''[http://lds.org/handbook/handbook-2-administering-the-church Handbook 2: Administering the Church]''.<br />
<br />
;High Priests Group : The stake president presides over the stake quorum of high priests, made up of all the high priests in the stake. The quorum is divided at the ward level into individual high priests groups. <br />
<br />
;High Priests Group Leader : The high priest group in a ward is presided over by a high priest group leader and two assistants. Under the bishopric’s direction, the high priests group leader coordinates temple and family history work in the ward.<br />
<br />
;[[Annual History|Historical Specialist]] : Clerk responsible for preparing the [[Annual_History|annual historical reports]].<br />
<br />
;Home Teacher : Home teachers are priesthood brethren who are assigned families at the ward level to visit monthly, to help and to strengthen. They are assigned by priesthood leaders.<br />
<br />
;Home Teaching : Home teaching is the responsibility of all Melchizedek Priesthood holders and of those who are teachers and priests in the Aaronic Priesthood. As part of their responsibility to watch over the members of the Church, home teachers visit their assigned families at least once each month to teach and strengthen them.<br />
<br />
== I ==<br />
; ICS - Information and Communications Systems Department<br />
<br />
; IGI - International Genealogical Index<br />
: A list of names of deceased persons for whom temple ordinances have been performed. The most current version is available on the [http://www.familysearch.org/ FamilySearch] Web site.<br />
<br />
; IMOS - Internet Mission Office System<br />
<br />
;Inactive : A term not officially used in the Church any more. See '''Less Active'''.<br />
<br />
;Inactivity<br />
<br />
;[[Individual Ordinance Summary]] : A form that contains most of the information on a [[Membership Records|Membership Record]] that can appropriately be given to a member.<br />
<br />
;Investigator<br />
<br />
;[[Individual Ordinance Summary|IOS]] : Individual Ordinance Summary<br />
<br />
; IP - Internet Protocol<br />
: An Internet protocol is a unique address that devices use to identify and communicate with each other on a computer network utilizing the Internet protocol standard (IP).<br />
: [http://en.wikipedia.org/wiki/IP_address Wikipedia Definition]<br />
<br />
; IROP - Internal Record Of Purchase : A document used to record internal Church purchase transactions. The most common IROP transactions for Church units are those made at LDS Distribution Services online through the LDS Store, in person, or by telephone. Unit IROPs are transmitted electronically through MLS.<br />
<br />
== J ==<br />
; JSMB - [http://www.lds.org/placestovisit/location/0,10634,1872-1-1-1,00.html Joseph Smith Memorial Building]<br />
<br />
<br />
== K ==<br />
; KB - KnowledgeBase<br />
: A database of articles that help individuals resolve issues.<br />
<br />
== L ==<br />
;Less Active : Participating in Church on an irregular basis, which may vary from coming to a few things a year to never coming at all. Members who attend meetings less than once a month are considered less active.<br />
<br />
;[[Priesthood Line of Authority|Line of Authority]] : The chain of ordinations for a priesthood holder showing who ordained him to his current office, who ordained the ordainer, and so on back to Jesus Christ.<br />
<br />
;LUAAT : Local Unit Area Auditor Trainer<br />
<br />
;[[Budget Allowance|LUBA]] : Local Unit Budget Allowance<br />
<br />
;LURBS : Local Unit Receipting, Reporting, and Banking System - A back office system used by administrative offices for financial record-keeping outside of North America. It provides various reports for local units, including a [[Ward/Branch Monthly Financial Report|monthly financial report]].<br />
<br />
;[[Administrative office#Local Unit Support|LUS]] : Local Unit Support Group - Located in Salt Lake City, Utah, provides support for priesthood leaders in Canada and the United States.<br />
<br />
;[[LUWS]] - Local Unit Web Site<br />
: Also called the "Classic Ward and Stake Website," these sites were retired at the end of 2012 and replaced by various tools on LDS.org.<br />
<br />
== M ==<br />
;Member : A member of the Church of Jesus Christ of Latter-day Saints is a person eight years old or older who has been baptized and confirmed a member of the Church. <br />
<br />
;Membership : The state of being a member of the Church of Jesus Christ of Latter-day Saints, as evidenced by records kept at Church headquarters and in the local unit's MLS. Records are also created for children of members of the Church who are under eight years old; however, these children are not considered members until eight years old, when they are baptized and confirmed.<br />
<br />
;[[Membership Clerk]] : Person responsible for maintaining membership records on the members of a unit.<br />
<br />
;[[Membership Records|Membership Record]]<br />
<br />
;MIS : Old DOS-based local unit membership software. See [[MLS]] for current software.<br />
<br />
;[[MLS]] - Member and Leader Services (membership and financial software)<br />
: MLS software is for use by unit leaders, clerks, auxiliary and quorum leaders, and secretaries at both the ward and stake levels. MLS is designed to make Church record-keeping easier and more efficient.<br />
<br />
;MRN : Membership Record Number<br />
<br />
;[[Administrative office|MSR]] : Membership and Statistical Records Department - the Church department that is commonly known to clerks as the [[administrative office]].<br />
<br />
== N ==<br />
;[[NQI]] : Non-quality item - a financial transaction that is not complete after 2 months.<br />
<br />
; NOB - North Office Building<br />
: The building that is directly north of the Church Office Building and was previously called the Data Center.<br />
<br />
<br />
== O ==<br />
;Office : A position in the priesthood (such as priest, elder, and high priest) that has attached to it certain duties, responsibilities, and rights.<br />
<br />
;Ordinance : A ceremony performed by the priesthood for a specific purpose. Examples are baptism/confirmation, ordination to the priesthood, and temple sealings. Some are saving ordinances and must be received by members in order to be saved, such as baptism/confirmation. Others may not necessarily be saving ordinances, such as a child blessing.<br />
<br />
;Ordination : The bestowal of the priesthood and/or a priesthood office. For example, when a male member is ordained to the office of elder, he receives the Melchizedek Priesthood and is ordained to the office of elder within the Melchizedek Priesthood. Later in life, if he is ordained to the office of high priest, he does not receive the Melchizedek Priesthood again, but is ordained to the office of high priest within the Melchizedek Priesthood. Both examples are considered ordinations.<br />
<br />
== P ==<br />
; PAF - Personal Ancestral File<br />
: A Church-produced computer software program that enables people to compile and organize their genealogy on their personal computers. PAF can help members identify ancestors and prepare their names for temple work.<br />
<br />
;Patriarch : Patriarch is an office in the Melchizedek Priesthood, and not a calling. A patriarch is recommended by the stake president, sustained in stake conference or stake priesthood meeting, and ordained by the First Presidency or one of the Twelve Apostles or (with written permission from the Twelve) the stake president. Patriarchs give personal blessings to members of the stake (see Patriarchal Blessing).<br />
<br />
;Patriarchal Blessing : A blessing given to a member by the patriarch of his or her stake. After the member obtains a recommendation from the bishop, he or she is given a blessing in which the patriarch may give the member's lineage, list weaknesses and strengths, pronounce advice from the Lord concerning the member's future, and any other direction or guidance.<br />
<br />
; PC - Personal Computer<br />
<br />
; PDD - Project Definition Document<br />
<br />
;PEC : Priesthood Executive Committee<br />
<br />
;PEF : Perpetual Education Fund<br />
<br />
;Perpetual Education Fund<br />
<br />
;Personal Priesthood Interview : ''Obsolete''. See Priesthood Interview<br />
<br />
;Physical Facilities Representative : A local priesthood holder responsible for the physical status of a meetinghouse.<br />
<br />
;PI : Priesthood Interview<br />
<br />
; PIX<br />
: Church-managed Cisco PIX firewall used primarily for FHC Internet connections.<br />
<br />
;PLT : Priesthood Leadership Travel<br />
<br />
;PPI : Personal Priesthood Interview. ''Obsolete''. See Priesthood Interview<br />
<br />
;Presiding Bishop : A General Authority of the Church. The Presiding Bishop and his counselors serve under the direction of the First Presidency to administer the temporal affairs of the Church.<br />
<br />
; PRF - Pedigree Resource File<br />
: A file of lineage-linked data submitted by both members and nonmembers through the [http://www.familysearch.org/ FamilySearch] Web site. The master index is available online and the entire file is available on CD. The Pedigree Resource File is the successor to the Ancestral File.<br />
<br />
;Priesthood Executive Committee<br />
<br />
;Priesthood Interview : A private stewardship meeting between a priesthood leader and a person who reports to him<br />
<br />
== Q ==<br />
;[[Quarterly Report]] : A report of member attendance and other key statistics submitted by wards to the stake and the Church each quarter<br />
<br />
<br />
== R ==<br />
;Recommend<br />
<br />
;Record<br />
<br />
;Record Keeping<br />
<br />
;REFIS<br />
<br />
;Relief Society : The women's organization of the Church, organized by Joseph Smith in 1842, dedicated to "the exercise of all benevolent purposes." The Relief Society provides Sunday gospel instruction, other Relief Society meetings, visiting teaching, and welfare and compassionate service opportunities.<br />
<br />
;RS : Relief Society<br />
<br />
; RSS - Really Simple Syndication<br />
: RSS is a Web-feed format that is used to publish frequently updated digital content to consumers who use RSS aggregators to notify them of updates.<br />
: [http://en.wikipedia.org/wiki/RSS Wikipedia Definition]<br />
<br />
== S ==<br />
; SAV - Symantec Anti-Virus : An anti-virus software formerly used on Church-owned computers, such as those used in stakes and wards. All computers should now have the Sophos anti-virus software.<br />
<br />
; SA - Single Adult<br />
: A single member above the age of 30. See also YSA.<br />
<br />
; SDK - Software Development Kit<br />
: SDK is typically a set of development tools that allows a software engineer to create applications for a certain software package, software framework, hardware platform, computer system, video game console, operating system, and more.<br />
: [http://en.wikipedia.org/wiki/Software_development_kit Wikipedia Definition]<br />
<br />
; SEO - Search Engine Optimization<br />
<br />
; SERP - Search Engine Results Page<br />
<br />
;Set Apart<br />
<br />
;SFS : ''Obsolete''. See Consolidated Financial Statement.<br />
<br />
; SOAP - Simple Object Access Protocol<br />
: A protocol for exchanging XML-based messages over a computer network, normally using HTTP.<br />
: [http://en.wikipedia.org/wiki/SOAP Wikipedia Definition]<br />
<br />
; Sophos Anti-Virus : An anti-virus software currently used on Church-owned computers, such as those used in stakes and wards.<br />
<br />
; SORT<br />
: An internal conference hosted by ICS for technical Church employees.<br />
<br />
; SRD - Solutions Requirement Document<br />
: The SRD is used to identify the business requirements and business case for a proposed technology project.<br />
<br />
; SSH - Secure Shell<br />
: SSH is a communication system that uses public-key cryptography to establish a secure connection between remote computers.<br />
: [http://en.wikipedia.org/wiki/Ssh Wikipedia Definition]<br />
<br />
;Stake<br />
<br />
;[[Stake Clerk]] : Person responsible for all clerical activities in a stake.<br />
<br />
;Stake President : The stake president presides over the stake and is assisted by two counselors. The stake president reports to and receives direction from the presidency of the Seventy or from the Area President.<br />
<br />
;[[Stake Technology Specialist]] : Person responsible for the technology assets of the stake and each ward in the stake.<br />
<br />
;[[Statistical Clerk]] : Person responsible for collecting and preparing the [[Quarterly Report]].<br />
<br />
== T ==<br />
<br />
;[[Desktop Management Software|TEM]] - Tivoli Endpoint Manager <br />
: Replaced LANDesk as the official software CHQ uses to centrally manage and secure the global fleet of Church-owned computers. TEM will install and utilize the BES Client service.<br />
<br />
;Temple<br />
<br />
;Temple Ordinances<br />
<br />
;Temple Recommend<br />
<br />
;Temporal<br />
<br />
;Tithing<br />
<br />
;Tithing Settlement<br />
<br />
<br />
== U ==<br />
;Unit : A congregation or other function in the Church that is responsible for its budget. Wards, Stakes, Branches, Districts, Family History Centers, etc., are all examples of Units.<br />
<br />
;Unit Financial Statement : the Unit Financial Statement has replaced the old Church Unit Financial Statement.<br />
<br />
== V ==<br />
;Visiting Teacher<br />
<br />
;Visiting Teaching<br />
<br />
; VoIP - Voice Over Internet Protocol<br />
: The technology that allows voice communication (such as telephone) over a network instead of through traditional phone lines. The Church has deployed VoIP in several locations indlucing BYU, the North Office Building, the Triad Center, and Ghana.<br />
: [http://en.wikipedia.org/wiki/Voip Wikipedia Definition]<br />
<br />
; VPN - Virtual Private Network<br />
: VPN is a private communications network often used within a company, or by several companies or organization, to communication confidentially over a publicly accessible network.<br />
: [http://en.wikipedia.org/wiki/Vpn Wikipedia Definition]<br />
<br />
<br />
== W ==<br />
;Ward<br />
<br />
;Ward Budget<br />
<br />
;[[Ward Clerk]] : Person responsible for all clerical activities in a ward.<br />
<br />
;Ward Council<br />
<br />
;Ward Welfare Committee<br />
<br />
;Welfare<br />
<br />
;Welfare Services<br />
<br />
<br />
== Y ==<br />
;YM - Young Men<br />
:Single male members between the ages of 12-18.<br />
<br />
;YSA - Young Single Adult<br />
:A single member between the ages of 18-30. See also SA.<br />
<br />
;YW - Young Women<br />
:Single female members between the ages of 12-18.<br />
<br />
[[Category:Help]]</div>Aebrownhttps://tech.churchofjesuschrist.org/wiki/index.php?title=User:Aebrown&diff=70503User:Aebrown2014-11-03T16:13:07Z<p>Aebrown: Update callings</p>
<hr />
<div>__NOTOC__<br />
== Alan Brown ==<br />
=== Forum/Wiki ===<br />
* Moderator, [http://tech.lds.org/forum LDSTech Forums] (User [http://tech.lds.org/forum/member.php?u=1684 aebrown])<br />
* Administrator, [[Main Page|LDSTech Wiki]] (User [[User:Aebrown|Aebrown]])<br />
<br />
=== Contact ===<br />
[[Special:EmailUser/Aebrown|Send me email]].<br />
<br />
=== Location ===<br />
Sandy, UT<br />
<br />
=== Interests ===<br />
.NET and Java development<br />
<br />
=== Occupation ===<br />
Software Engineer for the [http://www.FamilySearch.org Church Family History Department]<br />
<br />
=== Current callings ===<br />
* 2014-present: Bishopric counselor<br />
<br />
=== Previous callings ===<br />
* 2012-2014: Stake Clerk<br />
* 2004-2014: Stake Web Site Administrator<br />
* 1997-2014: Stake Technology Specialist<br />
* 2006-2012: Stake Financial Clerk<br />
* 2001-2012: Assistant Stake Clerk<br />
* 1996-2001: Ward Financial Clerk<br />
* 1992-1994: BYU High Councilor with responsibility for clerks and computers in 12 wards<br />
* 1986-1991: Ward Financial Clerk<br />
* 1985-1988: Stake Auditor<br />
* 1982: BYU Ward Membership Clerk<br />
<br />
== Sandboxes ==<br />
[[User:Aebrown/Sandbox|My Sandbox]]</div>Aebrown