Timeline for Does having many duplicated methods and deep inheritance hierarchies in GUI APIs (Java Swing, Android SDK) violate the SOLID design principles?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 10, 2014 at 20:53 | comment | added | user949300 | If isDoubleBuffered is your best example of a violation of SRP I'd say they did a good job. As for ISP, you comments make no sense to me. JButton is a class, not an interface. Of course it is littered with all the APIs of its parents. Same for OCP - it handles events by calling ActionListeners. Seems pretty open to me, but I must be missing something in your arguments. Please elaborate. | |
| Oct 9, 2014 at 21:08 | answer | added | Lovis | timeline score: 2 | |
| Oct 9, 2014 at 18:33 | comment | added | Bernard Igiri | @RobertHarvey hopefully my new edit helps clarify. | |
| Oct 9, 2014 at 18:33 | history | edited | Bernard Igiri | CC BY-SA 3.0 | added 1362 characters in body |
| Oct 9, 2014 at 18:10 | answer | added | user22815 | timeline score: 4 | |
| Oct 9, 2014 at 16:27 | comment | added | Robert Harvey | Why do you feel that your observations (duplicate methods, deep inheritance hierarchies) violate SOLID principles? Can you be more specific? As a general rule, GUI API's do use inheritance extensively; I think it's fair to say that GUI's are the dominant use case for inheritance hierarchies. That said, I've always found Java API's to be more convoluted than they need to be. | |
| Oct 9, 2014 at 16:23 | history | edited | Robert Harvey | CC BY-SA 3.0 | added 64 characters in body |
| Oct 9, 2014 at 16:04 | history | tweeted | twitter.com/#!/StackProgrammer/status/520243477959827457 | ||
| Oct 9, 2014 at 13:31 | history | edited | gnat | CC BY-SA 3.0 | title clarified from question text |
| Oct 9, 2014 at 13:29 | review | First posts | |||
| Oct 9, 2014 at 13:52 | |||||
| Oct 9, 2014 at 13:25 | history | asked | Bernard Igiri | CC BY-SA 3.0 |