--- In [email protected], "Clinton D. Judy" <[EMAIL PROTECTED]> wrote: > > Hahahahaha! > > Now that that's out my system, yes, I tend to have similar > experiences with you in this group.
LOL! > I think there's just a HUGE number of people here who are > novices and don't know very much about Flex that ask questions, > and very few "experts" that can answer 90% or more of > people's questions. I'm not *exactly* sure what my Flex programming expertise is at the moment. I've developed quite a number of apps, but it seems like often my approach to developing an app changes from the one before... so at times, it seems like I'm starting over. ;-) Ironically, though, I've learned a good portion of what I know by reading people's posts about issues they're having, using those posts to try to recreate the issue, and "tinkering" (30% Googling, and 70% just out-and-out trying things in code) to try to get the issue to go away. > But so many problems are the same and can be solved by doing > a simple search for the solution. Meh. A search in this group is usually my first point of attack. Then a broader Google search on the web. But I've found trying to search for issues with the keyword "flex" to be very frustrating. It's such a generic term. If I'm having an issue with a specific component, I'll Google for "mx:componentName" (with the quotes) and hopefully something about the type of issue... but other than that, more general questions are *very* hard to research using searches. Sure would've been nice if Macromedia named their product with a less-generic, more-searchable name.
