> Why do the Actionscript display class packages have camelcase in their
naming?
 
It's just our naming convention for packages... this casing does not
affect how FlexBuilder's hinting or anything else behaves. If you don't
like it you can use any casing you want for your own package names.
 
- Gordon

________________________________

From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of diamondTearz
Sent: Saturday, March 31, 2007 3:13 PM
To: [email protected]
Subject: Re: [flexcomponents] Why do the Actionscript display class
packages have camelcase in their naming?




That's good to know. I was wary of it because I thought this might have
been
the source of my problem in the past but appreciate you helping me clear
that up.

Josh Tynjala wrote:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> I've been using that same system for helper classes in custom
> components for some time now without any problems. I have some custom
> lists that place classes in com.joshtynjala.controls.listClasses.*,
and
> they always appear in Flex Builder's code completion system. 
> 
> Josh 
> 
> diamondTearz wrote:
> 
> 
> 
> 
> Josh- I think that's the detail I might have been missing. I think I
was 
> attributing the effect to maybe the way the classes were named. Have
you 
> named some classes with suffixes like "myviewClasses" and had normal 
> behavior from them in the editor? 
> 
> Mani 
> 
> Josh Tynjala wrote: 
> > I have not noticed any different behavior with the code
completion 
> > system when dealing with packages named with camcel case.
However,
> you 
> > may have noticed that some classes in these packages don't appear

> > within the code completion system. This is actually because the
> classes 
> > themselves use the [ExcludeClass] metadata and has nothing to do
> with 
> > the package name. 
> > 
> > Josh 
> > 
> > diamondTearz wrote: 
> > 
> > 
> > 
> > 
> > I think the convention when naming packages is usually to use al 
> > lowercase 
> > which is why this difference caught my eye. It seemed to me that
> using a 
> > capital letter in naming the package made my code completion
> behave 
> > differently. This is something I did a couple of weeks ago so my
> recall 
> > may be foggy on it- I was looking at creating some support
classes
> for 
> > my 
> > components and wanted to make sure that I knew why they used this
> in 
> > naming 
> > their packages. 
> > 
> > Michael Labriola wrote: 
> > > 
> > > 
> > > Mani, 
> > > 
> > > By convention, all classes in ActionScript start with an
> uppercase 
> > 
> > > character and are camel case. 
> > > 
> > > So: 
> > > 
> > > DataGrid 
> > > SomeComponent 
> > > 
> > > variable names also tend to be camel case, with a lower
> case first 
> > 
> > > letter. So, I would wager the packages are simply an
> extension of 
> > > this concept. 
> > > 
> > > It is a convention though, not a rule, so, I am not sure
> why you 
> > > would see any difference. 
> > > 
> > > Mike 
> > > 
> > > --- In [email protected]
<mailto:flexcomponents%40yahoogroups.com>  
> , 
> &gt; diamondTearz 
> &gt; &amp;gt; &amp;lt;[EMAIL PROTECTED]&amp;gt; wrote: 
> &gt; &amp;gt;&amp;gt; 
> &gt; &amp;gt;&amp;gt; 
> &gt; &amp;gt;&amp;gt; Does the camel case naming of the packages in
the
> components 
> &gt; in 
> &gt; &amp;gt; Flex serve a 
> &gt; &amp;gt;&amp;gt; special purpose? For example listClasses instead

> &gt; &amp;gt; of "listclasses". I was 
> &gt; &amp;gt;&amp;gt; wondering if naming them that way did something.
> I noticed 
> &gt; that 
> &gt; &amp;gt; it seemed 
> &gt; &amp;gt;&amp;gt; to have an effect on my code completion but
would
> like to know 
> &gt; 
> &gt; &amp;gt; more. 
> &gt; &amp;gt;&amp;gt; 
> &gt; &amp;gt;&amp;gt; Mani 
> &gt; &amp;gt;&amp;gt; 
> &gt; &amp;gt;&amp;gt; -- 
> &gt; &amp;gt;&amp;gt; View this message in context:
> http://www.nabble.com/Why-do-the- <http://www.nabble.com/Why-do-the->

> 
> &gt; &amp;gt;
> Actionscript-display-class-packages-have-camelcase-in-their-naming--
> 
> &gt; &amp;gt; tf3497273.html#a9768345 
> &gt; &amp;gt;&amp;gt; Sent from the Flex Component Development mailing
> list archive 
> &gt; at 
> &gt; &amp;gt; Nabble.com. 
> &gt; &amp;gt;&amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; &amp;gt; 
> &gt; 
> &gt; -- 
> &gt; View this message in context: 
> &gt;
>
http://www.nabble.com/Why-do-the-Actionscript-display-class-packages-hav
e-camelcase-in-their-naming--tf3497273.html#a9768801
<http://www.nabble.com/Why-do-the-Actionscript-display-class-packages-ha
ve-camelcase-in-their-naming--tf3497273.html#a9768801>  
> 
> &gt; Sent from the Flex Component Development mailing list archive at 
> &gt; Nabble.com. 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> &gt; 
> 
> -- 
> View this message in context:
>
http://www.nabble.com/Why-do-the-Actionscript-display-class-packages-hav
e-camelcase-in-their-naming--tf3497273.html#a9772406
<http://www.nabble.com/Why-do-the-Actionscript-display-class-packages-ha
ve-camelcase-in-their-naming--tf3497273.html#a9772406>  
> Sent from the Flex Component Development mailing list archive at
> Nabble.com. 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

-- 
View this message in context:
http://www.nabble.com/Why-do-the-Actionscript-display-class-packages-hav
e-camelcase-in-their-naming--tf3497273.html#a9772828
<http://www.nabble.com/Why-do-the-Actionscript-display-class-packages-ha
ve-camelcase-in-their-naming--tf3497273.html#a9772828> 
Sent from the Flex Component Development mailing list archive at
Nabble.com.



 

Reply via email to