david zuckerman/adobe

Making Flex Builder development exciting since 2005

1. Phillip Kerman 05.09.08 / 12pm

   namespaces? or maybe marching ants around the outside of the app. Oh, maybe override… wow–yeah, that’s needed.
2. Phillip Kerman 05.09.08 / 12pm

   dang, I’m thinking overload!
3. david.z 05.09.08 / 12pm

   alright, two points for you. new namespace hinting…plus override indications…there’s more though
4. Dan Schultz 05.09.08 / 1pm

   oh boy, package icons instead of just folders! do the packages show up as dot-notation in the project explorer? also, any chance you can make this bug part of your “pet features”?

   https://bugs.adobe.com/jira/browse/FB-12369

   i’ve submitted a couple other refactoring bugs, but they have gone largely unnoticed.
5. david.z 05.09.08 / 1pm

   So I just raised the attention of that bug…any other bugs that you feel are stagnant?
6. DasFX 05.09.08 / 1pm

   I see new icons in the Outline view.
7. Dan Schultz 05.09.08 / 1pm

   This one is a bugger:

   https://bugs.adobe.com/jira/browse/FB-11950

   Thanks David!
8. Ben Clinkinbeard 05.09.08 / 7pm

   It would be nice to have some auto-complete help on the things we write a billion times a day. “public ” should prompt me with var and function. “override ” should create a prompt, etc.

   Allowing event constants in event metadata would also be nice, like this: [Event(name=MyEvtClass.SOME_EVENT, type=MyEvtClass)]

   Somewhat related, the prompts for addEventListener should use actual event constants that exist, not just the string values in event metadata converted to const format.
9. Ben Clinkinbeard 05.09.08 / 7pm

   Oh, and organize the imports in Script blocks in MXML files. Please.
10. kafka 05.11.08 / 7am

    great class name..
11. Tink 05.11.08 / 12pm

    metadata that actually uses code as Ben’s example (i.e. using a constant and a class that can be checked by the compiler) would be great. I hate those loose strings we all have to use.

    I’d love to see the syntax of the event metadata changed as well whilst i think about it. IMO it should be…

    [Event(type=MyEvtClass.SOME_EVENT, class=MyEvtClass)]

    … means in AS we refer to that first prop as the type, the current metadata is somewhat confusing.
12. Josh Tynjala 05.11.08 / 4pm

    I second Tink’s and Ben’s requests. Completion for var/function and the ability to reference classes and constants in metadata would both be quite excellent.
13. Jensa 05.12.08 / 12pm

    David? FB-11950 that Dan pointed out is also my biggest annoyance. I have a suspicion that this one runs deep though. Whatever it is causing this issue, this is just one of the side-effects, so fixing this would close a lot of open bugs.

    J
14. david.z 05.12.08 / 12pm

    Jensa and Dan…can you guys give me more to go on than “sometimes it doesn’t work”? I need a solid, reproducible case or the actual projects that you’re dealing with. Feel free to e-mail me at dzuckerm at adobe dot com and we can figure this out off list
15. david.z 05.12.08 / 12pm

    Ben and Tink: I would love to see Flex change so that constants can be used in event declarations. There’s always a discussion about it internally, and i’ll make sure to add your feedback to that discussion

Powered by Hemingway flavored Wordpress.

Entries RSS Comments RSS