Re: initialView in Royale
OK, thank you. -- Sent from: http://apache-royale-users.20374.n8.nabble.com/
Re: initialView in Royale
Hi Hugo, This exactly how Royale works. It's just mark that following View is initial. You have more such of a section in whatever component you creating. For example each component had section "model" or "beads". I personally like the idea from the very beginning and haven't seen any strange in that. It force you to some organization, granulation etc. If I have one View I may have one mode - everything small and easily managable - Not with 1000 lines of code. Piotr On Sat, Nov 17, 2018, 12:06 PM hferreira wrote: > OK, thank you. > > > > -- > Sent from: http://apache-royale-users.20374.n8.nabble.com/ >
Re: initialView in Royale
OK, thank you. -- Sent from: http://apache-royale-users.20374.n8.nabble.com/
Re: initialView in Royale
maybe others could respond to this. That was as is when I came. I think something similar was in Flex mobile components, although at that time I think it was done that way to avoid instantiation of views and help the poor mobile performance at that moment El sáb., 17 nov. 2018 a las 11:02, hferreira () escribió: > I saw initialView in every example in Royale. > This seems strange for me. > Why not put the component instance directly on mxml ? > > > > -- > Sent from: http://apache-royale-users.20374.n8.nabble.com/ > -- Carlos Rovira http://about.me/carlosrovira
initialView in Royale
I saw initialView in every example in Royale. This seems strange for me. Why not put the component instance directly on mxml ? -- Sent from: http://apache-royale-users.20374.n8.nabble.com/
