Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Welcome, Guest. Please login or register.
May 29, 2017, 08:21:22 AM
Home Help Search Login Register
News: ATTENTION: Spambots must die! Humans must visit http://contact.futurescale.com to request forum access.
Pages: [1]
Print
Author Topic: Runtime vs Compile Time Instantiation of view component classes  (Read 2286 times)
eco_bach
Courseware Beta
Sr. Member
***
Posts: 81


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

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?
Logged
puremvc
Global Moderator
Hero Member
*****
Posts: 2867



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

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