Yes, it's the same back-end used by Flex Builder, if I'm not mistaken. Fdb is indeed almost unusable without a GUI, unless you're a command line freak and a bit of a masochist, IMO (and you never tried a "visual" debugger).
The idea of integrating a GUI for fdb into FlashDevelop has been mentioned in the FD forum a number of times. I don't know the current status of this feature, though. Last time I checked (about 6 or 7 months), it was on the wish list, but I couldn't find any info on its status. I hope they manage to get it working. It'd be awesome. Cheers Juan Pablo Califano 2009/8/12 Ian Thomas <i...@eirias.net> > On Wed, Aug 12, 2009 at 9:22 PM, Matt Gitchell<m...@moonbootmedia.com> > wrote: > > Yeah but if you want to debug/profile anything, you gotta pay that 5 > bones > > you mentioned earlier in this scenario, and I dunno, a coding environment > > without debugging now seems a little silly to me. I wish they'd do a > > standalone version of the profiler in Flex Builder, to be honest. > > Just as a complete aside, in case people don't realise, there _is_ a > debugger included with the Flex SDK (i.e. the free downloadable SDK). > It's a command-line shell called fdb; it's a bit of a pain to use, but > it can be a godsend if you don't have a full Flex license and if > inserting trace() statements everywhere hasn't helped. :-D > > Ian > _______________________________________________ > 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
