famono support, FView.regiserTransition refactor

hey!  the small letters on the demo page are super cute!  :)  i'm aware that the gap that sometimes comes is from the destroy() issue you mentioned; i'm sorry I haven't gotten to this yet but it is on my radar.

in the meantime, two things:

1) using famous.* in the root code will break in famono setups.  i don't know exact stats but judging from issues, it's about half our users.  so just put that code inside the FView.ready() so it works great on both.  (yeah, I know the original function doesn't need to be inside there, but it's to prevent confusion if for some reason the function is created and FView.ready doesn't run, and then we get the function but it's not extended - minor i guess)

2) it seemed weird that the package sets up `FView.registerTransition` but then the results are only accessible via a file scoped variable :)  So I added this func, and FView.transitions, into famous-views (which will be in the next release) - and also put in backwards compatible code so nothing breaks on older versions.