Search results
From APIDesign
You searched for APIDesignPatterns:Clarity
There is no page titled "APIDesignPatterns:Clarity".
For more information about searching APIDesign, see Help.
Showing below up to 20 results starting with #1.
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)
No page title matches
Page text matches
- OlderBlogPosts (111,273 bytes)
302: ...ifiers]], I'll explain how to achieve even more [[clarity]] than advocated by [[EliminateFuzzyModifiers]] e...
365: Is [[Builder]] better [[APIDesignPatterns|pattern]] than [[CumulativeFactory]]? As Radim an...
369: ==== Cumulative Factory [[APIDesignPatterns|API Design Pattern]] ====
371: ... [[APIDesignPatterns|API Design Pattern]]. Read [[APIDesignPatterns:CumulativeFactory|more]]...
384: Casper Bang asked following question about [[APIDesignPatterns:Exceptions|exceptions in API]] after reading the ... - Blogs:JaroslavTulach:Theory (23,123 bytes)
162: ...nalException|this new addition]] to the list of [[APIDesignPatterns]].
187: ...ge]] of an API is hard. One needs to strive for [[clarity]], one can invent engineering solutions to the pr... - Singletonizer (2,210 bytes)
26: [[Category:APIDesignPatterns]]
27: [[Category:APIDesignPatterns:Creational]]
28: [[Category:APIDesignPatterns:Clarity]] - OpenClass (1,999 bytes)
21: [[Category:APIDesignPatterns:Clarity]]
22: [[Category:APIDesignPatterns]] - ClarityOfAccessModifiers (8,203 bytes)
1: An important aspect of any [[API]] is its [[Clarity]]. As [[API]] is about
2: ...etween the [[API]] writer and [[API]] user, the [[Clarity]]
7: ...y, one might think. However expressing yourself [[Clarity|clearly]] in some
32: ...Clarity]] is important. The easiest way to hurt [[clarity]] is to give one thing multiple meanings. Nobody ...
38: ...ithmetica'' example. What troubles such missing [[clarity]] can result in has been described in [[Alternati... - EliminateFuzzyModifiers (8,118 bytes)
1: ...s that we do not need them. Our [[API]]s can be [[Clarity|clear]] enough with use of following easy steps.
13: ...is indeed violates the [[ClarityOfAccessModifiers|clarity rules]] and in many cases [[API]] designers may w...
17: ...ngle meaning access modifiers, so the so wanted [[clarity]] is achieved. Moreover the usage of such [[API]]...
45: ...st of the code stays the same. It is so easy to [[Clarity|clarify purpose]] of '''protected''' methods!
53: ... mean three different things. In the process of [[Clarity|cleaning the meaning]] we thus need to split the ... - ClarityOfTypes (6,491 bytes)
1: ...ives a recipe to turn those fuzzy meanings into [[clarity|clear]] ones. Yet the result is still not ideal. ...
28: ...essage: ''implement me, don't call me!''. Their [[clarity]] is kept.
30: ..., if you are implementing the provider''. Fully [[Clarity|clear]] again.
32: === [[Clarity]] for [[ClientAPI|Clients]] ===
34: ...the original ''Mixed'' class - e.g. we achieved [[clarity]] for [[ClientAPI|callers]] without complicating ... - ImplementOnlyInterface (5,877 bytes)
1: ...fferent [[evolution]] characteristics. Also the [[clarity]] of such interface methods may not be as clear a...
49: ...t and indeed, can also call its methods. Then the clarity of the ''Provider'' methods is lost. However this...
51: The original [[API]] has still its [[clarity]], but the whole system's single meaning is compr...
71: [[Category:APIDesignPatterns]]
72: [[Category:APIDesignPatterns:Clarity]] - ImplementOnlyAbstractClass (939 bytes)
1: ...Then it is clear the meaning of such methods is [[Clarity|clear]] again as advocated by [[ClarityOfAccessMo...
14: [[Category:APIDesignPatterns]]
15: [[Category:APIDesignPatterns:Clarity]]
16: [[Category:APIDesignPatterns:Creational]] - ClearDefinitionOfVersion (1,810 bytes)
17: ...using separate interfaces for each version, one [[Clarity|clearly communicates]] to the [[API]] users willi...
19: This is one of [[APIDesignPatterns|the patterns]] where usage of [[Java]] interfaces...
21: [[Category:APIDesignPatterns:Clarity]]
22: [[Category:APIDesignPatterns:Evolution]] - Visitor (3,438 bytes)
33: however that hurts the [[clarity]] of the specified version. When I see an impleme...
39: [[Category:APIDesignPatterns]]
40: [[Category:APIDesignPatterns:Evolution]] - SuperVsInner (2,316 bytes)
1: ...al desire for [[OOP|object oriented]] reuse and [[APIDesignPatterns|principles of good API design]]. Proponents of re...
14: ...:APIDesignPatterns]] [[Category:APIDesignPatterns:Clarity]] - Stateful (5,403 bytes)
65: ... claim that [[stateful]] [[API]] is a [[:Category:APIDesignPatterns:Anti|software antipattern]] (those who fight agai...
75: [[Category:APIDesignPatterns]]
76: [[Category:APIDesignPatterns:Anti]]
77: [[Category:APIDesignPatterns:Clarity]] - APIvsSPI (6,917 bytes)
85: ...Patterns:Evolution]] [[Category:APIDesignPatterns:Clarity]] - Final interface (8,284 bytes)
1: [[Final interface]] is a [[APIDesignPatterns|pattern]] often used in [[vendor library]] style ...
21: ...anguage (correct as [[DefaultMethods]] decrease [[clarity]] of the [[ProviderAPI]] interface).
91: ...AnnotationProcessor]] is finally real [[:Category:APIDesignPatterns|API Design Pattern]]!
93: ...]] [[Category:APIDesignPatterns:Anti]] [[Category:APIDesignPatterns:Evolution]] - Abstract class (1,425 bytes)
10: Still, in the name of [[ClarityOfTypes|clarity]], consider separating [[APIvsSPI]] into separate...
12: [[Category:APIDesignPatterns:Anti]]
13: [[Category:APIDesignPatterns]] - EnforcingProperUsage (6,834 bytes)
1: ... your [[API]] is probably suffering from a poor [[clarity]]. Do you users hack around your [[API]] - e.g. u...
3: == Striving for [[Clarity]] ==
5: ...APIDesignPatterns:Clarity|API design patterns for Clarity]] and focus on [[ClarityOfAccessModifiers]], [[Cl...
9: On the other hand, when striving for [[clarity]], it often happens that the [[API]] is more rest...
47: [[Category:APIDesignPatterns:Encapsulation]] - DefaultMethods (7,796 bytes)
71: ...a]] '''interface''' with [[default methods]] is [[clarity|fuzzier]] than pure '''interface''' (without any ...
86: * Do you agree that [[clarity]] is an important aspect of an [[API]]?
89: Then it is [[clarity|clear]]: Use '''final''' classes to represent [[C...
99: ...[[Category:APIDesignPatterns:Clarity]] [[Category:APIDesignPatterns:Evolution]] - Conceptual surface (2,250 bytes)
26: [[Category:APIDesignPatterns:Clarity]] [[Category:APIDesignPatterns:Meta]] - Default Listener Methods (2,732 bytes)
39: ...[[Category:APIDesignPatterns:Clarity]] [[Category:APIDesignPatterns:Evolution]]
View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)
Follow
