Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a class structure for handset and tablet elements: ProfileFragment(handset) and ProfileFragment(tablet) are derived from ProfileFragment(abstract).
Packages go like:
I’m not sure if I’m doing right with those potentially misleading duplicate class names. What would you recommend ?
You should always avoid naming multiple classes (which differ in their implementation) the same. Even though you can (using different packages).
You could go with putting the your device-type in the class name. E.g.
AbstractProfileFragmentTabletProfileFragmentHandsetProfileFragmentThose classes can (and should) still be split up into multiple packages.