Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Button inheritance

 
Gustaf Garrison
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can some one please explain to me why is (in this example) the button class related to android.view??
Should the inheritance be related to android.widget?
Please see attached image
In the packages they are separated but in the reference help, Button is child of android.view.View which is completely separated from android.widget package
I don't understand how this inheritance structure works

Can somebody explain this to me?

Thanks!!!

inheritance.jpg
[Thumbnail for inheritance.jpg]
inheritance
 
Ulf Dittmer
Rancher
Posts: 42969
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What, exactly, don't you understand about it? A class that extends some other class does not need to be in the same package (as you can see with android.widget.TextView extending android.view.View).

So when you say "android.view.View which is completely separated from android.widget package", nothing more is at work than the original package structure designer's ideas of what class should go into which package. That has no impact on the workings of those classes (and only a little impact on the overall class hierarchy). Those classes are not "separated" in any fundamental way.
 
Gustaf Garrison
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for your answer Ulf !
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic