This is a feature request as well (and probably not important to do before hobo 1.0) but it'd be nice to be able to specify the order that fields should appear in for a particular model, no matter where it appears. This could be done fairly easily by making with-fields and with-field-names. The easiest place would be to put this in the model, although that seems like really bad MVC design, so I'd recommend having a config file (or maybe even a tag that you can override for each model?) to define it.
On Oct 16, 9:48 am, Iain <[email protected]> wrote: > Related to Owen's idea ("being able to extend a tag in other than > application.dryml") - it would be great to have a standard place to > override polymorphic tags (eg. card and form) for your models. For > example, if you want to override the show page tag for model "Person", > you create show.dryml in the /app/view/person folder and put your show > page in there. However, if you want to override the card for Person or > the Form, you have to put it in application.dryml. This seems a bit > counterintuitive (the changes relate only to one model, not the whole > application) and it can lead to application.dryml becoming very > crowded. > > I've taken to putting overriden cards and forms in a separate file > (then importing them from application.dryml) but a much better > solution would be if hobo would look for a card.dryml or form.dryml > file in each of the view/<modelname> folders and take the overriden > tags from there instead. > > I realise that this is more of a feature request than a bug, but it's > probably my main annoyance at the moment. > > On Oct 16, 6:04 am, Owen <[email protected]> wrote: > > > > > Whoops, forgot the enhanced scopes for table-plus (search includes > > related tables). That's a top one... > > > On Oct 15, 2:25 pm, Owen <[email protected]> wrote: > > > > Being able to extend a tag in other than application.dryml would be > > > nice... > > > > On Oct 14, 1:12 pm, Tom Locke <[email protected]> wrote: > > > > > More fair warning: I looked at this ages ago and at the time concluded > > > > that the only solution is to make sure you don't call responds_to? > > > > (and of course #try) > > > > > Obviously we rely on respons_to? all over the place : / > > > > > Tom > > > > > On 14 Oct 2009, at 18:09, Matt Jones wrote: > > > > > > Well, if you want a nasty one, take a look at #247. There's some weird > > > > > interaction between .responds_to? and the association proxy stuff, > > > > > which can cause all(!) the records in a table to be loaded under some > > > > > circumstances. It's a minor issue with most apps (with small DBs) but > > > > > can really get painful with larger production datasets. > > > > > > Fair warning: debugging through the association stuff in Rails is > > > > > extremely hairy. There's a couple spots where if you try to print out > > > > > variables that should be in scope, ruby-debug just dies messily. > > > > > Really fun... :) > > > > > > --Matt Jones > > > > > > On Oct 14, 2009, at 10:51 AM, Bryan Larsen wrote: > > > > > >> I've actually got a bit of time to knock off some hobo bugs. (Thanks > > > > >> Owen & Barquin!) > > > > > >> Does anybody have any pet tickets they'd like addressed? > > > > > >> cheers, > > > > >> Bryan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
