I don't foresee us doing that, for the reasons stated. We've had no input requesting otherwise.
I'd be interested to know more about application experience with camel-casing, what the benefits are and whether it causes any difficulties (e.g., confusion because the platform is not camel-cased and you might not know whether you need casing or not because you don't know whether a name is a platform or application name). On 2010-01-29, at 18:25, Antun Karlovac wrote: > Just to be clear - I am and always was completely fine with using the > traditional OL naming convention. I just wanted to check first if OL is > moving to the camel-case naming convention that Webtop is switching to (which > is being done incrementally). > > -Antun > > On 1/29/10 3:22 PM, P T Withington wrote: >> I think that lowercase is the right thing for "public" API's. >> >> I can appreciate that in a large system it is helpful to have more legible >> names, and you will see that reflected in OL implementation. Camel-casing >> is used extensively in the LFC, but the public API's are lowercase. You >> could certainly carry this over to components. >>
