Re: [flexcoders] Fundamental bug in FlexBuilder 1.5?
Hey Vinny, C'mon Aral, don't be so modest. Give us the complete list ;-) Emailed, off list ;) Seriously, though, it's easier to include my sig in the first post I make to a new list than spend a paragraph with the usual, Hi, I'm blah-and-blah, I do blah-and-blee... Take care, Aral
RE: [flexcoders] Fundamental bug in FlexBuilder 1.5?
Aral, Its been identified as a bug and filed with MM, probably numerous times J When the Cairngorm .9 release happened, there was a slew of those reports. For now, Ive used a script block simplest possible thing that could work! Roberts From: Aral Balkan [mailto:[EMAIL PROTECTED] Sent: 01 February 2005 01:29PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Fundamental bug in FlexBuilder 1.5? Hi all, Long-time lurker, first-time poster... I wanted to draw your attention to an issue that I'm having with Flex Builder: Basically, the Preview/Run/Debug functionality stops working when you subclass mx.core.Application and/or mx.containers.Form in your applications. Of course this is a perfectly legal thing to do and, actually, the ARP framework will be recommending this as a best practice (among other things,it makes migrating from Flash to Flex child's play.) It also gets around having to mix code into your MXML files -- which is a nasty practice akin to how we used to #include script files in ActionScript 1 in Flash. In any case, this is a fundamental use case and it appears that Flex Builder doesn't currently support it. I posted about this on my blog in more detail, with a barebones sample to demonstrate the bug: http://www.flashant.org/index.php?p=273more=1c=1 I am still holding out hope that there is a way to override this default behavior in Flex Builder to tell it that it's ok to preview a subclass of Application/Form but I haven't been able to find such a way using the Dreamweaver extensibility APIs. Perhaps someone from the Flex team will have a potential solution/workaround for this. All the best, Aral -- Aral Balkan Managing Director, Ariaware Ltd. Best Practices Flash Flex Development course - March, 2005. London UK Tel: +44 (0) 870 7542240 Fax:+44 (0) 870 7542240 Mob: +44 (0) 779 5551278 Web: http://www.Ariaware.com Blog: http://www.FlashAnt.org Macromedia Certified Instructor Flash MX 2004 Advanced ActionScript Development Flash MX 2004 Professional ActionScript Development Director of Educational Content - Ultrashock Author - Friends of ED, Macromedia DevNet Director - London MMUG
RE: [flexcoders] Fundamental bug in FlexBuilder 1.5?
Aral, Long-time lurker, first-time poster... I wanted to draw your attention to an issue that I'm having with Flex Builder: Basically, the Preview/Run/Debug functionality stops working when you subclass mx.core.Application and/or mx.containers.Form in your applications. This is a known bug in Flexbuilder that was raisedup on this list when people started trying to build applications using the CairngormApplication tag that we advocated in the 0.9 release of Cairngorm. Currently there is no workaround other that using the mx:Application tag if you want to work in Flexbuilder. Macromedia are aware of the issue - we raised it and it was acknowledged as a bug. It doesn't however mean that people will have to dump lots of code in their MXML files; using the Application tag, developers are still free to create their own ActionScript 2.0 classes, and if you don't want to import them and instantiate them within mx:Script blocks, you can instantiate them "MXML-fashion" using namespace declarations. Best, Steven -- Steven WebsterTechnical Director iteration::two This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies ofit, immediately.Please also note that while software systems havebeen used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.
RE: [flexcoders] Fundamental bug in FlexBuilder 1.5?
Aral BalkanManaging Director, Ariaware Ltd.Best Practices Flash Flex Development course - March, 2005. London UKTel: +44 (0) 870 7542240Fax:+44 (0) 870 7542240Mob: +44 (0) 779 5551278 Web: http://www.Ariaware.com Blog: http://www.FlashAnt.org Macromedia Certified InstructorFlash MX 2004 Advanced ActionScript DevelopmentFlash MX 2004 Professional ActionScript Development Director of Educational Content - Ultrashock Author - Friends of ED, Macromedia DevNet Director - London MMUG C'mon Aral, don't be so modest. Give us thecomplete list ;-) Best, Vinny From: Aral Balkan [mailto:[EMAIL PROTECTED] Sent: dinsdag 1 februari 2005 12:29To: flexcoders@yahoogroups.comSubject: [flexcoders] Fundamental bug in FlexBuilder 1.5? Hi all,Long-time lurker, first-time poster... I wanted to draw your attention to an issue that I'm having with Flex Builder: Basically, the Preview/Run/Debug functionality stops working when you subclass mx.core.Application and/or mx.containers.Form in your applications.Of course this is a perfectly legal thing to do and, actually, the ARP framework will be recommending this as a best practice (among other things, it makes migrating from Flash to Flex child's play.) It also gets around having to mix code into your MXML files -- which is a nasty practice akin to how we used to #include script files in ActionScript 1 in Flash. In any case, this is a fundamental use case and it appears that Flex Builder doesn't currently support it. I posted about this on my blog in more detail, with a barebones sample to demonstrate the bug:http://www.flashant.org/index.php?p=273more=1c=1I am still holding out hope that there is a way to override this default behavior in Flex Builder to tell it that it's ok to preview a subclass of Application/Form but I haven't been able to find such a way using the Dreamweaver extensibility APIs. Perhaps someone from the Flex team will have a potential solution/workaround for this.All the best,Aral -- Aral BalkanManaging Director, Ariaware Ltd.Best Practices Flash Flex Development course - March, 2005. London UKTel: +44 (0) 870 7542240Fax:+44 (0) 870 7542240Mob: +44 (0) 779 5551278 Web: http://www.Ariaware.com Blog: http://www.FlashAnt.org Macromedia Certified InstructorFlash MX 2004 Advanced ActionScript DevelopmentFlash MX 2004 Professional ActionScript Development Director of Educational Content - Ultrashock Author - Friends of ED, Macromedia DevNet Director - London MMUG
