Timeline for Using nested public classes to organize constants
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 8, 2015 at 12:38 | history | edited | Tulains Córdova | CC BY-SA 3.0 |
added 6 characters in body
|
| Aug 29, 2014 at 15:35 | comment | added | kevin cline | +1, but UI constants probably should not be in business models like BankAccount. They belong in some UI class. | |
| Aug 29, 2014 at 15:34 | history | edited | kevin cline | CC BY-SA 3.0 |
added 1 character in body
|
| Aug 29, 2014 at 11:59 | comment | added | curioustechizen | While I agree that constants only classes are in most cases a sign of bad design, there are legitimate uses. For instance, the constant doesn't always "belong" to a particular class. Keys for Intent extras in Android programming are one such concrete example. | |
| Aug 29, 2014 at 0:36 | history | edited | Tulains Córdova | CC BY-SA 3.0 |
deleted 6 characters in body
|
| Nov 8, 2012 at 18:09 | vote | accept | FrustratedWithFormsDesigner | ||
| Oct 26, 2012 at 21:08 | history | edited | yannis | CC BY-SA 3.0 |
double negative!
|
| Oct 26, 2012 at 21:03 | history | edited | Tulains Córdova | CC BY-SA 3.0 |
added 142 characters in body
|
| Oct 26, 2012 at 20:56 | history | answered | Tulains Córdova | CC BY-SA 3.0 |