hi matt,

i just want to chime in with a little component philosophy. when you make your component, figure out all the options you want (or that are possible in your time constraint). if you have too many features it can get overwhelming. break things down by priority and put them in phases. you may never use the secondary features you thought you wanted so waiting until phase 2 lets you get experience and see what you really need.

one of the most important concepts i've learned in programming is never hardcode. oop, design patterns, model, view, controller, etc. all stem cell from this.

ask yourself, "what do i want?". plan it out, write down what you want, what you want it for and the steps you have to take to get it done. you write your steps down so you can follow them on the days you are brain dead. (end philosophy)

i think you can make your login component "cairngorm" compatible but i'm not yet familiar with cairngorm. if it was me i'd look at it and make the login component compatible with cairngorm and then if you have projects later on that dont use cairngorm make a "cairngorm free" version. i can help you on it once i get cairngorm down (2 weeks from now).

my 2 cents,
judah
PS is there a abbreviation people are using for cairngorm yet? CG? CM? cgm? FCM? crmgrm? abcxyz?

On 7/30/06, bjorn.schultheiss <[EMAIL PROTECTED]> wrote:

Yes,

As far as i can see All you need to incorporate CairgormEventDispatcher.
You will also want to set values at runtime, once the Event is
registered with the controller.

Componentized all views is very efficient in building a view framework.



--- In [email protected], "matthew_brailsford" <[EMAIL PROTECTED]>
wrote:
>
> Hi Guys,
>
> Does anyone have any tutorials on creating components using Cairngorm?
>
> Matt
>


__._,_.___


SPONSORED LINKS
Custom software development Database development software Embedded software development
Offshore software development Software development


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to