Thx Dan! It is crystal clear!
> From: [email protected] > Date: Thu, 12 Feb 2015 16:53:20 +0000 > Subject: Re: New annotations @hidden vs @Property or @PropertyLayout > To: [email protected] > > The reason that hidden is on both @Property and also @PropertyLayout (and > same for @Action/@ActionLayout and also @Collection/@CollectionLayout) is > because I'm anticipating user-defined layouts in the future... perhaps even > the idea that users might craft their own layout, and share them somehow. > > For those situations a user might want to hide a property if its never > important to them... hence putting them in the XxxLayout. > > On the other hand, the programmer might also want to say that an end-user > should never see a property. An example is in the todoapp, where each > todoitem has an "ownedBy" that should always be hidden (because for any > given user it will always simply just show their name). So in this case > the fact that a property should be hidden is a domain-level constraint > (rather than being a UI layer preference). > > To be safe then you probably should convert @Hidden -> > @Property(hidden=...), rather than@PropertyLayout. > > HTH > Dan > > > > On 12 February 2015 at 15:07, Yu Ri Tan <[email protected]> wrote: > > > Hi, > > I'm trying to replace all deprecated annotations to the new ones, but I > > don't know if I should use @Property of @PropertyLayout to replace @hidden > > since they're both possible. > > According to: > > http://isis.apache.org/reference/recognized-annotations/about.htmlI > > should replace @Hidden with @Property, but according to: > > http://isis.apache.org/reference/recognized-annotations/PropertyLayout.htmlthe > > @PropertyLayout annotation is also possible. > > Old situation: > > > > > > > > > > > > > > > > @Hidden(where = Where.ALL_TABLES) > > New situation: > > @Property(hidden = Where.ALL_TABLES) > > or:@PropertyLayout(hidden = Where.ALL_TABLES) > > I hope one of you can help me out! > > Kind regards, > > Yu Ri Tan
