How did you go about deleting the Flash menu?
...helmut
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Sacks
Sent: Wednesday, February 01, 2006 2:41 PM
To: 'Flashcoders mailing list'
Subject: RE: [Flashcoders] Tell me more about "_g
Thanks Ian.
On 2/2/06, Ian Thomas <[EMAIL PROTECTED]> wrote:
>
> On 2/2/06, Manuel Saint-Victor <[EMAIL PROTECTED]> wrote:
> >
> > Okay- let's meander back to the part where I learn from my question
> > So If i create a class with a bunch of static methods from what I've
> read
> > ,
> > I can
On 2/2/06, Manuel Saint-Victor <[EMAIL PROTECTED]> wrote:
>
> Okay- let's meander back to the part where I learn from my question
> So If i create a class with a bunch of static methods from what I've read
> ,
> I can use those methods without instantiating the class. This would
> effectively
PROTECTED]>
> To: "'Flashcoders mailing list'"
> Sent: Thursday, February 02, 2006 9:34 AM
> Subject: RE: [Flashcoders] Tell me more about "_global"
>
>
> >* yawns *
> >
> > -Original Message-
> > From: [EMAI
RTFM & stop this post please
regards
- Original Message -
From: "j.c.wichman" <[EMAIL PROTECTED]>
To: "'Flashcoders mailing list'"
Sent: Thursday, February 02, 2006 9:34 AM
Subject: RE: [Flashcoders] Tell me more about "_global"
* yawns *
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Sacks
Sent: Wednesday, February 01, 2006 9:57 PM
To: 'Flashcoders mailing list'
Subject: RE: [Flashcoders] Tell me more about "_global"
> Apart from that, your ema
ot.
Scott
-Original Message-
From: [EMAIL PROTECTED] on behalf of
Steven Sacks
Sent: Wed 2/1/2006 2:43 PM
To: 'Flashcoders mailing list'
Cc:
Subject: RE: [Flashcoders] Tell me more about "_global"
Let's make classes for everything. Let's make c
> You are clearly an idiot.
>
> Scott
Thanks for noticing. :)
___
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
ly an idiot.
Scott
-Original Message-
From: [EMAIL PROTECTED] on behalf of Steven Sacks
Sent: Wed 2/1/2006 2:43 PM
To: 'Flashcoders mailing list'
Cc:
Subject:RE: [Flashcoders] Tell me more about "_global"
Let's make classes for everything.
A global namespace as an object is all you need for managing global
variables.
...as long as you don't want compile-time type checking, the ability to
watch one of them or fire an event from them *ever*, and so on and so forth.
Oh, wait... I get it now! *You're* that guy whose project I inhe
You are clearly an idiot.
Scott
-Original Message-
From: [EMAIL PROTECTED] on behalf of Steven Sacks
Sent: Wed 2/1/2006 2:43 PM
To: 'Flashcoders mailing list'
Cc:
Subject: RE: [Flashcoders] Tell me more about "_global"
Let's make classes fo
gt; Sent: Wednesday, February 01, 2006 1:30 PM
> To: Flashcoders mailing list
> Subject: Re: [Flashcoders] Tell me more about "_global"
>
> > 7/10 are interactive advertising, which means that I have usually 2
> > weeks(at
> > best) to do something that doesn'
7/10 are interactive advertising, which means that I have usually 2
weeks(at
best) to do something that doesn't relate and never had the time to make
me
own framework.
Has it occurred to you that if you built a class and got in the habit of
using it, it would take exactly the same amount of
Steven Sacks wrote:
A stereotypical cop out. I guess I was wrong. You're not as smart and
clever as I gave you credit for. ;)
I think this conversation is wandering close to the line for what I
assume is a professional mailing list. Take the flame war to personal
email please.
-Adam
> Apart from that, your email takes a kind of
> i-won't-use-names-but-I'll-try-to-offend-you-all anyway tone, and your
> assumptions are just plain wrong on multiple levels. As I
> said simply the
> tone of your email makes it clear there is no use discussing
> it as well, you
> seem to have it a
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pedro
Furtado
Sent: Wednesday, February 01, 2006 3:24 PM
To: 'Flashcoders mailing list'
Subject: RE: [Flashcoders] Tell me more about "_global"
Fast ones :D
7/10 are interactive advertising,
Sacks
> Sent: Wednesday, February 01, 2006 12:27 PM
> To: 'Flashcoders mailing list'
> Subject: RE: [Flashcoders] Tell me more about "_global"
>
> Fast, bug-free ones. ;)
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
>
iscussing it as well, you
seem to have it all sorted out.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Sacks
Sent: Wednesday, February 01, 2006 8:43 PM
To: 'Flashcoders mailing list'
Subject: RE: [Flashcoders] Tell me more about &qu
Mennenoh
> Sent: Wednesday, February 01, 2006 12:26 PM
> To: Flashcoders mailing list
> Subject: Re: [Flashcoders] Tell me more about "_global"
>
> Really well put Steven! I agree 100% - OOP and components are
> great - at
> times. But forcing the issue really only sh
Fast, bug-free ones. ;)
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Robert Chyko
> Sent: Wednesday, February 01, 2006 12:10 PM
> To: Flashcoders mailing list
> Subject: RE: [Flashcoders] Tell me more about "_glo
Let's code everything in one frame when working closely with designers so
we can make
them feel stupid and helpless when they go into our application and can't
find anything and we can feel so superior to them because it's so obvious
and now we have to walk them through it and by doing so can sho
I ask why the curiosity?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robert Chyko
Sent: quarta-feira, 1 de Fevereiro de 2006 20:10
To: Flashcoders mailing list
Subject: RE: [Flashcoders] Tell me more about "_global"
I'm just curious
'Flashcoders mailing list'
Subject: RE: [Flashcoders] Tell me more about "_global"
Let's make classes for everything. Let's make components out of
everything.
There are so many benefits to complicating things and we CAN do it so we
SHOULD do it because it's so c
ct: RE: [Flashcoders] Tell me more about "_global"
Let's make classes for everything. Let's make components out of everything.
There are so many benefits to complicating things and we CAN do it so we
SHOULD do it because it's so clever and smart to do it that way. Let's
Let's make classes for everything. Let's make components out of everything.
There are so many benefits to complicating things and we CAN do it so we
SHOULD do it because it's so clever and smart to do it that way. Let's code
everything in one frame when working closely with designers so we can ma
Yah, as Ian mentioned, you lose all type checking with this
technique. Also, you require that the object be in the global name
space, while a singleton class does not clutter up the global
namespace at all (var globalData = AppState.getInstance();
globalData.foo = "bar"). Finally, how do yo
, 2006 9:43 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Tell me more about "_global"
Steven Sacks wrote:
>
> Making a class for globals is lame. I don't get why people do stuff
> like that. It's completely unnecessary. Here's how I make a
&
Steven Sacks wrote:
Making a class for globals is lame. I don't get why people do stuff
like that. It's completely unnecessary. Here's how I make a
namespace for globals in one line.
On frame one of the root timeline:
_global.APP = {};
Wow. That was so hard.
I can make the same, now it's
That is a really good solution. I think that the reason we do that is
because we are learning how to use object oriented programming techniques
and trying to synthesize various cloudy and sometimes contradictory
recommendations.
M
On 1/31/06, Steven Sacks <[EMAIL PROTECTED]> wrote:
>
> Making a
That is, of course, one way to do it. If you want to throw out all your
type-checking and the like. Personally I like to make the compiler do as
much of my error-checking as possible, rather than having to hunt through by
hand - so prefer to be 'lame'. Particularly because I'm providing a
framework
ailing list'
Cc:
Subject: RE: [Flashcoders] Tell me more about "_global"
Making a class for globals is lame. I don't get why people do stuff like
that. It's completely unnecessary. Here's how I make a namespace for
globals in one line.
On frame one
Making a class for globals is lame. I don't get why people do stuff like
that. It's completely unnecessary. Here's how I make a namespace for
globals in one line.
On frame one of the root timeline:
_global.APP = {};
Wow. That was so hard.
APP.someglobal
APP.someotherglobal
APP.etc
> Natha
I am using _global variables throught my FLAs, probably because I haven't really
been exposed to the negatives of using them, thus not really knowing any
better.
I am interested in conforming to better 'design' standards and am familiar with
the Singleton Design Pattern. Any chance you could prov
also, if i read your code (or my own a few months after i've written
it), i have o way of knowing where that mysterious
_global.settings.maxItems property has been defined so i can change
it.
mark
--
http://snafoo.org/
jabber: [EMAIL PROTECTED]
___
Flas
I generally keep at least one singleton class which is responsible
for storing global properties. I make those properties accessible
with getters and setters so that I can allow changes in those
properties to trigger events. You can't really do that if you use
_global to store your data. Al
Hi,
For me one of the _global biggest problems is that EVERYONE,
EVERYWHERE can modify the value of a global variable. There's no
private attribute at all.
AND be careful because one Player 6 movie can NOT see global variables
of a Player 7 movie. And vicecersa, of course.
My 2 cents.
Bye!
On
36 matches
Mail list logo
