First commity

.project

@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>Brightcove</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+		<buildCommand>
+			<name>com.aptana.ide.core.unifiedBuilder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
+	</buildSpec>
+	<natures>
+		<nature>com.aptana.projects.webnature</nature>
+	</natures>
+</projectDescription>

README.markdown

@@ -0,0 +1,68 @@
+# Samsung sample Brightcove video player #
+
+**By [Brightcove](http://brightcove.com) and [A Different Engine](http://adifferentengine.com)**
+
+## Overview: ##
+This template provides a jump-start to getting your Brightcove content published on Samsung devices. This is not meant to be a drop in application.To begin publishing with this application, you need the following:
+
+_This is not meant to be a plug and play solution. Its meant to jump start developers on the Samsung Platform_
+
+For more information check out the additional readme in js/Common/enginelite/README.markdown for more details on the associated framework.
+
+_Neither Brightcove or A Different Engine Ensure this code to be bug free!_
+
+### Skills Needed ###
+The expectation is that this library is meant for developers familiar with existing front end web technologies. Users should be proficient in the following:
+
+* HTML
+* Javascript 
+* CSS
+
+In particular we use a few, common open source Javascript libraries. These include:
+
+* [Jquery](http://jquery.com/)
+* [Underscore](http://documentcloud.github.com/underscore/)
+* [Backbone](http://documentcloud.github.com/backbone/)
+
+
+### A Note on Local Setup
+
+So this framework will support development in the browser, however browsers do not allow for the type of cross domain AJAX requests required for these types of apps (This is a security feature which the CE Devices relax).  In order to handle these we bounce our AJAX requests off of a local proxy written in PHP (See proxy.php). This means when you're writing your apps if you want to develop in browser (which we find desireable because of the more advanced debugging tools) this app needs to run in a "hosted" environment which supports php. This php proxy is not intended for use in production environments without additional security controls.
+
+###Get your accounts and development environment ready###
+
+* A Brightcove account (http://www.brightcove.com)
+Sign up for an account for the Video Platform on Brightcove. Select the account that suits your content delivery needs. 
+* A Samsung device or the Samsung SDK (PC ONLY) (http://www.samsungdforum.com/)
+Sign up for an account and download the Samsung Smart TV SDK.  
+* A Modern Web Browser Please note that the sample Brightcove video player is designed to work in modern versions of Firefox, Chrome and Safari for ease of development. Generally video playback in H.264/MP4 will not work on Firefox but generally has worked in Chrome.
+* A Local Web Server if browser testing is required.
+
+
+
+###Getting your content ready###
+
+* Get a Brightcove customer token with read and URL access. This can be found under Account Settings > API Management
+* Create a custom Brightcove player using one of the multi-playlist player templates. Make note of the ID number of this player. You will need it for configuration settings.
+* Create at least one playlist for your Roku content. 
+    Each playlist will appear as a category section in the Roku Application. 
+
+###Configure the app###
+* config.xml is documented in the [Samsung user guide](http://www.samsungdforum.com/Guide/View/Developer_Documentation/Samsung_SmartTV_Developer_Documentation_3.0/Getting_Started/Application_Development_Process/Implementing_Your_Application_Code/Coding_Your_JavaScript_Application), but you want to note the path to the icons for the application, the width and height of your target resolution, as well as the name of your application.
+* application.js: There are Brightcove Configuration settings at the top of this page 
+    + customerToken: your Brightcove customer token with read and URL access
+    + playerID: this is the id of the custom player you created for your Samsung content
+
+### Skin the app ###
+* Icons
+    + Player Icons: There are two sets of navigation icons for use, located in /images/navbar/black and /images/navbar/white. You can create new icons if you like as well. These are referenced in the control hints container on index.html
+    + Application Icons: Application icons used in the Samsung Application manager are located in the /images/icons directory. These must be transparent png files. These are documented in the [Samsung user guide](http://www.samsungdforum.com/Guide/View/Developer_Documentation/Samsung_SmartTV_Developer_Documentation_3.0/Getting_Started/Application_Development_Process/Implementing_Your_Application_Code/Coding_Your_JavaScript_Application)
+* Interface Images:
+    + loading.png (/images/[resolution]/loading.png): This image appears as the application is loading. It is loaded in index.html and can be changed easily.
+    + down_arrow.png, left_arrow.png, right_arrow.png, up_arrow.png (/images/[resolution]/): these images control the main navigation bar and can be remade to your needs.
+    + logo.png (/images/[resolution]/logo.png): replace this image with your company logo
+    + navbar_back.png (/images/[resolution]/navbar_back.png): this image appears behind the navigation controls on the video player page.
+    + overlay.png (/images/[resolution]/overlay.png): This full-screen image provides the background for the navigation page.
+    + pagingback.png (/images/[resolution]/pagingback.png): This image appears behind the paging element on the navigation page (i.e. 1 of 5)
+    + playicon.png (/images/[resolution]/playicon.png): This image appears on rollover of a video thumbnail.
+    + videoheader.png (/images/[resolution]/videoheader.png): This image appears at the top of the video player. Note: This image has a built-in progress bar.

config.xml

@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<widget>
+    <ThumbIcon>images/icons/App_106.png</ThumbIcon>
+    <BigThumbIcon>images/icons/App_115.png</BigThumbIcon>
+    <ListIcon>images/icons/App_85.png</ListIcon>
+    <BigListIcon>images/icons/App_95.png</BigListIcon>
+	<category itemtype="string"></category>
+	<type itemtype="string">user</type>
+	<cpname itemtype="string"></cpname>
+	<cplogo itemtype="string"></cplogo>
+	<cpauthjs itemtype="string"></cpauthjs>
+	<ver itemtype="string"></ver>
+	<mgver itemtype="string"></mgver>
+	<fullwidget itemtype="boolean">y</fullwidget>
+	<srcctl itemtype="boolean">y</srcctl>
+	<ticker itemtype="boolean">n</ticker>
+	<childlock itemtype="boolean">n</childlock>
+	<audiomute itemtype="boolean">n</audiomute>
+	<videomute itemtype="boolean">n</videomute>
+	<dcont itemtype="string">y</dcont>
+	<widgetname itemtype="string">Brightcove Sample App</widgetname>
+	<description itemtype="string"></description>
+	<width itemtype="number">960</width>
+	<height itemtype="number">540</height>
+	<author itemtype="group">
+		<name itemtype="string"></name>
+		<email itemtype="string"></email>
+		<link itemtype="string"></link>
+		<organization itemtype="string"></organization>
+	</author>
+</widget>