Quick poll on debugging and tooling for Flex and PHP projects

As you know, one of my focuses as a Platform evangelist is Flex and PHP integration. Thus you can imagine I spend quite a lot of time doing Flex and PHP projects or research around these technologies. Lately I’ve been working on workflows for PHP and Flex (tooling, debugging, libraries) in light of the new tools (or new versions) we have been developing at Adobe. While some of these findings will see the light as articles, others are more intended as suggestions or feature request for upcoming versions of Flash Builder.

I’m really curious to find out:

  • What tools are you using?
  • What do you use for debugging?
  • What frameworks (AMFPHP, Zend Framework, Doctrine etc) do you use when working on Flex and PHP projects?
  • And the most important question: What features do you think Flash Builder needs in order to make you a happier/richer developer?

Please take some time and drop a comment with your thoughts around these questions.

And because I understand it takes some time to answer these questions, I want to give away three Flash Builder 4 licenses. I will choose randomly three lucky people from those who take the survey. The winners will be announced at the end of March, however you’ll get the licenses once we release Flash Builder 4 (now it is in Beta 2). Make sure you fill in your real name and a valid email address.

LATER EDIT: The winners of this raffle are: Mario Kralj, chandra shekhar pant, and Ben Dalton! Congratulations and pretty soon you’ receive the license.

59 thoughts on “Quick poll on debugging and tooling for Flex and PHP projects

  1. 4 What features do you think Flash Builder needs in order to make you a happier/richer developer?

    — While creating custom component from the existing component, add override the protected methods option with generate constructor with super class option. So that custom code fast and with that learners will know more.

  2. 1) While creating Custom Components I didn’t want to expose the (mxml) controls directly in Code Hinting. So Add a property like ‘accessor’ which accept ‘public/private/internal’ as parameters. if its ‘private’ hide that control from code hinting when object for custom component is created.

    2)During Debugging add feature so that we can take the code execution backward. i.e if a method is from line 10 to line 20 and we are in line 18, add a functionality so that we can take the execution back to line 12(This feature is there in Visual Studio.Net)

  3. So I might be a few days late to the game, but since I specialize in PHP integration I thought I would throw in my two bits. :)

    What tools are you using?
    I am currently using FB4, and Zend Studio 7. (Separately unfortunately at this point.)

    What do you use for debugging?
    when I need integrated development / Debugging, I end up using FB 3 plugged into Zend 6. I really really really really really want to plug FB 4 into Zend 7.1 :)

    What frameworks (AMFPHP, Zend Framework, Doctrine etc) do you use when working on Flex and PHP projects?
    I used to use AMFPHP, but I have since switched to Zend due to better debugging support, and native data-types between Flex and PHP.

    And the most important question: What features do you think Flash Builder needs in order to make you a happier/richer developer?

    The ability to read my mind? That would be sweet. j/k. In all seriousness, I think Flash Builder is headed in the right direction in it’s integration of PHP. The one feature that I would really like to see mature more is the ability to plug existing PHP into Flash Builder’s code generation tools. It has been my experience in the past that it seemed to get all confused, and didn’t play nicely w/ PHP changes, especially if it was the addition or removal of functions. :/ Also, the data types that it tries to generate are confusing as heck for most people to be able to look @.

  4. 1 – Tools :
    – Flash Builder Beta 2
    – Flex 3 (Standalone)
    – TextMate

    2 – Debugging :
    – Flex 3 / Flash Builder Debbuger

    3 – Frameworks :
    – Cairngorm
    – Zend Framework
    – AMFPHP

    4 – Flash Builder Improvements :
    – Faster compiler

  5. 1 – Tools :
    – Flash Builder Beta 4
    – Notepad++ for PHP
    – Eclipse for Java
    2 – Debugging :
    – Flash Builder Debbuger
    3 – Frameworks :
    – SWIZ Framework
    – Zend
    – AMFPHP

  6. 1: Tools
    – Flex Builder 3 Pro Eclipse Plugin
    – UEStudio ’09 (www.ultraedit.com)
    – UltraCompare Pro
    – Subversive
    – FlexPMD

    2: Debugging
    – Built-in Eclipse Debugger
    – Custom runtime debug tool
    – FlexSpy

    3: Frameworks
    – Cairngorm

    4: One interesting thing I’ve been thinking about would be to have some option in eclipse to hide trace statements. I use trace statements a bit for some of my debugging, but I hate to leave them in the code because it becomes cluttered. If I had an option to toggle the visibility of them in the editor I could leave them there and toggle the “show trace statements” when I need to add/modify the existing ones. Along with this, it would be nice to be able to set a value on a class by class basis to disable any trace statements for that class. (So when I’m focusing on a specific class for debugging, I can enable the tracing statements for just that area, so as not to clutter the console output)

  7. @Nabeel

    LATER EDIT: The winners of this raffle are: Mario Kralj, chandra shekhar pant, and Ben Dalton! Congratulations and pretty soon you’ receive the license.

Leave a Reply

Your email address will not be published. Required fields are marked *