isn't this the beauty of Ruby? ... It enables you to extract common behaviour into a module... I think the best way to go would be to see what are the "profile" fields naming conventions. You then apply these conventions to the models you need to display as a "profile" and extract the common methods to a module which you include with some acts_as_... macro (just to stay with readability and conventions...)
What do you think? David On Nov 19, 10:27 pm, Levi Rosol <[EMAIL PROTECTED]> wrote: > So one of the next steps I need to take with CE is to implement some > sort of Group functionality. The idea is that any user can create a > Group. A Group will have nearly all of the same functionality that a > User has in terms of a profile, comments, photos, friends (but called > members), etc.. > > What are your thoughts on the best way to approach building this? I > think because of how tightly everything is tied to the existing User, > the only route to go with this is to create a new model from scratch > and do a lot of copy/pasting to bring over the existing User > functionality. > > Got a better way? Cause this doesn't seem very DRY. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
