be careful with precision vs. intuition conventions each of them have benefits for the long and short term
also a price On Nov 21, 2012, at 4:14 PM, Igor Stasenko wrote: > On 21 November 2012 15:11, Igor Stasenko <[email protected]> wrote: >> On 21 November 2012 14:55, Mariano Martinez Peck <[email protected]> >> wrote: >>> >>> >>> On Wed, Nov 21, 2012 at 4:50 PM, Igor Stasenko <[email protected]> wrote: >>>> >>>> On 21 November 2012 12:47, Fernando Olivero <[email protected]> >>>> wrote: >>>>> I totally agree. Dummy does not tell me about the class. >>>>> >>>>> Are there just 3 uses of Dummy in the core? >>>>> >>>>> We should either use Null or use a specific prefix always, so its form >>>>> a >>>>> consisten pattern. >>>>> >>>>> DummyUIManager -> NullUIManager >>>>> >>>> yes, not "Headless" please. >>>> >>> >>> why? >>> >>> It is not a complete NULL UIManager. A NullUIManager would implement all >>> the API and do nothing (or implement nothing but only #doesNotUnderstand: >>> doing nothing or something like that) DummyUIManger DOES stuff, but it >>> makes sures not to end up calling the UI (like progress bar, notifications, >>> confirmations, etc). So, in this particular case, HeadlessUIManager is much >>> more accurate for me than Null. >>> >> then you will need to explain EVERY time to users why they should use >> CommandLineUIManager, or NonInteractiveUIManager for headless mode, >> rather than HeadlessUIManager. >> Good luck with that :) >> > > this is, btw , one of the reasons why i picked NonInteractive name > instead of calling it 'headless'. > Because it is more precise. And Camillo also used 'CommandLine' > instead of 'Headless'. > > In this regard, Dummy/Null is much more precise with describing > behavior of that ui manager class than headless. > > -- > Best regards, > Igor Stasenko. >
