Android：如何最好地将数据传递到视图？

发布于 2024-10-16 00:57:34 字数 247 浏览 2 评论 0原文

我有一个显示游戏所有级别的视图。这些级别由活动读取，然后传递到视图中。我可以从视图中读取它们，但这实际上并不是它的责任，而且我喜欢关注点分离。

现在，我为此调用一个设置器：

((GameView) findViewById(R.id.game)).setLevels(loadLevels());

但是，我不喜欢这样一个事实：如果我忘记调用设置器，视图将无法正常工作。有没有更好的方法来通过级别？

原文

I have a view that displays all the levels of my game. These levels are read by the activity and then passed into the view. I could read them from the view, but it's not really its responsibility, and I'm a fan of separation of concerns.

Right now, I'm calling a setter for this:

((GameView) findViewById(R.id.game)).setLevels(loadLevels());

However, I don't like the fact that the view will be dysfunctional if I forget to call the setter. Is there a better way to pass the levels in?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

浅浅淡淡 2024-10-23 00:57:34

这也是一个偏好问题。理论上来说，按照你现在的方式通过关卡是完全可以的。或者，如果您需要的不仅仅是设置级别，而是提供更多功能（即还保存级别），我通常使用一个单独的类负责处理这些事情（即存储库、一些“管理器”类等...）。然后，这个类被传递到构造函数上的视图中，最好是强制提供它。当然，为了分离事物，我使用接口而不是具体的实现，它可能看起来如下：

public class MyView {

   public MyView(ILevelLoader levelLoader){
      this.levelLoader = levelLoader;
   }

   ...
}

通常，这可能不起作用，因为视图是由框架直接实例化的，而不是由应用程序实例化的。在这种情况下，您被迫通过适当的设置者来完成此操作。这是某种 MVC/MVP 模式。

出于您的兴趣，您可能还想了解一下 IoC 容器和依赖项注入。 Google 提供的 Guice 是一个很好的框架，我已经在 Android 上使用过。

It is also a bit a matter of preference. Theoretically it's perfectly fine to pass the levels as you're doing. Alternatively, if you need more than just set the levels, but provide further functionalities (i.e. also saving of levels) I normally use a separate class responsible for handling such things (i.e. a Repository, some "Manager" class etc...). This class is then passed into the View on the constructor preferably s.t. one is forced to provide it. Of course, in order to separate things, I use interfaces rather than specific implementations s.t. it may then look as follows:

public class MyView {

   public MyView(ILevelLoader levelLoader){
      this.levelLoader = levelLoader;
   }

   ...
}

Often, this may not work, because the view is something instantiated by the framework directly rather than by the application. In such a situation you're forced to do it through an appropriate setter. It is some sort of MVC/MVP pattern.

Just for your interest, you might also want to take a look at IoC containers and dependency injection. Guice provided by Google is a nice framework I've already used on Android.

回复收藏 0 原文