RE: [flexcomponents] Re: Cairngorm Components?

[Andrew Trice]

You *could*, but it wouldn’t really fit with the cairngorm architecture.  I’d recommend just creating common views/commands for login functionality, and just reusing those per project.  You could create a base project that you use as a template for future projects that includes a basic setup of caringorm and any common elements (such as a login).   -Andy   _____________________________________ Andrew Trice Cynergy Systems, Inc. http://www.cynergysystems.com   Blog: http://www.cynergysystems.com/blogs/page/andrewtrice Email: [EMAIL PROTECTED] Office: 866-CYNERGY    From: flexcomponents@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of matthew_brailsford Sent: Friday, July 28, 2006 7:44 AM To: flexcomponents@yahoogroups.com Subject: [flexcomponents] Re: Cairngorm Components?   So you wouldn't be able to encapsulate the business/command side of things? --- In flexcomponents@yahoogroups.com, "Stefan Schmalhaus" <[EMAIL PROTECTED]> wrote: > > > We create many different solutions, all of which will have a log in, > > so how would you encapsulate the login functionality so that you > > could just re-use it per project? > > As far as I understand the Cairngorm concept, a "login component" > could only be a view (based on a Panel with username/password text > fields, a login button etc.) that can be used in a ViewStack, for > example. > > Stefan > __._,_.___ SPONSORED LINKS Custom software development Database development software Embedded software development Offshore software development Software development YAHOO! GROUPS LINKS  Visit your group "flexcomponents" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___