marak / data-behaviors Goto Github PK

right now we are using a mix of sample data copy pasted from multiple examples. it would be nice to have a unified sample data set that contains funny / engaging information.

we shouldn't force the developers to use raw CSS sheets. we should add the option to code CSS in less or scss and then compile to CSS at compile time.

i do NOT want to see any CSS templating engines working in the browser itself. the browser should only be sent regular CSS. we might explore a JSON style sheets solution to represent our internal sheets, but this would be transparent to the developer.

The current error reporting is somewhat lacking...

we need to capture ALL errors gracefully and attempt to give an accurate description of what happened.

there are TWO types of errors that could occur in o-behave
compile time errors
run-time errors

compile-time errors should be caught by Ted and outputted in the console

run-time errors should be caught by the browser and logged to the console / written to the DOM (when appropriate). there is a bit of eval() magic happening here, so we'll need to address that first in order to better track error messages.

Ted's current directory watcher is not ideal. We are using nodes sync filewatcher api on several nested files and directories in a loop. We are also unwatching these same items with the sync filewatcher.

There is a bit of an OS race condition here with MacOS's filesystem and the file watcher which is currently being solved with a forced delay. I think if we switch to the macs native FSEvents (http://en.wikipedia.org/wiki/FSEvents) we'll get much better performance and response time from Ted.

there is an escaping issue with single quotes / double quotes when developing in the HAML templates.

we should be able to trap and escape special chars in the compile process, so the developer doesn't have to deal escaping themselves