Skip to content

Instantly share code, notes, and snippets.

@puyo
Created November 19, 2010 22:18
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save puyo/707298 to your computer and use it in GitHub Desktop.
Save puyo/707298 to your computer and use it in GitHub Desktop.
Putting all your slick in one place...?
:javascript
Shining.config({...})
#first
%h1 Hi there world
%p Yes this is a slide
%p.step with a step
:javascript
// stuff for the first slide
:css
/* css relevant to the first slide */
#second
%h1 Second slide
%aside Still a slide
#third
%h1 Third slide
%p How many more?
@puyo
Copy link
Author

puyo commented Nov 19, 2010

Mmm. I'm trying it now and none of their examples work. It looked okay on the box. It does seem like overkill for this.

@juliocesar
Copy link

I think by far the most welcome change I can think of is Jasmine specs. I've tried getting the suite tested through it to no avail a few times.

@puyo
Copy link
Author

puyo commented Nov 20, 2010

Sammy's Haml is no better. It lacks forEach, filter, trim, etc. too and thus doesn't work on IE8. Your copy of haml-js seems fine though. Do you not feel confident about it? Is there anything it doesn't handle?

@juliocesar
Copy link

Mine works because I forked it and made it work. If you look at my chances, what I did is I added the missing native JS methods to it, so it just ensures it works everywhere. That could well be copied and pasted into Sammy.js' haml-js.

Now the problem with haml-js was that stuff such as line breaks would sometimes work, and sometimes not. Sometimes you had to use 2 line breaks to get it to work. It was full of small quirks like that that would make the experience frustrating. So I figured Shining would be better off without it.

@puyo
Copy link
Author

puyo commented Nov 20, 2010

Ah okay. That does sound frustrating. sad panda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment