Well, it is an example in itself. Dependencies are in /public/javascript/lib, and the core in /public/javascript/src/base.
The main page is in /public/templates/index.html, and inside that .html every route starts with /assets/ because I use it with Play framework. You can change the routes to /public/ or whatever.
In /public/javascript/src/screens you can find two basic screens which point to each other, and in /public/templates/ there are 2 .haml files corresponding to each screen. In /public/locals are the locals for each screen.
You could simply publish those files in a way that we can open with our browsers without having to download the project, and link it in the readme. This would be worth a thousand words :)
Some example code/tutorials/howto or common use cases would be really useful to understand what your project is used for...
And saying it is an example in itself, clearly isn't helping us understand it.
Who needs it? Why is it useful? What are the features? A screen system is about as descriptive as a 'javascript framework'.
No, it doesn't have anything to do with Gnu Screen or tmux or command-line linux. It is just a very simple and clean way to create websites using knockout.js for data bindings, sammy.js for route system, abstracting and automatic much of the boilerplate needed for sammy and knockout.
So it makes web pages. Dynamically, programmatically. Awesome. [wanders off and deletes perl cgi-bin running on NCSA server]. I love it when computers make my life easier and return my precious leisure time. Please accept my apologies for my inherent lack of insight.
10 comments
[ 5.2 ms ] story [ 31.9 ms ] threadAnd don't suppose that everybody know what a "Screen system" is...
The main page is in /public/templates/index.html, and inside that .html every route starts with /assets/ because I use it with Play framework. You can change the routes to /public/ or whatever.
In /public/javascript/src/screens you can find two basic screens which point to each other, and in /public/templates/ there are 2 .haml files corresponding to each screen. In /public/locals are the locals for each screen.
Hope that clarifies something...