#rubyonrails - Sat 31 Mar 2007 between 01:44 and 02:26

NY Lost Funds



Radniretpope: wow thats pretty nifty thanks
t0rnagreed
tpopeor rather
nobody uses nested controllers more than once
cygnus128i am talking about nested models but why not?
tpopeoh right
well there's not really a good default
cygnus128yeah, i know
i have thought about it
but if the option is available for the purpose of namespacing it seems to kinda defeat the purpose that you could still have collisions in your table names
you could safely use a convention like module__class
tpopebutfor the fact it's hideous
cygnus128well the whole thing is hideous
tpopeyou may want to suggest it on the mailing list
it's as good of idea as any
and you're right, it at least avoids conflicts
cygnus128either that or take out nested models completely
suggested on the mailing list
we'll see where that goes
hypnos22what's a good name for the join model between a message and its sender/recipient. "messaging"
sounds weird
cygnus128yeah, i've got nothing better
hypnos22damn
cygnus128what kind of message?
eh, it doesn't really matter
louielouiehypnos22: delivery?
hypnos22hrm
cygnus128that only describes the relationship from one side though
eakbashow do I execute system commands in ruby?
cygnus128or from one perspective
lagciscohypnos22: messagment
cygnus128there are a number of ways
thinfueakbas: you can use `` or system() they behave differntly
hypnos22lagcisco: genius
thinfueakbas: `` returns the output
lagciscoheh
cygnus128exec is another
lagciscomessagship
eakbasok thanks
thinfu: thanks

Page: 3 10 17 24 31 38 45 52 59 66 73 80 

IrcArchive

NY Lost Funds