blocks|key|1286208|text|您可以尝试实现某种视图模型，它保存了对象的当前布局。这样，x/y值和对象的id一起存储在布局文件中，而纯模型数据则存储在其他地方。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1286209|也许这有点帮助，|1286210|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You could try to implement some kind of view model, which saves the current layout of your objects. This way, x/y values together with the id of the object are stored in a layout file while pure model data is stores elsewhere.

Maybe this helps a bit,

blocks|key|2678777|text|我认为你需要确保你保持的内容和方式是分开的。您正在显示的是抽象的、一组坐标、形状类型。你如何显示它是非常具体的。我要确保域模型纯粹处理什么，视图层唯一地处理如何处理。但是，如果不了解更多关于应用程序的信息，就很难深入了解细节。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2678778|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think you need to make sure you're keeping the what and the how separate. What you are displaying is abstract, sets of coordinates, shape types. How you're displaying it is very specific. I'd make sure the domain model dealt purely with the what and the view layer dealt uniquely with the how. It's hard to get into specifics though without knowing more about your app.

blocks|key|2633970|text|在图表工具中，形状的x/y位置是域数据的一部分(形状的位置是图表的一部分--没有它就不能绘制图表)，使用这些x/y坐标并在屏幕上绘制形状的代码是表示层的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2633971|我知道有些人认为只用于显示的数据应该单独保存，但在我曾经单独处理过的每个项目中，这都是一个巨大的维护和支持噩梦。|2633972|在一个简单的图表工具中(如果工具只是绘制和编辑图表，而没有基于图表的任何花哨处理)，就没有业务逻辑，只有绘制和编辑图表(属于表示层)和图表数据(即域模型)的代码。|2633973|如果没有业务逻辑，通过为域和表示使用一组单独的对象，您将不得不两次复制所有模型数据(一次在模型对象中，一次在表示对象中)，并且将业务逻辑与演示文稿分离没有任何好处(因为没有)。|2633974|另一方面，如果您有一些算法运行在数据上，您可以通过将图形数据与绘图代码分离来获得一些好处--您可以在工具之外运行该算法，您可以进行更好的自动化测试，等等。|2633975|另外，如果您编写了另一个对相同数据进行操作的系统，那么如果您将模型定义与绘图代码分离，您至少可以共享模型定义和保存/加载代码。|2633976|那么，让我们总结一下：|2633977|所有关系图数据都是模型的一部分(包括仅用于绘制屏幕或处理用户输入的表示purposes).|2633978|Anything的数据在表示层(obviously).|unordered-list-item|2633979|
|2633980|If中)，这两个数据覆盖了您的所有代码和数据，应用程序没有任何“业务逻辑”，并且层分离可能是过度的。如果您有任何不适合这两个类别的代码，并且您认为它应该是模型的一部分，而不是构建两个单独的层。|2633981|
<+code+>H+19If系统之间有任何代码共享的机会，您应该确保共享代码不与表示代码混为一谈。|2633982|和最后一个“额外”点--如果这是一个可能在很长一段时间内正在积极开发并在将来添加了新功能的项目--您可能希望分离UI/数据，以使将来的工作更容易--您必须决定这种未来的节省是否值得现在的额外时间，以及这种分离是否真的有可能在未来有所帮助。|2633983|2633984|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|16|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|R|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|R|7|1F|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|12|$]]

In a diagramming tool the x/y position of a shape is part of the domain data (the location of the shapes is part of the diagram - you cant draw the diagram without it), the code that use those x/y coordinates and draw a shape on the screen is part of the presentation tier.

I know some people think that data that is only used for display should be saved separately, but in every project I've ever worked on that saved data separately this turned up to be a huge maintenance and support nightmare.

In a simple diagramming tool (if the tool just draws and edit the diagram without any fancy processing based on the diagram) there is no business logic, there's only the code that draws and edit the diagram (that belongs in the presentation tier) and the diagram data (that is the domain model).

If there is no business logic, by using a separate set of objects for domain and presentation you'll have to duplicate all your model data twice (once in the model objects and once in the presentation objects) and you won't get any advantages from separating the business logic from the presentation (because there isn't any).

On the other hand, if you do have some algorithms you run on the data you do have something to gain by separating the graph data from the drawing code - you can run the algorithm outside the tool, you can have better automated tests, etc. 

also if you write another system that operates on the same data you can at least share the model definition and save/load code if you separate it from the drawing code.

So, let's summarize:

<ul>
<li>All the diagram data is part of the model (including data only used for presentation purposes).</li>
<li>Anything that draws to the screen or handles user input is in the presentation tier (obviously).</li>
<li>If those two cover all your code and data than your application don't have any "business logic" and the tier separation is probably overkill.</li>
<li>If you have any code that doesn't fit into those two categories and you think it should be part of the model than you should build the two separate tiers.</li>
<li>If there's any chance for code sharing between systems you should make sure the shared code is not mixed in with the presentation code.</li>
<li>And one last "bonus" point - if this is a project that's likely to be in active development for a long time with new features added in the future - you may want to separate the UI/data anyway just to make future work easier - you have to decide if this future saving is worth the extra time now and if this separation is really likely to help in the future.</li>
</ul>

I having trouble figuring out the correct architecture for this kind of application: it's a diagramming application, which resembles MS Visio. The diagrams are used to generated data which is passed to another application.

When designing applications, I've always tried to used layering, but now I can't decide how to do this when the data is so tightly coupled with the presentation. For example, a certain object in my canvas has a (X,Y) data, which is used for presentation purposes only, but has to be stored like domain data.

Where I'm getting things wrong? I'm pretty sure I'm looking at this from the wrong angle, but I can't figure out the right one.

Thanks again!

UPDATE:

I'm also aware that maybe I shouldn't be separating UI from domain in this case. If that is so, please provide me with some rational of when to apply separation and when not to.

Separated Presentation on a UI Centric Application

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我很难为这种应用程序找出正确的架构:它是一个图表应用程序，类似于MS。这些图表用于生成传递给另一个应用程序的数据。在设计应用程序时，我一直试图使用分层，但现在我无法决定如何做到这一点，因为数据与表示耦合得如此紧密。例如，我的画布中的某个对象有一个(X，Y)数据，该数据仅用于表示目的，但必须像域数据一样存储。我在哪里搞错...

问以UI为中心的应用程序上的分离表示
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问以UI为中心的应用程序上的分离表示EN