Ok, in this case this is usually configured by a site administrator and might be changed at runtime. Which means it's neither Preferences nor Configuration :) Configurences maybe (just a joke)
Carsten > Hi, > Preferences normally refer to something a user specifies, specific to their > user account. > Configuration is something a deployer specifies for others via a GUI or a > file. > > While I agree the line is blurred as the deployer of Sling/AEM could be > considered to be a user, they are not a user in the sense of the AEM > application. Preferences might cause lots of confusion. > Best Regards > Ian > > On 26 July 2016 at 15:10, Carsten Ziegeler <[email protected]> wrote: > >>> Hi, >>> >>> I know discussing names here is hard but I had an idea ;-) >>> >>> Context Driven Preferences >>> >>> I think it's distinct from anything else that we have so far, matches >>> the purpose and I'd like to avoid "configuration" as we already have >>> too many of those. >>> >> Yepp, I called it in my prototype "preferences", so I think that's good. >> Context *Driven* sounds like a methodology to me, not like a module name :) >> What about "Contextual Preferences" (but on the other hand I'm not a >> native speaker...) >> >> Carsten >> >> >> >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >> [email protected] >> >> > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
