Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought

Welcome, Guest. Please login or register.
November 24, 2017, 02:54:53 PM
Home Help Search Login Register
News: Please DM @puremvc on Twitter to gain forum access. Spambots are why we can't have nice things.
Pages: [1]
Author Topic: Runtime vs Compile Time Instantiation of view component classes  (Read 2580 times)
Courseware Beta
Sr. Member
Posts: 81

View Profile
« on: February 10, 2012, 09:11:56 PM »

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?
Global Moderator
Hero Member
Posts: 2871

View Profile WWW
« Reply #1 on: February 12, 2012, 09:41:35 AM »

Are there any advantages I am not aware of?
Can't think of any myself.
Pages: [1]
Jump to: