Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Thanks for your answer. Yes that's what the view does. Let's a user choose an image. But the class name ChooseImageView is very specific. Should you go for a more "generic" name? I guess when designing a framework/SDK you should aim for more generic names but when creating classes for an app it's more preferable to use specific (descriptive) names? Commented Jun 14, 2017 at 19:15
  • You're missing my point. I can't help you get away from this name or tell you if you should get away from or stick with it if you don't tell me what you've named. It's like you've asked, "Is Rex a good name for a ..." Where's the rest of the question??? Commented Jun 14, 2017 at 19:17
  • Sorry but I thought I described what the view does. It's a view where the user is presented three different options (buttons basically) so by pressing on any of them the user will choose an image. That's the purpose of the view. Commented Jun 14, 2017 at 19:24
  • 1
    @PeterWarbo It think that what CandiedOrange is trying to say is that the actual name is neither right nor wrong. In order to be able to say whether is right or wrong we need to know in which level of abstraction the classes live at. For that, we need to be more familiar with the design and the model. So far, ChooseImageView is a quite generic name that could involve a lot of things related to the UI from just screen layout till the implementation of a widget within a panel. Commented Jun 14, 2017 at 20:30
  • 1
    @Laiv thank you. I'm trying to express confusion and it's coming out all confused. :) Commented Jun 14, 2017 at 20:37