Thank you for your answer!
I agree with you about the "spaghetti hierarchy". They 'inherited' the "spaghetti hierarchy" in some parts already because it is an old legacy project.
So in my experience it is less difficult to judge if a subsubsubsubclass already contains a special form element or not, if you take the getter-approach (1). And if your IDE is fancy enough, you almost get this information for free.
At least it is easier to see (for me) than 'subclass removes A,B and adds C, subsubclass removes B again and adds E... now what does subsubsubsubsubclass contain' as described in (2)
Well, the application design is not really a good example for customer related configuration and I would pursue another and less hardcoded approach, too.
So regarding this context I should have asked which of these two solutions is less painful.
And I completely agree: there should probably be an acronym for that! ;)
k
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.