Gordon, did we ever make a rule about prefixes? Prefixes are most likely to result in capitalization issues like Tink is saying. I remember we got loudly told by the community to remove the FX prefix from the Spark components and use namespaces instead. Did we make that an official part of the naming conventions?
-Alex On 8/17/12 5:53 PM, "Gordon Smith" <gosm...@adobe.com> wrote: > On second thought, changing them would be a bad idea because this convention > comes from the flash.* API. In other words, it wasn't an arbitrary choice for > Flex. As long as Flex is Flash-based, acronyms should not be mixed case, so > that the API looks consistent at all levels of the platform stack. > > - Gordon > > -----Original Message----- > From: Gordon Smith [mailto:gosm...@adobe.com] > Sent: Friday, August 17, 2012 5:42 PM > To: flex-dev@incubator.apache.org > Subject: RE: espensko...@apache.org > > I wouldn't object if you want to change all of them, in all classes, > interfaces, functions, etc. I would object to not being consistent. > > - Gordon > > -----Original Message----- > From: Tink [mailto:f...@tink.ws] > Sent: Friday, August 17, 2012 3:14 PM > To: flex-dev@incubator.apache.org > Subject: Re: espensko...@apache.org > > I've followed these coding standard for some time, it makes sense to keep all > code to a particular standard, but I think is is one is a mistake. > > I've so often ended up will classes like FXQSIForm, which would be so much > better as FxQsiForm. > > Tink > > > On 17 Aug 2012, at 20:08, Gordon Smith wrote: > >>> SwfClassLoader.as >> >> Hi, I wanted to mention that the Flex coding standards call for acronyms such >> as SWF and SWC to never be mixed case. >> >> - Gordon > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
