...split the thread based on Jesse's question
a helper object is an object that helps :) it is a kin to the gopher object which goes for this and goes for that. ha! Thought you answered this on your blog? Oh, that was strictly the ViewHelper, eh? Got me thinking though....in OOP terms just what is a "helper object"? I don't recall seeing these in say Java, or maybe they have a different name. DK On 11/2/05, JesterXL <[EMAIL PROTECTED]> wrote: > What's a helper object? > > ----- Original Message ----- > From: "Roger Gonzalez" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, November 02, 2005 11:22 PM > Subject: RE: [flexcoders] To code-behind or not to code-behind? > > > You might want to search the archives, we had a long chat about this > recently. > > The conclusion that I personally push is to avoid relying on script > source inclusion but rather to either > > a) create custom base classes and derive your MXML components from them, > and/or > b) aggregate helper objects, and/or > c) factor the MXML into metacomponents with well defined interfaces. > > I find that inline OR external script snippets get messy and out of > control, and you're generally better off following standard OO > programming. > > Another way of looking at it is that if your MXML is looking more like > AS code than like MXML, you're probably better off refactoring things. > When any given MXML class is down to 10-15 lines of script, things look > pretty clean, and it seems better to just put it inline. > > (personal opinions here, we argue this one internally quite a bit!) > -rg > > > -----Original Message----- > > From: [email protected] > > [mailto:[EMAIL PROTECTED] On Behalf Of Julian Suggate > > Sent: Wednesday, November 02, 2005 7:31 PM > > To: [email protected] > > Subject: [flexcoders] To code-behind or not to code-behind? > > > > Gidday everyone, > > > > Years back, I wrote php scripts with code embedded in the > > html and it led to maintenance hassles. Since then, I've > > migrated to Java and now .NET and what I liked about their > > models was the ability to separate the code into > > "code-behind", something done quite elegantly in ASP.NET. > > These eliminated a lot of the maintenance problems I'd > > encountered earlier with PHP. > > > > So when I saw macromedia's examples of mxml with > > <mx:Script>...</mx:Script> blocks embedded directly into the > > mxml, I immediately searched for a way to avoid this. I found > > that i could add a source=".." attribute to the mx:Script > > element and the AS code would be included by the compiler > > from an external file at compile time. The IDE was even smart > > enough that any elements I'd defined with id attributes in > > the mxml showed up with intellisense in the included AS file > > (I am using Flex Builder 2, not sure if FB1.5 had that > > feature or not). > > > > But now I'm having second thoughts. It kinda feels like going > > against the grain. I don't want to carry old biases into a > > new paradigm unnecessarily. I read an article by Aral Balkan > > (of ARP fame) endorsing the code-behind approach quite > > strongly, but by the same token, all sample apps from the > > Cairngorm team freely mix mxml and AS code, as do examples > > from macromedia themselves. > > > > I note though, that the Cairngorm framework itself is all > > pure AS; it is only the sample apps that use inline actionscript. > > > > I can't seem to find a best practice anywhere, because for > > every framework/example/article I find that seems to hint at > > one way of doing things, I find another one that suggests the > > opposite! Has anyone else with more Flex experience than me > > answered this question, particularly in terms of which > > approach is easier to maintain? > > > > At this stage, any hints would be appreciated! > > > > TIA, > > Jules > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > > > > > > ________________________________ > > > > YAHOO! GROUPS LINKS > > > > > > > > * Visit your group "flexcoders > > <http://groups.yahoo.com/group/flexcoders> " on the web. > > > > * To unsubscribe from this group, send an email to: > > [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > > * Your use of Yahoo! Groups is subject to the Yahoo! > > Terms of Service <http://docs.yahoo.com/info/terms/> . > > > > > > ________________________________ > > > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > > > > > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > > > > > > > -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it? ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
