There's quite a few of these client side frameworks getting about now, along with renderers.
sammy.js is prolly the one that sticks out most in my mind for a client side framework: http://code.quirkey.com/sammy/ There's also haml rendering in javascript server: http://github.com/creationix/haml-js/ client: http://github.com/creationix/jquery-haml http://github.com/edspencer/jaml a moustache renderer: http://github.com/janl/mustache.js Hope that helps Daniel On Tue, Dec 8, 2009 at 1:20 PM, David Lee <deathtoallfanat...@gmail.com>wrote: > Gabe, thanks for the link. I think JS templating for jQuery is a great > idea. > > Now if someone could just implement HAML in JS, it'd be impossible to > render structurally malformed HTML with a typo, and it'd tidy up a bunch of > view code... > > > On Tue, Dec 8, 2009 at 1:15 PM, Gabe Hollombe <g...@avantbard.com> wrote: > >> Lately, I've had some similar thoughts myself, Craig. I've been using >> John Resig's micro templates approach for outputting html from json data >> structures, but I still have a somewhat unstructured approach to where/how I >> include event handlers on my pages. So, my reply isn't too much help here, >> other than mentioning the micro templates approach. But, at least you know >> you're not the only one thinking about these things. >> >> I'd be interested to hear other folks' thoughts as well. >> -g >> >> >> On Tue, Dec 8, 2009 at 12:27 PM, Craig Ambrose <craigambr...@gmail.com>wrote: >> >>> Hi folks, >>> >>> I'm feeling the need for a bit of structure, like that provided like a >>> framework like rails, for the client side of my rails apps. I'm >>> finding that more and more I'm really disliking returning javascript >>> from rails requests. Doing so makes lots of assumptions about the page >>> that is making the request, and makes my rails actions less versatile. >>> I'm also doing more and more on the client side, and so I really want >>> to just talk to the rails app via JSON for all AJAX behavior. >>> >>> I could of course switch to a client side framework (like GWT, or EXT- >>> JS), and could still use rails for a backend. However, I'm not saying >>> that I want to built totally client heavy apps. I'm just saying that >>> *when* I choose to use AJAX, I want to leave the task of presenting >>> the result to the client. I still want to use a lot of non-ajax pages, >>> as most of my work is still "webby", not just a single page app. >>> >>> So, my javascript is better than it used to be. I organise my >>> javascript into classes, and put each class in a seperate file (using >>> caching to combine them later). That's about the extent of it. >>> >>> Javascript programming (for the web) is by nature fairly event driven. >>> It feels a lot like building desktop applications. I think my >>> javascript could benefit from the structure a framework wold provide. >>> In fact, I even think that MVC is the right pattern. Models could >>> provide functionality on top of the simple data structures transmitted >>> from the server as JSON. Controllers handle events on the page and >>> decide what to do. Views may or may not be necessary, but html >>> templating in javascript is sometimes necessary if we're building >>> parts of the page on the fly. >>> >>> Most importantly though, a framework would give me expected directory >>> structure, common plugin structure, and encouragement to test. The >>> benefits would be many, including making it easier to spot duplication >>> (due to the common structure), and easing multi-developer work. >>> >>> What options do I have here? What have people tried for rails? I've >>> used EXTJS before, but I'm looking for a way of organising my JS >>> inside rails, not an actual javascript interface library. Does anyone >>> know of any plugins, or have any thoughts? >>> >>> cheers, >>> >>> Craig >>> >>> -- >>> >>> You received this message because you are subscribed to the Google Groups >>> "Ruby or Rails Oceania" group. >>> To post to this group, send email to rails-ocea...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> rails-oceania+unsubscr...@googlegroups.com<rails-oceania%2bunsubscr...@googlegroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/rails-oceania?hl=en. >>> >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to rails-ocea...@googlegroups.com. >> To unsubscribe from this group, send email to >> rails-oceania+unsubscr...@googlegroups.com<rails-oceania%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. >> > > > > -- > cheers, > David Lee > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to rails-ocea...@googlegroups.com. > To unsubscribe from this group, send email to > rails-oceania+unsubscr...@googlegroups.com<rails-oceania%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-ocea...@googlegroups.com. To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
