I originally was all go to separate the view and code using the
source prop in a script tag. What i didn't like about this was that
it was a loose link. Code behind makes this a more solid link but
after experimenting with that also i've found I end up with some many
files open it begins
What is your reasoning to use code behind? Why would you want to double
every class and add an additional inheritance layer just to separate Mxml
from ActionScript? Why would you want to declare every component you are
using twice, once in AS and the second time in Mxml? Is it to separate
and last but not least you can put your Mxml files into packages just like
classes - that's what they really are after all: classes.
Cheers
Ralf
On 2/8/07, Ralf Bokelberg [EMAIL PROTECTED] wrote:
This is just my personal view though, i'm not aware of an official
version.
Cheers,
Ralf.
On
This is just my personal view though, i'm not aware of an official
version.
Cheers,
Ralf.
On 2/8/07, Ralf Bokelberg [EMAIL PROTECTED] wrote:
What is your reasoning to use code behind? Why would you want to double
every class and add an additional inheritance layer just to separate Mxml
from
:[EMAIL PROTECTED] On
Behalf Of Ralf Bokelberg
Sent: 08 February 2007 21:25
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] What's the official consensus of using
CodeBehind??
This is just my personal view though, i'm not aware of an official
version.
Cheers,
Ralf.
On 2/8/07, Ralf
IMHO, I think it was very helpful in Flash Arp ages. As the view was
binary code and was very handy to have the code in classes to be able to
support version control, unit test, etc.
But now since mxml is also a text file I think it does not have too much
sense to do that.
Besides that you
:[EMAIL PROTECTED] On
Behalf Of Ralf Bokelberg
Sent: Thursday, February 08, 2007 3:20 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] What's the official consensus of using
CodeBehind??
What is your reasoning to use code behind? Why would you want to double
every class and add an additional
I must admit that I just don't understand the interest in code-behind.
When you write
MyComponent.mxml:
mx:Canvas
mx:Script
public var foo;
public function bar():void { ... }
/mx:Script
/mx:Component
you are writing a subclass
8 matches
Mail list logo
