As a co-author of Naked Objects, I would like to add my opinion.
Often, people really like the concept of a bare object template, but they don’t like the specific user interface. You did not say how long you looked at the implementation, or really, which one. Two main open source implementations (there are several others, but less installed):
- .NET framework Naked Objects
- Apache Isis for Java Platform
both of them have more than one user interface. But let's assume that you looked at all the user interfaces by default and are not happy with any of them. Firstly, most people who use either the framework for corporate configuration end up setting the default user interface using either just .css or using additional JavaScript, but still sticking to the concept of a “common” user interface that is created dynamically .
More recently, Dan Heywood and I have been very attentive to the idea of a nudity template with the introduction of the Restful Objects specification - an ultra-clean REST API that works for any rich domain model. Both implementations of two bare objects now also implement the Restful Objects specification. The fact is that using the RO API it is now relatively easy to develop new, radically different user interfaces (general or fully custom-made) that speak with the implementation of the RO server. In other words, it is relatively easy to create your own implementation of the concepts of bare objects on the client side, reusing one of the two main server implementations.
The Spiro you mentioned is our first attempt to create a building block library to create such a user interface using JavaScript (TypeScript, actually) and Angular.js. And the cool thing about using the RO specification is that you can run the same client against any server implementation. I recommend that you look at it carefully.
source share