signagestudio web lite
JavaScript HTML CSS TypeScript PHP Ruby
Failed to load latest commit information.
_assets added support for empty scenes on special MIME Jul 22, 2016
_collections added support for empty scenes on special MIME Jul 24, 2016
_common rewrite history Jul 11, 2016
_controllers give option to hide create account as well as in priv/hybrid expose a… Jul 15, 2016
_doctheme rewrite history Jul 11, 2016
_lang rewrite history Jul 11, 2016
_libs added support for empty scenes on special MIME Jul 24, 2016
_models rewrite history Jul 11, 2016
_templates rewrite history Jul 11, 2016
_utils fixed bug in fq slider css length Jul 28, 2016
_views fq changed line name Jul 27, 2016
examples rewrite history Jul 11, 2016
node_modules rewrite history Jul 11, 2016
temp fq changed line name Jul 27, 2016
typings give option to hide create account as well as in priv/hybrid expose a… Jul 15, 2016
.gitignore rewrite history Jul 11, 2016
Declarations.js give option to hide create account as well as in priv/hybrid expose a… Jul 15, 2016
Declarations.js.map rewrite history Jul 11, 2016
Declarations.ts rewrite history Jul 11, 2016
Elements.js fq changed line name Jul 27, 2016
Elements.js.map fq changed line name Jul 27, 2016
Elements.ts fq changed line name Jul 27, 2016
Events.js give option to hide create account as well as in priv/hybrid expose a… Jul 15, 2016
Events.js.map rewrite history Jul 11, 2016
Events.ts rewrite history Jul 11, 2016
LICENSE rewrite history Jul 11, 2016
README.md fixed bug in fq slider css length Jul 28, 2016
StudioLite.js fixed fq port Jul 20, 2016
favicon.ico rewrite history Jul 11, 2016
gulpfile.js cleaned up dist of studiolite.html Jul 19, 2016
init.js rewrite history Jul 11, 2016
package.json fixed bug in fq slider css length Jul 28, 2016
redirect.html rename redirect to studiolite.html in server release script Jul 20, 2016
server.js rewrite history Jul 11, 2016
signagestudio_web-lite.iml rewrite history Jul 11, 2016
studiolite.html fixed bug in fq slider css length Jul 28, 2016
style.css fixed bug in fq slider css length Jul 28, 2016
style_dark.css rewrite history Jul 11, 2016
tsconfig.json rewrite history Jul 11, 2016
uploadVerFiles.bat rewrite history Jul 11, 2016

README.md

by digitalsignage.com

   _____ _             _ _       _      _ _       
  / ____| |           | (_)     | |    (_) |      
 | (___ | |_ _   _  __| |_  ___ | |     _| |_ ___ 
  \___ \| __| | | |/ _` | |/ _ \| |    | | __/ _ \
  ____) | |_| |_| | (_| | | (_) | |____| | ||  __/
 |_____/ \__|\__,_|\__,_|_|\___/|______|_|\__\___|
                                                  
                                                                                                                            

StudioLite, Digital Signage for the rest of us

current version: 1.5.102 dev-build


StudioLite is an open source, 100% FREE, Digital Signage platform that was designed with ease of use in mind. With StudioLite anyone can have a Digital Signage solution that is entirely customizable. Take the source code, modify it, brand it and build a product that's right for you and your customers. Best of all, you will take full advantage of the world's most popular Digital Signage cloud so you don't have to worry about backend programming or even setup a server, it's all done for you using the mediaCLOUD.

  • Based on the poplar SignageStudio Pro ( [MediaSignage]: http://www.DigitalSignage.com )
  • Connected to a private mediaSERVER or the public free mediaCLOUD
  • 100% open source based on GNU V3 license
  • Contributors are welcome, fork, modify and send pull requests

Links:

Technical data:

  • Build on top Backbone js with a clean MV* design
  • Includes jQuery, Underscore as base libs
  • Powered by Bootstrap using responsive design for phones, tablets and desktops
  • Runs with require js for on demand modulated loading
  • Driven using Soap API and includes Helper SDK
  • Uses a local msdb (database) through SDK for offline work
  • Available as obfuscated and raw source
  • Support available through the MediaSignage support forum

Installation:

StudioLite can be downloaded directly from GitHub, or (recommended) is to install it through node.js and npm. With node.js and npm you will be able to easily update to the latest version of StudioLite as well as take advantage of the the built in Express server that is included with StudioLite.

Option 1 (recommended):

  • Download node.js (all major operating systems supported): http://nodejs.org/
  • Install node.js
  • open a terminal (Mac / Linux) or command prompt (windows)
  • switch to node.js directory and run: npm install studiolite -g --prefix ./
  • change directory to: cd ./lib/node_modules/studiolite
  • run the command node server.js if you wish to use the bundled express server
  • you may also host it directly on your own web server if you like, such as apache or IIS
  • open browser and point it to [YOUR_IP]:8080/_studiolite-dev/studiolite.html

Option 2:

  • Download the zip from GitHub
  • On your web server (i.e.: apache, IIS) create a root directory and name it: _studiolite-dev
  • Unzip all files into _studiolite-dev directory
  • open browser and point it to [YOUR_IP]/_studiolite-dev/studiolite.html
  • IMPORTANT: make sure _studiolite-dev is in the root of web server

Main html files

  • If you are using the mediaCLOUD or this repo on GithHub, to host this project on your own server you will use: studiolite.html to load the app
  • If you are using a private or hybrid mediaSERVER you will find in your server distribution the file: index.html to load the app

Updates:

If you used npm install studiolite updating is as easy as switching to your node directory and typing node update studiolite to get the latest release If you downloaded directly from GitHub, you will need to re-download the zip file and expand over your existing installation.

npm registry: https://www.npmjs.org/package/studiolite

Customization:

Keep in mind the SignageStudio lite as well as its related SDK Pepper are often released with new updates, so you will lose any changes you make to your code if you overwrite it with our release builds.

To overcome this you can follow these guidelines:

  1. Always be sure to override files and not modify the original source file. This is true for both CSS and JavaScript code. Simply load your version of the CSS after ours to apply your latest changes. HTML files can be diffed (see below).
  2. Our code base is modulated and uses 100% object oriented design pattern. This allows you to sub class (aka inherit) from our classes and make your applied changes (use _.extend to mixin).
  3. You can also use pre-processor scripts which replace code segments automatically using directives.
  4. And finally, even while following steps 1-3 you may find that your code is broken due to design changes in the original repository. That’s when GitHub comes to the rescue. When your fork the source repository, you can always merge the tree onto your forked project. Use source control diff tool to merge the changes into your code and resolve any conflicts.

With the above steps you can ensure that your source code is fully customizable while still keeping it synchronized with our ongoing development efforts. And if you built something wonderful, just send us a pull request so we check it out. If we like what you did we we will merge it into our code base, so you will always receive it when you fetch our changes.

If you are not a developer you can hire professional, inexpensive help from sites like oDesk and Freelancer. Just post you are looking for a JavaScript, jQuery, Backbone experienced developer.

License: