As well as TrueView, as well as Naked Objects for .NET . It supports client / server mode and the web viewer (based on the Java equivalent viewer) is currently migrated.
Depending on what properties / actions are available for a given user / role, this is done dynamically in Bare Objects. There are three types of predefined business rules: 1. Is the item visible? 2. is the member useful? 3. is a member change (new property value or action parameter) valid? Or, more emphatically: can you see it? can you use it? you can do that? The Naked Objects programming model allows these rules to be specified both declaratively and strongly.
Even if you complete your domain model in your own user interface layer, I recommend that you take a look at NO.
Greetings
Dan Haywood
author: "A project managed by a domain using bare objects", pragprog.com
Dan haywood
source share