[flexcoders] Re: Best practices for the naming of item renderers ?

[João]

For example, a List component shows Users. Each user has a picture and
some data, shown thanks to an ItemRenderer class. I would like to know
if there are best practices for naming ItemRenderer classes.

Thanks,

João Saleiro

RE: [flexcoders] Re: Best practices for the naming of item renderers ?

[Alex Harui]

I still don't think I understand.  You can call the class anything you want.  
Are you looking to avoid name collisions or something like that?

From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf 
Of João
Sent: Tuesday, December 23, 2008 4:01 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Best practices for the naming of item renderers ?


For example, a List component shows Users. Each user has a picture and
some data, shown thanks to an ItemRenderer class. I would like to know
if there are best practices for naming ItemRenderer classes.

Thanks,

João Saleiro

[flexcoders] Re: Best practices for the naming of item renderers ?

[João]

I'm talking about some kind of coding conventions. In a team
environment it's a good practice to make everyone follow the same
coding conventions. Different programmers give more or less the same
names to classes/methods/properties, etc since all of them follow the
same rules. Unfortunately we do not have rules for naming Item
Renderer classes so I'm researching if there are any coding
conventions for this files - else, we need to create our own conventions.

Thanks,

João Saleiro

Re: [flexcoders] Re: Best practices for the naming of item renderers ?

[Ricky Bacon]

João wrote:
 I'm talking about some kind of coding conventions. In a team
 environment it's a good practice to make everyone follow the same
 coding conventions. Different programmers give more or less the same
 names to classes/methods/properties, etc since all of them follow the
 same rules. Unfortunately we do not have rules for naming Item
 Renderer classes so I'm researching if there are any coding
 conventions for this files - else, we need to create our own conventions.

I'm not aware of any official convention, but I've always found 
descriptive names to be the most helpful.  If you are creating am item 
renderer for a users list, something like UsersListItemRenderer in the 
proper namespace will work.

I like to use this in general so a given class is as descriptive as 
possible:  UserRegisterEvent, UserRegisterCommand, etc.

-Ricky

Re: [flexcoders] Re: Best practices for the naming of item renderers ?

[Manish Jethani]

On Wed, Dec 24, 2008 at 5:30 AM, João joao.sale...@webfuel.pt wrote:
 For example, a List component shows Users. Each user has a picture and
 some data, shown thanks to an ItemRenderer class. I would like to know
 if there are best practices for naming ItemRenderer classes.

I don't know about best practices, but in the above example I would
name it UserRenderer. It's just what I've been doing. Sometimes I even
put all the renderers in a package of their own
(com.example.someapp.ui.renderers.*).

-- 
manishjethani.com