Where would you place a your global properties? This is a question that
has always got me.
If the properties such as framerate, gatewayURL, styles, etc need to be in
the class application. They have to be there for two reasons.
1. User defined inspectable properties.
2. variables must be
Hey Ricardo,
just to give you a ruff idea, there are bazillion ways of doing this.
You have two flas, shell.fla and section.fla. In each there's a clip
on Stage called container_mc.
In shell.fla on _root you do:
Application.main(container_mc);
In section.fla on _root you do:
var
Well, I think that there are different ways to accomplish this and every
developer will have his own way. You could store the config variables in
Application, or you could have a Config class that is set up when
Application starts, i.e. getting the configuration from an XML file, and
the rest
Forget about: Application.main(container_mc);
Application.main();
M
On 11/22/06, Michael Nisi [EMAIL PROTECTED] wrote:
Hey Ricardo,
just to give you a ruff idea, there are bazillion ways of doing this.
You have two flas, shell.fla and section.fla. In each there's a clip
on Stage called
Argh! Finally got it working! Thanks all.
I was missing some concepts in OOP for collaboration with teams, like
intrinsic classes and interfaces.
Ok, what I did for a try was having a method in my main class to register
third party movies' main classes. The I also have an interface they should
I forgot I'm thinking they should also have an intrinsic class for an object
with global properties and stuff (not sure about this)
On 11/22/06, Ricardo Sánchez [EMAIL PROTECTED] wrote:
Argh! Finally got it working! Thanks all.
I was missing some concepts in OOP for collaboration with teams,
Personally I'd pass them interfaces rather than intrinsics (mostly
because interfaces are a standard OOP concept but intrinsics are a
Flash-specific 'hackette'), but that's a matter of personal choice.
Ian
On 11/22/06, Ricardo Sánchez [EMAIL PROTECTED] wrote:
I forgot I'm thinking they should
But I need to pass them at least an intrinsic so they can register their
class, wouldn't I?
On 11/22/06, Ian Thomas [EMAIL PROTECTED] wrote:
Personally I'd pass them interfaces rather than intrinsics (mostly
because interfaces are a standard OOP concept but intrinsics are a
Flash-specific
Ah - that's because I don't do this with statics/getInstance(). :-)
If I did, I'd probably do it with a minimal 'locator' class rather
than an intrinsic. e.g.
MyAppLocator.getApp() returns IApp
IApp defines registerMe()
That sort of thing. :-)
But, at the end of the day, whatever works for
Yes, something like a ViewLocator or a special SectionLocator.
Regards
Michael
On 11/22/06, Ricardo Sánchez [EMAIL PROTECTED] wrote:
But I need to pass them at least an intrinsic so they can register their
class, wouldn't I?
On 11/22/06, Ian Thomas [EMAIL PROTECTED] wrote:
Personally I'd
There is another approach to communicate those swfs:
- At your side:
1. Class Application (singleton)
2. Class LoadedSWF (or whatever), abstract class that every swf of the
team development will have to extend. This class could implement any
interface you like, and will have a constructor like
They have to extend the MovieClip class in order to be able to do that, am I
wrong?
I mean, If I load an swf with loadMovie (instead of creating an instance
with new) nothing assures me they are going to implement that class.
I'm a little lost in the relationship between movies and classes
My 0.2,
Basically it really depends on what are they doing. Say you have a
player or main movie. You're tipically going to load different movies
or sections on it. And you want all sections to have a common list of
public properties and methods. Define that list and make it an
interface.
just force them to execute some registration code on first frame of theyr
movie and pass instance which will accept all those calls according to
predefined communication interface
2006/11/8, Ricardo Sánchez [EMAIL PROTECTED]:
Hi!
Where I work we are about to begin a pretty big project
By registration code you mean register to a class? As in Object.registerClass()
?
On 11/8/06, Janis Radins [EMAIL PROTECTED] wrote:
just force them to execute some registration code on first frame of theyr
movie and pass instance which will accept all those calls according to
predefined
When working on a collaborative team on a big project, design patterns
are your best friend. You should check out the Composite design pattern
and/or MVC.
http://www.asserttrue.com/articles/2006/10/27/max-2006
After attending their workshop, I went out and bought the book they
recommended and I
Hi Ricardo, why do you think using Interface or Interfaces will force
you to compile the collaborators code. I don't get the point. They can
compile your Interfaces into their swfs and you can compile them into
yours. That's what interfaces are for. No?
Regards
Michael
On 11/8/06, Ricardo
I'm sorry, I'll explain mysel.
If I make an interface that I want their movies to implement... How do I
load an external movie? To load it instanciating the class I'll have to
compile it... am I wrong?
Can you show some code? I'm pretty lost.
Thanks all.
On 11/8/06, Michael Nisi [EMAIL
Something else I recommend is have somebody who is in charge of
integration and they make sure that everyone who hands them code
thoroughly tests it first. This is how I write my apps when it's just
me, as well, and as a result my code is pretty much bug-free. If their
code can't be tested
You'll probably have a container class which manages loading, etc. It
loads swfs. In the swf a class implements your Interface.The class get
initialized inside the loaded clip, so you don't have to know anything
about it.
interface ricardo.Loadable
{
public function doSomething(Void):Void
}
Same here. Can't imagine to develop without testing anymore. Test
while you code, not afterwards. It let's you design your objects in a
transparent way.
Regards
Michael
On 11/8/06, Steven Sacks | BLITZ [EMAIL PROTECTED] wrote:
Something else I recommend is have somebody who is in charge of
-Original Message-
From: [EMAIL PROTECTED] [mailto:flashcoders-
[EMAIL PROTECTED] On Behalf Of Michael Nisi
Sent: Wednesday, November 08, 2006 11:38 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Writing code for big teams
Same here. Can't imagine to develop without
Hi,
Whilst this suggestion is not good practice if you can get in at the
start of a project - I would recommend doing things the way others have
said, by using interfaces, I was given a very nice workaround for a
situation I got stuck in recently.
I was given about 20 SWF FLA
23 matches
Mail list logo
