LDSTechForumProjects

Church Historical Timeline code details

Church Historical Timeline Index edit
This article is a stub. You can help LDSTech by expanding it.
To Do: Write something that will let non-developers and developers know how they can get started with the project

Download the Project

  1. Follow these instructions: Create LDS Java Stack Project

Current Timeline Code Version: timeline2.3 (FYI: the MIT SIMILE|Timeline project has recently moved from MIT to Google.)

Become Familiar With the Community Best Practices

Community Development Best Practices edit

The Church Historical Timeline Files

  • index.html - LDS Timeline page (the entire application is comprised of a single HTML page)
  • lds.xml - data file containing LDS events in XML format
  • timeline-api.js -
  • timeline-bundle.js -
  • timeline-bundle.css -
  • ext -
    • geochrono -
    • planning -
  • images -
  • scripts -
    • 'ext -
    • l10n -
    • classicTheme.js -
    • decorator.js -
    • detailed-painter.js -
    • ether-painters.js -
    • ethers.js -
    • labellers.js -
    • original-painter.js -
    • overview-painter.js -
    • setupHighlightControls.js - controls highlighting (highlightIcon, highlightTape, etc.)
  • styles - folder containing Cascading Style Sheets (CSS) that control the look & feel of the timeline
  • timeline_ajax - folder containing files that enable AJAX features
    • ethers.css - (styles/ethers.css) stylesheet that controls the appearance of timeline events (duration tape, background colors for each band)

The OLD Church Historical Timeline Files

  • index.html - the main HTML page that renders the timeline. Most of the layout of the timeline is controlled by this page: title; location of the controls (filter & highlighting for lds & world); location of the event counts (lds & world); location of the history bands (lds events summary, lds events content, world events content, world events summary)
  • lds.xml - contains LDS historical events in an xml format
  • world.xml - contains world historical events in an xml format
  • api - folder containing javascript, css, and other support files
    • bundle.js - scripts/bundle.js: loads XML; sets highlight colors (core of layout engine)
    • bundle.css -
    • examples.js - displays the filter and highlighting controls and event counts
    • labellers.js -
    • timeline.js - displays the timeline bands (2 summary bands and 2 event bands)
    • timeline-api.js -
    • ext - folder
      • geochrono - folder (contains several files & subfolders)
      • planning - folder (contains several files & subfolders)
        • scripts - folder
          • l10n
          • ether-painters.js
          • labellers.js
          • planning.js
          • units.js
        • planning-api.js
    • images - folder (contains 33 images used in the application)
    • scripts - folder containing JavaScript code that enables the functionality of the timeline
      • ext - folder
        • japanese-eras.js -
      • l10n - folder (contains several language folders - cs, de, en, es, fr, it, ru, se, vi, zh)
      • util - folder
        • data-structure.js -
        • date-time.js -
        • debug.js -
        • dom.js -
        • graphics.js -
        • html.js -
        • platform.js -
        • xmlhttp.js -
      • decorators.js -
      • ether-painters.js -
      • ethers.js -
      • labellers.js -
      • layouts.js -
      • painters.js -
      • sources.js -
      • themes.js -
      • timeline.js -
      • units.js -
    • styles - folder containing Cascading Style Sheets (CSS) that control the look & feel of the timeline
      • ethers.css -
      • events.css -
      • styles.css -
      • timeline.css -
    • util - folder containing JavaScript utility functions
      • data-structure.js -
      • date-time.js -
      • debug.js -
      • dom.js -
      • graphics.js -
      • html.js -
      • platform.js -
      • xmlhttp.js -
This page was last modified on 7 April 2010, at 11:24.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.