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 (<[hidden email]>) escribió:
I saw initialView in every example in Royale.
This seems strange for me.
Why not put the component instance directly on mxml ?
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.
The Basic Application tries to encourage an MVC pattern to try to have clean separation of data and views of data and controller logic. In theory, as you eventually try to target other platforms/runtimes/devices, you may need to only change the view or controller, but not the data if you have good separation.
The emulation components do not have an initialView.