On Naked Objects for .NET (see www.nakedobjects.net) we are currently working on a brand new variant called Naked Objects MVC, which combines Naked Objects with ASP.NET MVC. This gives you a 100% generic HTML UI, which you can then customise as much as you want when you are ready to do that. We're a few weeks away from releasing the Beta.
The DnD viewer of Naked Objects does - through the tree viewer on the left-hand side of the form - allow the graph of objects to be viewed.
Rob Matthews has also been doing quite a lot of work on this viewer to make it more extensible for other views. We hope to push a new release out in May (probably called 4.1).
For my part, I've been working on a new HTML viewer using Wicket. Like Richard's .NET equivalent, this will also support customization, either cosmetically using CSS or more substantially by writing new Wicket components (to render an object, an object collection, a collection of objects, or what have you). The code is currently in sourceforge.net/projects/wicketobjects.
But in your question you said that really want is a tool to help you do the modelling part, not so much the deployment. In which case NO will let you develop your pojos, and then you can go deploy with a custom presentation and persistence layers if you want. There's discussion of this in my book (chapter 13 thru 15).
正如 Dan 所说，我目前正在开发 DND 查看器，并且有兴趣提供其他视图，以测试设计的灵活性或包含它们（如果它们是通用的）。
Can you be more specific as to how you want your views to be shown. Are there specific relationships that you want to show this way, or is it all of them?
As Dan said, I am currently working on the DND viewer and would be interested in providing other views, either to test the flexibility of the design or for inclusion if they are generic.
发布评论
评论（3）
一定是Java吗？
在 .NET 的 Naked Objects（参见 www.nakedobjects.net）上，我们目前正在开发一种名为 Naked Objects MVC 的全新变体，它将 Naked Objects 与 ASP.NET MVC 结合在一起。这为您提供了 100% 通用 HTML UI，然后您可以在准备好时根据需要进行自定义。距离发布 Beta 版还有几周时间。
Does it have to be Java?
On Naked Objects for .NET (see www.nakedobjects.net) we are currently working on a brand new variant called Naked Objects MVC, which combines Naked Objects with ASP.NET MVC. This gives you a 100% generic HTML UI, which you can then customise as much as you want when you are ready to do that. We're a few weeks away from releasing the Beta.
Naked Objects 的 DnD 查看器 - 通过表单左侧的树查看器 - 允许查看对象图。
Rob Matthews 也在这个查看器上做了很多工作，以使其对于其他视图更具可扩展性。我们希望在 5 月份推出新版本（可能称为 4.1）。
就我而言，我一直在使用 Wicket 开发新的 HTML 查看器。与 Richard 的 .NET 等效项一样，这也将支持自定义，无论是在外观上使用 CSS，还是更实质地通过编写新的 Wicket 组件（以呈现对象、对象集合、对象集合或您拥有的东西）。该代码当前位于 sourceforge.net/projects/wicketobjects 中。
但在您的问题中，您说真正想要的是一个帮助您完成建模部分的工具，而不是部署。在这种情况下，NO 将允许您开发 pojo，然后您可以根据需要使用自定义表示层和持久层进行部署。我的书中对此进行了讨论（第 13 章至第 15 章）。
The DnD viewer of Naked Objects does - through the tree viewer on the left-hand side of the form - allow the graph of objects to be viewed.
Rob Matthews has also been doing quite a lot of work on this viewer to make it more extensible for other views. We hope to push a new release out in May (probably called 4.1).
For my part, I've been working on a new HTML viewer using Wicket. Like Richard's .NET equivalent, this will also support customization, either cosmetically using CSS or more substantially by writing new Wicket components (to render an object, an object collection, a collection of objects, or what have you). The code is currently in sourceforge.net/projects/wicketobjects.
But in your question you said that really want is a tool to help you do the modelling part, not so much the deployment. In which case NO will let you develop your pojos, and then you can go deploy with a custom presentation and persistence layers if you want. There's discussion of this in my book (chapter 13 thru 15).
您能否更具体地说明您希望如何展示您的观点？您是否想以这种方式展示特定的关系，或者是所有的关系？
正如 Dan 所说，我目前正在开发 DND 查看器，并且有兴趣提供其他视图，以测试设计的灵活性或包含它们（如果它们是通用的）。
Can you be more specific as to how you want your views to be shown. Are there specific relationships that you want to show this way, or is it all of them?
As Dan said, I am currently working on the DND viewer and would be interested in providing other views, either to test the flexibility of the design or for inclusion if they are generic.