Thanks Mike, I think what you said makes sence, i'm just trying to digest it at the moment and find where it sits in the way i'm thinking.
hmmmmmmmmm --- In [email protected], "Michael Schmalle" <[EMAIL PROTECTED]> wrote: > > > Andy says create a base platform to build everything on top of. > > Well, isn't this what a component is? A base platform to build on and reuse > common functionality? :) > > Seems to my this is what the UIComponent states; "I am creating an interface > for all others to follow. I am the base platform for this kind of > functionality." > > > Web controls are self contained and can hold quite a lot of > functionality whilst maintaining a "plug in" functionality (ie drop > in the dll, and change a few settings in thw web.config) > > I agree and this is exactly how Flex will evolve. OOP is still new in the > web development sense. > > All I have to do is think back to the 1000's of hours I spent playing with > Lego's to get me really excited about what can be build on top of the 'Flash > Platform'. > > I think maybe what you are asking also is, what interface should I implement > when 'creating web controls'. > > When you create that base platform you speak of, you are just defining your > interface that others will implement and extend. > > Really, good high level components will come from an interface that makes > sense and is patterned. > > Peace, Mike > > On 7/28/06, matthew_brailsford <[EMAIL PROTECTED]> wrote: > > > > Many of my dificuilties are down to the fact i'm thinking of things > > from a .NET point of view, so i think how can i make a Flex > > equivilant of a webcontrol? and what not. > > > > Web controls are self contained and can hold quite a lot of > > functionality whilst maintaining a "plug in" functionality (ie drop > > in the dll, and change a few settings in thw web.config) > > > > Ideally i would have a toolkit of components that can make up the > > majority of a systems regular functionality. > > > > But it looks that if i want to use cairngorm i will have to do what > > Andy says create a base platform to build everything on top of. > > > > --- In [email protected] <flexcomponents% 40yahoogroups.com>, > > "Michael Schmalle" > > > > <teoti.graphix@> wrote: > > > > > > Not having anything to do with caringorm; > > > > > > I think some type of login encapsulation would be considered an > > application > > > component.or a component of an application. > > > > > > I think you will see some interesting things start to become > > encapsulated in > > > the future. The word 'Application' is just to broad and could be > > thrown at > > > anything that didn't define some lowlevel encapsulation. > > > > > > In my opinion, component means a design pattern and specific mind > > set you > > > take when you are defining micro pieces of a system in realtion to > > a macro > > > system that could be part of an even larger system. > > > > > > philosophy then kicks in, what are words anyway, components to me > > are more > > > 'the act of closing sub systems'. > > > > > > Peace, Mike > > > > > > On 7/28/06, matthew_brailsford <matt@> wrote: > > > > > > > > Thanks guys, > > > > > > > > You've been a big help, and confirmed what i thought was > > probabley > > > > the case. > > > > > > > > Matt > > > > > > > > --- In [email protected]<flexcomponents% 40yahoogroups.com><flexcomponents% > > 40yahoogroups.com>, > > > > > > "Andrew Trice" > > > > > > > > <andrew.trice@> wrote: > > > > > > > > > > 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: andrew.trice@ > > > > > > > > > > > > > > Office: 866-CYNERGY > > > > > > > > > > > > > > > > > > > > ________________________________ > > > > > > > > > > From: [email protected]<flexcomponents% 40yahoogroups.com><flexcomponents% > > 40yahoogroups.com> > > > > > [mailto:[email protected]<flexcomponents% 40yahoogroups.com> > > <flexcomponents% > > 40yahoogroups.com>] > > > > > > On Behalf Of > > > > matthew_brailsford > > > > > Sent: Friday, July 28, 2006 7:44 AM > > > > > To: [email protected]<flexcomponents% 40yahoogroups.com><flexcomponents% > > 40yahoogroups.com> > > > > > > > Subject: [flexcomponents] Re: Cairngorm Components? > > > > > > > > > > > > > > > > > > > > So you wouldn't be able to encapsulate the business/command > > side > > > > of > > > > > things? > > > > > > > > > > --- In [email protected]<flexcomponents% 40yahoogroups.com><flexcomponents% > > 40yahoogroups.com> > > > > > <mailto:flexcomponents%40yahoogroups.com> , "Stefan Schmalhaus" > > > > > > > > > > > <stefan@> 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > What goes up, does come down. > > > > > > > > > > > > > -- > What goes up, does come down. > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcomponents/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
