Hi,
thanks for both your replies Robert Amir.
We are not quite ready to move this project over to Flex, AS3, although I'm
wondering if I should reconsider and force it:). The current system consists
of somewhat 500 to 600 swf's, and although the system is pretty cool, some
stuff needs a bit of
Sounds to me that your over complicating a bit. What you probably could
do is provide a base set of classes for you model/data and then one or
more adapters to add the needed conversion to and from framework
specifics. In general I think that while ease of reuse is a great idea,
you aren't
Hi JC,
Your solution is quite good. Using an 'Abstract Interface' is always
encouraged :)
The guideline goes like - 'Program to Abstraction not to Implementation'
Unfortunately AS3 does not (yet:) allow Generics / Collection Type
safety - so we are still forced to make sure we
do the right
Hi,
we are looking into using another component set than the v2 architecture.
However we don't want to switch over and over again, and frankly as the
architecture developer I dont want anything to do with components at all.
So I was thinking about a setup where I write component interfaces such
4 matches
Mail list logo