PureMVC Architects Lounge

Announcements and General Discussion => General Discussion => Topic started by: eco_bach on February 10, 2012, 09:11:56



Title: Runtime vs Compile Time Instantiation of view component classes
Post by: eco_bach on February 10, 2012, 09:11:56
Hi
Working with a vendor who was created a PureMVC application but in a way I am not familiar with. All of the view component swfs are essentially 'dumb' containers with undefined library MovieClip classes which are instantiated only at runtime. They are 'composed' by their corresponding view classes and mediators. I can't see any advantages to architecting this way.
1-Almost impossible to delegate creation of self contained view components to other developers

2- All the code is compiled into the main swf, making it rather large and unwieldly.

Are there any advantages I am not aware of?


Title: Re: Runtime vs Compile Time Instantiation of view component classes
Post by: puremvc on February 12, 2012, 09:41:35
Are there any advantages I am not aware of?
Can't think of any myself.