royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Douglas McCarroll <list.apache-royal....@brightworks.com>
Subject Re: Migrating Enterprise Flex Application
Date Wed, 18 Jul 2018 13:07:16 GMT
> Cairngorm.swc
> CairngormEnterprise.swc

> I understand the Flex programming model but don't have any
> hands on experience.

Some years ago I worked with Cairngorm and another Flex framework named
Mate, and was also looking into other frameworks such as PureMVC. At this
point I don't remember them in detail, but I can make a few comments which
may be helpful, or may be obvious.

Each of these frameworks does at least two things: It defines a system for
organizing your code and it provides infrastructure code which enables this
approach.

If you switch from one framework to another, e.g. from Cairngorm to PureMVC
you'll need to understand the way each framework works, then rearrange your
code so that it works within the new framework. Probably the hardest bit
will be learning/understanding the two frameworks. Once you do, modifying
your code shouldn't be too difficult. You'll need to make some changes but
most of your existing code will still be usable as written.

IIRC, PureMVC had a good reputation. As their website brags (
http://puremvc.org/) it's been ported to a whole bunch of languages.

Some would argue that one doesn't need to use a framework, or can create a
simple framework oneself. I liked using frameworks because they defined a
standard way of doing things, which eliminated the need for teams to agree
on how they would organize their code (or, worse yet, allow their code to
devolve into a disorganized mess). But I also felt that Cairngorm, as
least, had more levels of abstraction than I could understand the need for.

Douglas

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message