##ForeverScape## ###Artwork So Large You Need Special Software Just To See It###

Two football fields long, standing 12 stories tall, it is ongoing...

###Live Demo: http://staging.foreverscape.com###

Over five years ago a hand-drawn illustration began, one so large that only machines could see it. The paper alone weighs over twenty pounds! You'd think Google Maps could at chart it, but in fact the periodic nature and every page connecting left-to-right breaks tile-engine logic. This open-source project is an invitation to create your own exploration engine, a diving-off point into the larger-than-life reality known as the ForeverScape. The core is pure javascript wrapped in AngularJS for the user interface components. Every hand drawn page is individually scanned.

The plan is to have a fully fledged geography system with drag and drop comment markers and goto-any-point. This underlying API will pave the way for the ultimate scavenger hunt game, or whatever you can dream of.

“It Goes Until I do”

Read More:

• Sketching Infinity
• Sketch Exchange
• Artist Profile
• The Soon to be Deprecated Website

###Licensing:###

Any display of content directly from or derived from the ForeverScape artwork must be accompanied with the text "ForeverScape" on or in the same vicinity of the display apparatus, NOT JUST IN SOURCE CODE. The minimum font size for the text "ForeverScape" must be at least 7% of the of height or width (whichever is greater) of the screen size of the artwork presented and must link to http://foreverscape.com?source={{ URL of your company or app}} in a browser on the device. This applies to any single image, cropping of a single image or assembly of multiple images. If your host is found to be pulling more than 500,000 CDN responses, please contact ForeverScape LLC to split the Amazon CloudFront bill or make arrangements to purchase redistribution rights. Failure to comply will lead to blocking your hosts.

You can create commercial software products using this API and the images in the CDN hosted by ForeverScape, LLC as long as you adhere to the restrictions above. Failure to comply will be prosecuted to the fullest extent of the law, including trademark and copyright law. Redistribution of images is strictly prohibited and granted only by the Artist in writing. Reproduction of images, in the form of digital tranfer over network, print, etching, engraving, stamping, and other mediums is strictly prohibited.

Code is distributed under MIT license.

###Usage:###

There are several ways to use this library

   1. Add your own components to the application directory (or other directory of choice)
        

  2. Include `Core` Directory in your project
       
        - copy the core directory to your application
        - inject the following modules

  3. Standalone Page (Good for viewing the Foreverscape)
        - Compile using `Compiling` directions below
        - host the application on your server of choice
        - run index.html in your browser

###Compiling###

1. install node
2. install grunt
3. install node modules with command npm install
4. run grunt comiple to compile to the compiled directory

##TODO: Stories + Features##

The biggest thing we're struggling with is how to organize your angular app to be reusable. Creating a single corporate app is easy, but what if you want all the functionality of a whole app, but as a reusable module (both from a maintainability standpoint and an organisational one)? Should we use Polymer? http://www.polymer-project.org/ Dev: http://dev.foreverscape.com

Items without developing tag are future stories. Developing tags are actively in development.

Top Refactoring Tasks

• abstract the touch/gesture stuff out of the tile engine, add callback mechanisms so multiple controllers can use it

basics

• Repository

• Setup staging server

• Setup New Database + API Server Nope. Let's use AWS via JS SDK directy for backendless client

• Deployment/Build scripts

• setup dev server

• set Cloudfront to pull static content from staging and live server, make the minified index pull statics from CDN, not relative path. Make grunt task to auto-increment builds so that statics get deployed to new version directories

• Tile Engine

  • mobile layout works for iOS
  • mobie layout works for android
  • works in firefox had to workaround for zoom
  • works in IE 10+ only tested so far
  • works in chrome
  • Place Marker developing
  • Scroll To Marker developing
  • commenting API developing
  • snap a screenshot and share on Facebook wall / twitter --> deploy to CDN or S3 (needs JS SDK auth)
  • autoplayback in any direction developing
  • fullscreen mode
  • double-tap [touch] to zoom back to default <span style="color"developing
  • pinch [touch] to set zoom tested ios, android need to test mobile IE
  • perhaps use AWS identity services + DynamoDB for location comment engine
  • widget player project that people can "embed" into blog, website etc.

• Website Overhaul Design

  • Fonts Etc
  • Layout Templates
  • pages + content
  • SEO grunt script to redirect to hashed pages

• Integrate products sales

  • top banner area
  • sales page
  • snap a capture and send a physical postcard with on demand print API

GAME Design

- use AWS identity services
- Social media API + login
- Game API
- Game CMS
- setup Game Staging site?? nah, just make "game mode" on site when logged in
- Mobile Targets: Use Appcellerator Titanium or PhoneGap???
- Mobile platform specific code
- Publish Targets Android
- Publish Target IOS

####FU Angular ####

While Angular is great for building UI and two-way data binding, this overhead is bad for the actual tile engine. Looking at mobile performance, we abandon the Angular convention of ng-repeat for the actual tile engine component. UI and other interfaces are fine, but the tiling needs to be super-efficient, we can't have two-way binding and $digests() going on all the time.data available. Ping me if you have a good organization strategy for angular reuse.