Difference between flight.component() and defineComponent()

[Bogdan Begovic]

I have been using Flight since version 1.1.1 and, for creating new components, I have been using a new require module that returns function defineComponent() with constructor and mixins as parameters. Today a have seen this flight.component() construction of components in a page.

So I wanted to ask if anyone can explain to me what is going on here, will defineComponent be deprecated and when to use one or the other?

[Gabriel Pugliese]

It's just namespacing. 

When you use "define(['flight/lib/component'], function (PARAM)...", the PARAM can be any string and is defined only inside the scope of the function. In examples they named it defineComponent.

But if you use flight without an AMD lib (like using a script tag), "flight" is a global var that has the method "component", that is exactly the same of the "defineComponent" function. (flight.component === defineComponent)

Hope this is clear enough

Gabriel Pugliese
CodersTV.com
@coderstv

[Bogdan Begovic]

@Gabriel Thanks, wasn't aware of this :)