The Backbone's connected to the...
kashflow.com
kashflow.com
well, technically PP wasn't used here, but the unnecessary transition effect makes me feel like it was.
Welcome to PP 2.0, browserdeath edition.
"WHO WROTE THE 'DEATH NOTE' SCRIPT?" released on HN earlier this week was very interesting but I kept losing my place down the page.
I have little issue with presentations in and of themselves, although generally speaking either the presentation is missing most of the relevant information or it's just a more annoying format for a blog post.
I do have an issue with reveal.js which is the epitome of "style over substance" presentations full of pointless rotations and intractable multi-dimensional navigations, and with overuse of image macros which are the lowest common denominator of the modern web and the most information-free way to waste time and bandwidth.
> "WHO WROTE THE 'DEATH NOTE' SCRIPT?" released on HN earlier this week was very interesting but I kept losing my place down the page.
A bigger difference is that this piece happens to have actual content. And dense one at that. It's not trivial to read let alone skim.
I also think presentations could work better as a single-consumer format if "presentation notes" were available alongside, expanding on the slide itself with what the presenter would usually talk about. Essentially a slide becomes a "hook", a header for a page of content. And the presentation itself becomes a sectioned/paginated post. But I don't know any presentation site which provides a good interface for that (I don't believe speakerdeck does anyway).
Could you explain further as to what the interface would be like? If the presentation is full screen, where would the notes be? Somewhere off-page that you could pull in if needed?
That's a pretty interesting idea, and it could help e.g. non-native or disabled audience follow the talk.
If the on-device UI is done well-enough, it could also help with the usual "ask questions at the end" format: tap the text and jot down a quick reminder, and at the end of the presentation the things you tapped can be displayed for review or questioning.
> If the presentation is full screen, where would the notes be? Somewhere off-page that you could pull in if needed?
Sure, but I think it'd work better if the interface was closer to "presenter view", with the slides taking only part of the screen (say half) and the notes/accompanying text taking the rest. Then you could have something similar to e.g. Reeder/Mac's interface, using the spacebar to read "the next thing", either scrolling down the text (if not all of it can be displayed) or switching to the next slide (if the text is under a page or its end has been reached)
I don't need a long blog post, but my eyes can jump from paragraph to paragraph much faster than (apparently reveal.js's?) slidey animation thing.
me too. I had to close my eyes for the spin after a few times.
Most people here know and prefer html/css to magic.
> You also have an automated generated page (that contains all of your js files or 1 big file if is min)
Easy with Rails. A lot of backbone apps are running on rails.
Ps. I really think it's a bad idea coupling your client side to the server side. Imagine you want to go to node.js someday..?
Backbone serves all these interests by providing only a very minimal framework for model/view binding. How you structure the app and what supporting libraries you use are completely up to you. It also makes it very easy to port existing code into Backbone which is quite a strong evolutionary trait for a javascript framework these days.
Long term I think Backbone will lose the popularity contest to richer solutions, but similar to HTTP and the web itself, sometimes less is more.
No really, I realize you say that server refreshes work for wikipedia, but you really seem to be suggesting that all websites should be single page apps.