This thread smells related to the recipe that I requested at www.cookbook.hobocentral.net. I've got a presenter combined with a form_assistant plugin that makes for an elegant and maintainable view. I want to capture a bunch of info at signup, which I would think would be a common concern. There are inevitably multiple models involved in that form. I've got the presenter logic in a seperate layer (helper for now). It's a thing of beauty. I need to figure out how to extend do_signup to use my presenter object--no help in the docs. But ara_vartanian brings up some good points on where this kind of logic should (shouldn't) live. It seems to me that common design problems with known patterns need an easy hobo implementation. There are some perspectives out there that say this level of design is over- thinking things. But why then does everyone have the Gang of Four book on their desktop? Sadly, I usually find myself floundering about to ultimately find elegant hobo solutions. Just bitching, sorry.
--Paul On Nov 19, 2:05 am, Tom Locke <[EMAIL PROTECTED]> wrote: > > if you wanted the :type > > => ... feature for attr_accessor you could probably just steal that > > bit from ModelExtensions. > > Actually that made little sense, because that extension relies on a > bunch of other stuff in ModelExtentions : / > > Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
