How does PureMVC mobility benefit the app developer?

Question

One of the stated goals of the PureMVC framework is to avoid platform dependency in order to be portable. Given that, due to differences in language and API, the application code will always be highly platform dependent, and to avoid platform dependencies, the system reinvents the wheel and / or provides only a set of functions with the lowest common denominator, how portability from the framework is useful to me as an application developer?

Answer 1

I worked with PureMVC. They are trying to implement their material in quite a few languages. You may be right about the least common denominator, but overall it's not a bad structure, and I saw a really nice AS3 app in PureMVC.

I don't think they talk about portability in terms of porting actual code. The idea is that you use a generic MVC architecture that you can apply to other projects and other languages.

They are trying to say that if you become familiar with the PureMVC template, you can potentially enter the new PureMVC code base, even if it is a different language, and you already know the land.

You can also say that developers who develop good PureMVC skills are more likely to develop good habits that will translate as you move from language to language. But then again, maybe not .. for the reasons you mentioned.

Answer 2

We are using PureMVC on two projects now, and, in my opinion, trying independent language independence is a big load.

The promise is to jump right in the project, because the framework already knows, it doesn’t seem necessary to me if the languages ​​are no longer very similar (C # in java will make sense, as3 to php not) - I agree that it is useful to have well-known ways of solving things, but for this, “simple” templates are good enough.

However, I also do not agree with the use of various templates that the project uses, so our choice not to use it in the next project may be related to both problems, and not just to the attempt of language / platform independence.

Answer 3

Portability PureMVC helps you when porting or overriding in another language.

I can’t count the number of platforms and languages ​​in which I wrote the code that are now extinct, and for which, even if I still had the source code, it would be mostly useless and should be rewritten from scratch today, since the code is usually was 100%.

But all application code should not be highly platform dependent. Viewing components and services (the boundaries of your application) will certainly be, but your application logic, which is sandwiched between the borders, does not have to be.

The scope of PureMVC is really quite narrow; just to help you split your code into three levels that are forbidden by the MVC meta-template. There is no reason this code should be tied to your platform in order to be optimal.

When the time comes for the transition, you will understand that the participants in the structure and their roles, responsibilities and cooperation remain the same. This will allow you to understand the syntactic differences of the language, recreate the components and services of the presentation. At least you don't have to completely redesign.

And for the case of redefinition in another language, imagine that you are trying to capture a significant part of the mobile market using your application. The market is so broken that you have to implement the same program on two or more Windows Mobile, iPhone, Flash and Java. We are sure that you will probably have separate teams responsible for the applications, but why do they have a completely different architecture? With PureMVC, you can have a single architecture for all versions of your application.

- = Cliff>

Answer 4

PureMVC is the only real option for Flash Platform developers who choose not to use the Flex Framework. For some projects, the cost of Flex is too high (it happens!).

I like the prototype in Flex, and then rip it off and replace my views with custom components when the application is almost done. PureMVC makes this very easy to do with this reseller template. I'm not sure that there is another framework that would allow me this workflow.

Personally, I think PureMVC has gone too far with portability goals: I like the fact that it works with Flash and Flex (for the reasons mentioned above), but I feel like it should have stayed there and used the native Flash Player event architecture.

Answer 5

Are there any examples of using PureMVC to create and migrate applications on multiple platforms?

My company is creating a Flex application that may be required to migrate to other platforms:

• Silverlight (most likely)
• Mobile (maybe)
• Desktop (maybe not just AIR!)
• TVs (maybe in the end)

I see PureMVC as a framework if it can facilitate porting and maintenance. I am curious to see if other PureMVC applications have been placed on another platform, and that their experience has been with porting, and then developing development for an application on multiple platforms in parallel.

Greetings

Kartik

Answer 6

PureMVC does not rely on a platform for its internal operations (Flash Events, etc.). Thus, although he does not make the transfer easier, let's say, he can help simply by showing us his friendly and familiar face, wherever we decide :-)