On 08/25/2011 08:25 PM, Bill Burke wrote:
>
>
> On 8/25/11 12:49 PM, Markus KARG wrote:
>> While I understand Bill's concerns as a vendor, I need to say that I more care for preventing errors than for reducing
>> the number of classes in this case. As the user will only get in touch the methods, but not directly get in touch with
>> the classes (they do not care that the methods in turn create instances of different classes) the number of classes
>> should not become a problems for users.
>>
>
> This has nothing to do about being a vendor. Its about users being able to understand the API. I don't know where you
> got that idea from...
>
I would side Markus here - understanding of a fluent API is not expected to be conveyed as a list of class and method
descriptions. It's like learning English from a dictionary without understanding the proper sentence structure. Fluent
API's are best learned by examples. Class hierarchy plays a marginal role when it comes to learning how to use a
*fluent* API.
Examples, examples, examples, ... (
http://www.youtube.com/watch?v=8To-6VIJZRE ) ;-)
Marek