SRB March meetup

[Jason Ong]

For this month's meetup we have Peter Kim (Decisive Bits), Cameron Priest (Tradegecko) and Jason Ong (Tailored) as speakers.

Speakers/Topics:

Peter Kim - MacRuby / Journey app

Cameron Priest - Our experience using Ember.js with Rails

Jason Ong - Beginning Rails antipattern - Fat Models

Date: 13/3, Tuesday

Time: 7:30pm, door opens at 7pm

Many thanks to Luther Goh (Gradeful) for hosting us!

P.S. I've sent a google calendar invite with the same details using HackerspaceSG calendar.

--
Cheers,
JasonOng

---
web: http://bit.ly/jasonong

[Luther Goh Lu Feng]

I am unable to make it tonight. But Meng has agreed to host and he
will arrive with Cameron.

[Jason Ong]

Thanks dude!

--
You received this message because you are subscribed to the Google Groups "Singapore Ruby Brigade" group.
To post to this group, send email to singap...@googlegroups.com.
To unsubscribe from this group, send email to singapore-rb...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/singapore-rb?hl=en.

[Paul Gallagher]

Hey Cameron, thanks for showing off ember.js at the meetup.

It inspired my to try it in one of the apps we're building. On the side, I setup a test/demo project today to see how a bunch of technologies fit together with ember - incl mongodb, coffeescript, twitter bootstrap (github of course: https://github.com/evendis/rails-ember-mongo-bootstrap-demo).

I'm using ember-rest at the moment for marshalling the data communications. It works fine with mongo, no serialisation issues. And with InheritedResources, it makes for super thin controllers. Here's the *full* listing ... ;-)

  class PostsController < InheritedResources::Base
    respond_to :html, :json
  end

However ember-rest is pretty basic, so I was thinking of switching to ember-data next to try some more complex relationships. I know you were using ember-data, but can't remember if you were also using MongoDB. Have you had MongoDB running with ember-data?

One other area I haven't looked into yet is the best way to write tests for the ember app. Any tips you can share on what works best? (assuming the ember app is hosted with a rails backend)

Regards,
Paul

PS: next weekend's project: something in MacRuby, thanks Pete;-)

 

--

[Cameron Priest]

Yo,

Sounds like a good stack ;)

Yip we're running Mongoid, also FYI I think Jose has dropped inherited resources - cant remember why - but I think he'd moved 3.2 to be more inline with what he thought controllers/responders should look like.

Def check out active model serializers aswell.

Regarding Mongoid and ember.js-data - data actually supports embedding of models within other models, have a read over the readme and flick me any questions.

Also Skype : cameronpriest

I'm writing this on the iPhone so not sure if I missed any Qs.

And definately hit macruby - it's cool - but you end up needing a decent understanding of osx libraries etc - but I suppose less verbose...

Regards,

[Paul Gallagher]

Thanks Cameron, when I dive into ember-data I'll probably need to compare notes (aka cheat;-)

PS: I'm still mulling over whether I really buy into the direction and approach ember is taking compared to alternatives (in the broadest sense). I'll probably start another thread after I've poked around a bit more; it's an interesting and extremely timely discussion to be having   

Regarding InheritedResources, yes although Jose makes a clear "deprecation" (I think way back when rails 3.0 was coming out), the project refuses to die - it's too useful, and responders alone achieves only a fraction of what IR does - even with 3.2. It seems Jose has been slipping slightly to the right with respect to "hiding and showing too much logic", hence shifting focus to responders and core rails improvements;-). It is great to see Jose not just drop IR completely though - he's still the perfect active maintainer of the IR project.

Had a look at active model serializers, but haven't used it in anger yet. For my tests, the models were so simple I didn't need anything - default implicit to_json worked fine. To date been using various other approaches for serialization to a standardised API structure - most recently RABL which is also pretty cool (seems to combine the declarative style and scope of active model serializers, while presenting itself as a templating engine) 

Cheers,
Paul

--
You received this message because you are subscribed to the Google Groups "Singapore Ruby Brigade" group.

To view this discussion on the web visit https://groups.google.com/d/msg/singapore-rb/-/YIvsz5Gono4J.