I suppose that's possible, but seems a lot of work. For example, with
the edit.vm I'd either have to design my own UI pretty much from
scratch, or put ugly #if statements all through it to tell it to
ignore the few properties I do not want to show up. Neither approach
feels very appealing.
I could work out my own viewmodel implementation and pass THAT to the
scaffolding, but converting to/from the activerecord entity to the
viewmodel is also looks like a lot of manual work.
It seems to me that putting some sort of attribute on the activerecord
entity would be the simplest move. But that would mean my User model
wouldn't have it's "Ignored" property on any scaffolding it might be
used on in the future.
Maybe adding to the scaffolding attribute itself would work-- some way
to list the properties on the type that will be scaffolded. Or a
callback method for the scaffolding code that would return the
properties that should be used. Hmm.
On Oct 31, 6:10 pm, John Simons <
johnsimons...@yahoo.com.au> wrote:
> Jake,
>
> You could override the default templates with your own for this
> specific models.
> Seehttp://
www.castleproject.org/monorail/documentation/v20/integration/a...
> for how to override templates.
> And here for examples of templates:
http://github.com/castleproject/Castle.MonoRail/tree/master/src/Castl...