> 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]
