Talk Suggestion
Jonathan Conway
happy to talk about them:
i) Datamapper - Whirlwind guide to the ORM Datamapper, what sets it
apart from other Ruby ORM's such as AR, Datamappers internals and
demonstration of converting a bunch of AR models to Datamapper. I
*think* this would fit in 30 minutes and hopefully not overrun though
it'd be tight.
ii) Rich client side applications with Sproutcore - Introduction of
the fundamentals then onto some live coding (I'm insane I know!)
interfacing a Sproutcore application to a Merb or Rails backend.
iii) Neo4J - An introduction to Neo4J and why/when it might be of
interest. Accessing Neo4J from Ruby and finally a demonstration
application showing off Neo4J's abilities in a Merb app.
Be honest if these topics are either too 'fringe' or because I'm using
Merb I'm just repackaging the 'same old shit' as someone else put it;)
hehe.
Cheers
Jonathan
Dan Webb
i) Datamapper - Whirlwind guide to the ORM Datamapper, what sets it
apart from other Ruby ORM's such as AR, Datamappers internals and
demonstration of converting a bunch of AR models to Datamapper. I
*think* this would fit in 30 minutes and hopefully not overrun though
it'd be tight.
James Adam
> i) Datamapper - Whirlwind guide to the ORM Datamapper, what sets it
> apart from other Ruby ORM's such as AR, Datamappers internals and
> demonstration of converting a bunch of AR models to Datamapper. I
> *think* this would fit in 30 minutes and hopefully not overrun though
> it'd be tight.
I'd love to hear about this. I can probably do a bit of reading
beforehand, but it might be cool to have some examples of when
Datamapper is better/more efficient (and when it's worse) than
ActiveRecord. Are there any features that ActiveRecord has which
DataMapper doesn't? Can you use DataMapper with ActionPack without too
much pain?
All that said, I think it's interesting outside of the Rails context.
If it's a more efficient ORM than ActiveRecord, I'm interested.
Discussing internal decisions that affect such efficients would be
cool too.
> ii) Rich client side applications with Sproutcore - Introduction of
> the fundamentals then onto some live coding (I'm insane I know!)
> interfacing a Sproutcore application to a Merb or Rails backend.
I'm a bit less interested in this - I can't see myself needing/wanting
to use it at the moment.
> iii) Neo4J - An introduction to Neo4J and why/when it might be of
> interest. Accessing Neo4J from Ruby and finally a demonstration
> application showing off Neo4J's abilities in a Merb app.
Why might it be of interest?
Awesome stuff though Jonathan. Keep it up!
James
Jonathan Conway
Why might it be of interest?
> iii) Neo4J - An introduction to Neo4J and why/when it might be of
> interest. Accessing Neo4J from Ruby and finally a demonstration
> application showing off Neo4J's abilities in a Merb app.
James Adam
>
> Why might it be of interest?
>
>
> Honestly, the reason it could be interesting is purely EVIL
> muhahah;). As Neo4J is insanely fast at traversing and manipulating
> large graphs it would be perfect as a data store for another social
> network site for horny teenagers to cat fight over! Think Friendster
> on LSD!
You had me at Evil....
Kidding of course. I guess I'll need to look at Neo4J and figure out
if it sounds useful or not :)
Martin Sadler
Roland Swingler
of it before.
R
petef
> ii) Rich client side applications with Sproutcore - Introduction of
> iii) Neo4J - An introduction to Neo4J and why/when it might be of
inou...@googlemail.com
Can Datamapper work non relational dbms like couchdb? I thought the
ability to put properties within models go hand in had with Data
mapper, rather than with Active Record.
Jonathan Conway
Cheers
Jonathan
mnemonaut
> ii) Rich client side applications with Sproutcore- Introduction of
> interfacing a Sproutcore application to a Merb or Rails backend.
Dan Webb
>> ii) Rich client side applications with Sproutcore- Introduction of
>> the fundamentals then onto some live coding (I'm insane I know!)
>> interfacing a Sproutcore application to a Merb or Rails backend.
I don't think Sproutcore is enough to do with Ruby to be of relevence
really. The fact that it uses Merb under the hood is incidental.
Also, its designed to work with any backend so interfacing it to Merb
or Rails is going to be fairly generic and not that related to
especially Ruby related.
I know most of us use Ruby on the web but I'd like to see RubyFringe
be about Ruby and not be filled with talks about web technology. I
heard a lot about that stuff already.
That's my two cents anyway :)
James Adam
> On Wed, Sep 24, 2008 at 10:29 AM, mnemonaut
> <mnem...@googlemail.com> wrote:
> I know most of us use Ruby on the web but I'd like to see RubyFringe
... or RubyManor. ;-)
Dan Webb
was trying to make a point there as well...
On Wed, Sep 24, 2008 at 11:02 AM, James Adam <ja...@lazyatom.com> wrote:
now most of us use Ruby on the web but I'd like to see RubyFringe
James Adam
focussed.
vincey
> happy to talk about them:
>
> i) Datamapper - Whirlwind guide to the ORM Datamapper, what sets it
> apart from other Ruby ORM's such as AR, Datamappers internals and
> demonstration of converting a bunch of AR models to Datamapper. I
> *think* this would fit in 30 minutes and hopefully not overrun though
> it'd be tight.
Anything about complex joined table queries would be good in my books.
-v
Murray Steele
Firstly there's been a lot of negative interest in this talk - people just don't seem to want to hear it. Secondly the negative interest has been saying the same things that we've felt about Ruby Manor; namely that the talks should be primarily about Ruby. So this talk is being closed. Thanks for proposing it though!
Murray & James