Well, it's a judgement call and part a matter of taste. I guess I figure that if an attribute is virtual (not stored in the db but produced by concatenating other fields), I don't really know if a HoboField makes sense for it (it shouldn't be in db migrations, for example). And if no HoboField, then no polymorphic view tag. (Maybe I'm wrong about this).
My ultimate dream, by the way, is for Hobo to have a kind of spec for objects that can be passed into <form/> tags. That way, I could make any kind of object -- whatever my preferences might be -- play nice with the Rapid tags, not just ActiveRecord::Base descendants. On Nov 15, 6:13 am, Tom Locke <[EMAIL PROTECTED]> wrote: > Off hand I'm not sure why this_parent is wrong, but I'm just wondering > why you're not using Hobo's features for this kind of thing? e.g. > using rich types, defining <view> tags or other tags... > > > <repeat> > > <do with="&this.formatter"><view:foo/></do> > > </repeat> > > > Ah but this doesn't work. Why? Digging through the source, I found > > that this_parent inside the view tag is still set to original model > > object, not the formatter. > > That's v strange. this_parent should just be whatever the previous > 'this' was. Sorry - not very helpful! > > 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 -~----------~----~----~----~------~----~------~--~---
