Venkat Subramanian (at NFJS) was talking about a version of RoR that was like the scaffolding in grails (the classes/controllers are modeled in memory, like Bashar's snippet)... but AOP was used to override the behavior, so only the parts you wanted to change were actually code in concrete source files, so you didn't have a ton of auto-gen'd code to maintain and deal with (and no clue what the performance is like)... forget the name of the project - I guess DHH thought it was cool... I'll try to find it in my notes when I get home tonight.
Maybe Bill Mitchell remembers =) he was at that BoF too On 8/10/07, eric biesterfeld <[EMAIL PROTECTED]> wrote: > > While I see the sarcasm dripping here :), perhaps a scaffolding system > would be nice. I was looking at the sample code and I am seeing a > *lot* of code that is easily generated. Of course, any actual > framework is more interesting than code generation that can happen, > but as we see in grails and rails and other new frameworks, the > scaffolding is becoming more and more a "must" rather than just a > bonus. > > Unfortunately, it's not going to be until next week that I'm going to > be able to look into Crank, but I'll try to give a more detailed > opinion then. :) > > On 8/10/07, Rick Hightower <[EMAIL PROTECTED]> wrote: > > > > > > Thanks... Wow... I have never heard of RoR. > > > > How does RoR read JPA annotations? I thought RoR was for Ruby. > > > > Thanks for your feedback on Cranks master/detail, pagination, sorting, > > relationship mgmt, etc. I really appreciate it. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
