Sure... Should have probably explained the curiousity more up front anyway...
I guess I'm just looking at it from the other side of the fence - I currently work with a web-based application in which parts of the front-end are done in Flash (and getting the rest of the pieces over to Flash is part of my job). A few of the screens are fairly old and contain a lot of "non-traditional" coding practices, like _global and the like. Basically in my experience these have been - for me - harder to follow, debug, etc. - maintain in general. So I guess I kinda look at things like _global in a bad light because of the experience I've had with them - and I was just curious as to what end product you were making that you felt _global were useful. I think the biggest difference between what we do is that I've never had to pass my code of to a designer to make pretty - the few of us here that write the ActionScript also design the interfaces as well - so having some one else look at it and have no clue what is going on has never been an issue really. (And this really isn't a problem - cause we aren't doing anything too fancy e.g advertising) -----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, 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. Still I insist in a one frame architecture, and leave the all the item in the library for the designers. May 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 to know what kind of projects these are that you are working on? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pedro Furtado Sent: Wednesday, February 01, 2006 2:52 PM To: 'Flashcoders mailing list' Subject: RE: [Flashcoders] Tell me more about "_global" Supported! I dare to add a few thoughts of me own. A good application is one that works, an excellent application is one that works fast. That said and with utra-tight deadlines together with designers having to open my fla so they can make it pretty while I make the next app, _global rules! This of course doesn't apply to frameworks and such, but still there's room for everything. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Sacks Sent: quarta-feira, 1 de Fevereiro de 2006 19:43 To: '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 clever and smart to do it that way. 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 show them how smart and clever we are. Let's stroke our egos to prove what smart coders we are and program job security into our applications by making it extremely difficult for our clients to hire anyone else to work on our code, especially considering we might not be available (busy, vacation, dead) to help walk anyone through the complicated messaging system we've put into place to do something as simple as storing global variables. It's such a clever way of doing things, don't you see? We've built a better mousetrap! Those people using a simple global namespace objects are suckers! I'm not saying variable watchers and events don't have their place, but we're talking about a global namespace to store variables available to the entire application, a replacement for _global and the conflicts that can arise from it, something that has been done longer than you've been coding. You're acting like a simple global namespace to store variables is only for noob coders and that really smart coders make their code super complicated. You guys are the reason Dreamweaver MX 2004, Photoshop 7, etc. take 10-20 seconds to start up instead of 1-3 like their predecessors. You guys are the reason many clients have bad tastes in their mouths from working with independent contractors. Why not apply your cleverness and creativity to planning your next D&D campaign or go learn a real programming language like C and learn to program games if you're so smart. As far as debugging goes, I've never had trouble with standard debugging techniques. You know, like trace() and NetDebug.trace(). Quick and easy. Here's my debug code: import mx.remoting.debug.NetDebug; NetDebug.initialize(); _global.out = function(m) { trace(m); NetDebug.trace(m); } Oh noes! It's not complicated enough for you! Feel superior in your complicated debugging style! ;) _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
