RE: [flexcoders] Please Adobe. Unanswered questions, and building the community
Thanks for responding, My initial worry was not that all my questions are not getting answered. It was more like if Adobe wants to get into the dev realm and be active in convincing existing MS dev people to make a switch to Flex from the upcoming WPF/e and WPF platforms, their community support and involvement needs to be greater then that of MS on a per dev basis. The product is only 20% of the work effort to see a real success, the other 80% is execution, and actions required to get a user base that makes future development worth while. Convincing developers to change platforms will be much harder then convincing designers. MS has to convince the designers, and Adobe need to convince the developers. Adobes task is much greater. Im afraid that the post came off as someone whining cause his questions dont get answered which was not at all the intent. I frequent the MS channle9 and MS forums often as I use their products, there is no talk about Flex/Apollo only WPF/Ajax/WPFE. Im an avid tech blog reader, tech magazine reader, all around anything tech, and see no mention or little thereof of Flex. I heard the first time of Flex 1.5 last June? How long has it been out? Im a dev thats always looking for new technology to solve problems, so how is this possible. This worries me too the core about the future of Flex. Its a viable platform, and very powerful, however Macromedia has/had a reputation in the Dev world (animations etc..) Adobe has a rep in the Dev world (its just for designers). So how can Adobe hope to unclench the Dev world that MS fights so much to protect? It takes much more then a superior product to make it happen. MS is a PR machine. Unless Adobe gets very involved (very being an understatement) how does Adobe hope to accomplish this? The only way is better execution combined with superior involvement/support, and then hope that the word of mouth becomes viral. To become viral you need the story which Flex has, and the people to spread that. The story of Flex is not getting out there enough. I believe that Flex has the potential to stop MS WPF/e in its tracks, but the buck starts here, not in 6 months, and not in 2. Anyway enough rambling, Ill just continue to do my part where I can to ensure my investment pays off. Again my apologies if it came off the wrong way. Jason -Message d'origine-De : flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED]De la part de Gordon SmithEnvoyé : vendredi 23 juin 2006 08:10À : flexcoders@yahoogroups.comObjet : RE: [flexcoders] Please Adobe. Unanswered questions, and building the community My understanding is that Adobe support engineers don't generally start supporting products until they are released (and therefore the product is stable). It's up to the development team to support alpha, beta, and GMC releases and we do that to the best of our abilities as we have spare time. We're currently helping to train the Flex support engineers to take over this work since we are about to release.Also, some of us are paying a bit more attention to the "official" adobe.com forums and a bit less to flexcoders, but we try to monitor multiple places if possible.Finally, we're also missing Matt Chotins's contribution... he got promoted to Product Manager.- Gordon-Original Message-From: [EMAIL PROTECTED]ups.com [mailto:[EMAIL PROTECTED]ups.com] On Behalf Of Jason HawrylukSent: Thursday, June 22, 2006 7:58 AMTo: [EMAIL PROTECTED]ups.comSubject: RE: [flexcoders] Please Adobe. Unanswered questions, and building the communityIf they would confirm it's a bug then yes I agree, If they read them all howhard is it to respond with a simple it's a bug, should be able to do that,try looking into here or this. The questions asked are not consideredtrivial in my mind, it's not like I've ever asked how to build a cellrenderer or anything (not that that's bad). It's rare I do not have the helpup at the same time as flex, I refer to it very often.I feel the post has been taken in a critical sense. I want to see Flexsucceed as much as the next person, however to think that a strong communitycan be built without considerable contributions from the maker, is kind ofhard to imagine. Where would Java be today if Sun did spend a considerableeffort, and expense in its community building?"A couple of questions answered here, and there will not do it. " May havebeen out of line :)Anyway thanks for the input.Jason-Message d'origine-De : [EMAIL PROTECTED]ups.com [mailto:[EMAIL PROTECTED]ups.com]De lapart de Tom ChivertonEnvoyé : jeudi 22 juin 2006 10:56À : [EMAIL PROTECTED]ups.comObjet : Re: [flexcoders] Please Adobe. Unanswered questions, andbuilding the communityOn Thursday 22 June 2006 09:16, sourcecoder
RE: [flexcoders] Please Adobe. Unanswered questions, and building the community
Judah: I only found one Flex book(Nov. 2006) and the three AS3 book(Aug. 2006, Sept. 2006, & Oct. 2006) What are the other Flex 2 book's and which one is coming out next week? Thanks, Jack From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of judahSent: Thursday, June 22, 2006 3:24 PMTo: flexcoders@yahoogroups.comSubject: Re: [flexcoders] Please Adobe. Unanswered questions, and building the community I'd give it a bit more time. Having a beta schedule makes it difficult with the full release coming up. On the betas I've been on the support and questiong answering has always been spotty. This is because the state the program is in. Bugs need to be queued, tested and then confirmed before an answer can be given. Features are still floating around. Once they get out of beta I think things will settle down.Personally, I think they are doing a great job, but I know you've had questions unanswered. The solution may be to wait and see until after Flex 2 is released, reword the question over and over breaking it down, or on the Adobe side have additional community TSR's (technical support reps) on this list (which if they do add more I hope they'll announce it). I've been to Barnes & Nobles every week checking and I know of at least 3 new Flex 2 books coming out and two ActionScript 3 books in the next few months. One is coming out next week. These will hopefully answer a lot of questions.Best Regards,Judahsourcecoderia wrote:> IMHO a community is not at all built this way, any answer is better > then no answer. For developers we ask a question if it goes without > response we think either they are ignoring the question, can't be > bothered, or it's a bug. Since the first thought is that they can't > be bothered we continue to try and find a solution to the problem, > until completely frustrated. >> Theses things are very important (to me at least) when choosing to > switch from a dot net development environment to something such as > flex. I've been working with flex for a year now, and of course I'm > very happy with it, however I feel that the community involvement > from adobe is rather lacking. >> You can't hope to build a solid community that supports it self, we > are not the experts, you are. We need your help, and you need our > help. But; the communication, and participation in the building of > the community has to work both way's. I've answered far more > questions then I have had answered, I participated in the alpha > testing, I've reported bug's in this forum. All this I'm very willing > to do, and continue doing. However your community support people > could at least take the time and read the question, and either > confirm it as a bug, not possible, or give an idea of where to look. >> I'm not unhappy with Flex, I'm rather impressed and energized. > Learning a new language, and platform is difficult, and time > consuming. >> Why are there no tutorials except the few you have done to get people > up to speed, where is all the learn by example stuff, tips, general > community building. Surly you can invest in some full time community > support personnel.>> Flex is moving Adobe into a developer realm, as apposed to the > designer realm. I think if you hope to convince the developer realm > (a more demanding task) community involvement from Abode needs to be > greatly increased. A couple blog entries a week will not do it. A > couple of questions answered here, and there will not do it. We need > to see that your behind us, that you want to help us succeed with > your product, that you continue to listen, and that you're doing > everything humanly possible to help get us up to speed. >> Flex has the potential to be more then just some other platform. In > order to go head to head with MS, and unlock the dedicated developer > community they've built, you need to greatly increase your community > involvement.>> Hopefully in posting this I've not managed to get on the spam/ignore > list of all Adobe support :)>>> Here are some example things with no response, I'm sure if asked, > every person in this forum could repost at least 1 or 2 unanswered > questions. Any answer is better then none.>> Garbage collection and removeChild [Flex 2 beta 3]?>> http://groups.yahoo.com/group/flexcoders/message/40262>>> E4X Interpreter:>> http://groups.yahoo.com/group/flexcoders/message/40342?> threaded=1&var=1&p=1>> I can't get a xml chain to bind here.>> [Bindable]> public var boundtarget:XML = new XML> (Jason);> private var owatch:ChangeWatcher;> > private fu
RE: [flexcoders] Please Adobe. Unanswered questions, and building the community
My understanding is that Adobe support engineers don't generally start supporting products until they are released (and therefore the product is stable). It's up to the development team to support alpha, beta, and GMC releases and we do that to the best of our abilities as we have spare time. We're currently helping to train the Flex support engineers to take over this work since we are about to release. Also, some of us are paying a bit more attention to the "official" adobe.com forums and a bit less to flexcoders, but we try to monitor multiple places if possible. Finally, we're also missing Matt Chotins's contribution... he got promoted to Product Manager. - Gordon -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jason Hawryluk Sent: Thursday, June 22, 2006 7:58 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Please Adobe. Unanswered questions, and building the community If they would confirm it's a bug then yes I agree, If they read them all how hard is it to respond with a simple it's a bug, should be able to do that, try looking into here or this. The questions asked are not considered trivial in my mind, it's not like I've ever asked how to build a cell renderer or anything (not that that's bad). It's rare I do not have the help up at the same time as flex, I refer to it very often. I feel the post has been taken in a critical sense. I want to see Flex succeed as much as the next person, however to think that a strong community can be built without considerable contributions from the maker, is kind of hard to imagine. Where would Java be today if Sun did spend a considerable effort, and expense in its community building? "A couple of questions answered here, and there will not do it. " May have been out of line :) Anyway thanks for the input. Jason -Message d'origine- De : flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] la part de Tom Chiverton Envoyé : jeudi 22 juin 2006 10:56 À : flexcoders@yahoogroups.com Objet : Re: [flexcoders] Please Adobe. Unanswered questions, and building the community On Thursday 22 June 2006 09:16, sourcecoderia wrote: > bothered, or it's a bug. Since the first thought is that they can't > be bothered we continue to try and find a solution to the problem, > until completely frustrated. There is an official (read $$$) support channel, and there are unofficial support channels (like here). Here is provided by community members and a few people from Adobe, basically (as I see it) on a best effort basis. This is not the place to report bugs (though it's useful to report them here too for everyone to see). > questions then I have had answered, I participated in the alpha > testing, I've reported bug's in this forum. All this I'm very willing > to do, and continue doing. However your community support people > could at least take the time and read the question, and either > confirm it as a bug, not possible, or give an idea of where to look. I agree with you right up to the last bit - Adobe should not have to respond to every single post. Just rest assured they really do read them all. > Why are there no tutorials except the few you have done to get people > up to speed, where is all the learn by example stuff, tips, general > community building. Surly you can invest in some full time community > support personnel. I'm sure there will be a ton of this e.g. DevNet articles, later this month. Assuming Adobe really are planning the Flex2 release announcement for CFUNITED. > A > couple of questions answered here, and there will not do it. I think thats rather on the low side :-) > questions. Any answer is better then none. I've said before that I try and go back over no-child posts older than a few days and say at least *something*, but sometimes it's over my head, doesn't have a simple cut'n'paste test case, or just a case of needing to read the manual (hell, it's got a search button !) in which case I've got tired of saying the latter :-) Overall, Adobe are certainly going in the same good, open, direction MM were - and I'm, sure there is more to come. -- Tom Chiverton This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confide
Re: [flexcoders] Please Adobe. Unanswered questions, and building the community
I'd give it a bit more time. Having a beta schedule makes it difficult
with the full release coming up. On the betas I've been on the support
and questiong answering has always been spotty. This is because the
state the program is in. Bugs need to be queued, tested and then
confirmed before an answer can be given. Features are still floating
around. Once they get out of beta I think things will settle down.
Personally, I think they are doing a great job, but I know you've had
questions unanswered. The solution may be to wait and see until after
Flex 2 is released, reword the question over and over breaking it down,
or on the Adobe side have additional community TSR's (technical support
reps) on this list (which if they do add more I hope they'll announce
it). I've been to Barnes & Nobles every week checking and I know of at
least 3 new Flex 2 books coming out and two ActionScript 3 books in the
next few months. One is coming out next week. These will hopefully
answer a lot of questions.
Best Regards,
Judah
sourcecoderia wrote:
> IMHO a community is not at all built this way, any answer is better
> then no answer. For developers we ask a question if it goes without
> response we think either they are ignoring the question, can't be
> bothered, or it's a bug. Since the first thought is that they can't
> be bothered we continue to try and find a solution to the problem,
> until completely frustrated.
>
> Theses things are very important (to me at least) when choosing to
> switch from a dot net development environment to something such as
> flex. I've been working with flex for a year now, and of course I'm
> very happy with it, however I feel that the community involvement
> from adobe is rather lacking.
>
> You can't hope to build a solid community that supports it self, we
> are not the experts, you are. We need your help, and you need our
> help. But; the communication, and participation in the building of
> the community has to work both way's. I've answered far more
> questions then I have had answered, I participated in the alpha
> testing, I've reported bug's in this forum. All this I'm very willing
> to do, and continue doing. However your community support people
> could at least take the time and read the question, and either
> confirm it as a bug, not possible, or give an idea of where to look.
>
> I'm not unhappy with Flex, I'm rather impressed and energized.
> Learning a new language, and platform is difficult, and time
> consuming.
>
> Why are there no tutorials except the few you have done to get people
> up to speed, where is all the learn by example stuff, tips, general
> community building. Surly you can invest in some full time community
> support personnel.
>
> Flex is moving Adobe into a developer realm, as apposed to the
> designer realm. I think if you hope to convince the developer realm
> (a more demanding task) community involvement from Abode needs to be
> greatly increased. A couple blog entries a week will not do it. A
> couple of questions answered here, and there will not do it. We need
> to see that your behind us, that you want to help us succeed with
> your product, that you continue to listen, and that you're doing
> everything humanly possible to help get us up to speed.
>
> Flex has the potential to be more then just some other platform. In
> order to go head to head with MS, and unlock the dedicated developer
> community they've built, you need to greatly increase your community
> involvement.
>
> Hopefully in posting this I've not managed to get on the spam/ignore
> list of all Adobe support :)
>
>
> Here are some example things with no response, I'm sure if asked,
> every person in this forum could repost at least 1 or 2 unanswered
> questions. Any answer is better then none.
>
> Garbage collection and removeChild [Flex 2 beta 3]?
>
> http://groups.yahoo.com/group/flexcoders/message/40262
>
>
> E4X Interpreter:
>
> http://groups.yahoo.com/group/flexcoders/message/40342?
> threaded=1&var=1&p=1
>
> I can't get a xml chain to bind here.
>
> [Bindable]
> public var boundtarget:XML = new XML
> (Jason);
> private var owatch:ChangeWatcher;
>
> private function Init_TargetBinding():void{
> //build the array for the property chain
> owatch = BindingUtils.bindProperty(text1, "text",this,
> [ "boundtarget","namex"]);
> trace(owatch.isWatching());
> }
>
>
>
> as well as being able to do the below
>
> BindingUtils.bindProperty( txtField, "text", this,
> ["xdata","item","(@id=='3456')","description"] );
>
>
>
> Bug confirmation please ? Felx 2.0 b3
>
> http://groups.yahoo.com/group/flexcoders/message/39228
>
> FileReference upload bytes FB2
>
> http://groups.yahoo.com/group/flexcoders/message/35364
>
>
> Still problems with Tree, and drag and drop Flex 2.0 b3
>
> http://groups.yahoo.com/group/flexcoders/message/37927
>
> Cursor questions Flex 2.0 B3
>
> http://groups.yahoo.com/group/flexcoders/
RE: [flexcoders] Please Adobe. Unanswered questions, and building the community
If they would confirm it's a bug then yes I agree, If they read them all how hard is it to respond with a simple it's a bug, should be able to do that, try looking into here or this. The questions asked are not considered trivial in my mind, it's not like I've ever asked how to build a cell renderer or anything (not that that's bad). It's rare I do not have the help up at the same time as flex, I refer to it very often. I feel the post has been taken in a critical sense. I want to see Flex succeed as much as the next person, however to think that a strong community can be built without considerable contributions from the maker, is kind of hard to imagine. Where would Java be today if Sun did spend a considerable effort, and expense in its community building? "A couple of questions answered here, and there will not do it. " May have been out of line :) Anyway thanks for the input. Jason -Message d'origine- De : flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] la part de Tom Chiverton Envoyé : jeudi 22 juin 2006 10:56 À : flexcoders@yahoogroups.com Objet : Re: [flexcoders] Please Adobe. Unanswered questions, and building the community On Thursday 22 June 2006 09:16, sourcecoderia wrote: > bothered, or it's a bug. Since the first thought is that they can't > be bothered we continue to try and find a solution to the problem, > until completely frustrated. There is an official (read $$$) support channel, and there are unofficial support channels (like here). Here is provided by community members and a few people from Adobe, basically (as I see it) on a best effort basis. This is not the place to report bugs (though it's useful to report them here too for everyone to see). > questions then I have had answered, I participated in the alpha > testing, I've reported bug's in this forum. All this I'm very willing > to do, and continue doing. However your community support people > could at least take the time and read the question, and either > confirm it as a bug, not possible, or give an idea of where to look. I agree with you right up to the last bit - Adobe should not have to respond to every single post. Just rest assured they really do read them all. > Why are there no tutorials except the few you have done to get people > up to speed, where is all the learn by example stuff, tips, general > community building. Surly you can invest in some full time community > support personnel. I'm sure there will be a ton of this e.g. DevNet articles, later this month. Assuming Adobe really are planning the Flex2 release announcement for CFUNITED. > A > couple of questions answered here, and there will not do it. I think thats rather on the low side :-) > questions. Any answer is better then none. I've said before that I try and go back over no-child posts older than a few days and say at least *something*, but sometimes it's over my head, doesn't have a simple cut'n'paste test case, or just a case of needing to read the manual (hell, it's got a search button !) in which case I've got tired of saying the latter :-) Overall, Adobe are certainly going in the same good, open, direction MM were - and I'm, sure there is more to come. -- Tom Chiverton This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. For more information about Halliwells LLP visit www.halliwells.com. We are pleased to announce that Halliwells LLP has been voted AIM Lawyer of the Year at the 2005 Growth Company Awards -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links Yahoo! Groups Sponsor ~--> Great things are happening at Yahoo! Groups. See the new email design. http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/nhFolB/TM --
Re: [flexcoders] Please Adobe. Unanswered questions, and building the community
On Thursday 22 June 2006 09:16, sourcecoderia wrote: > bothered, or it's a bug. Since the first thought is that they can't > be bothered we continue to try and find a solution to the problem, > until completely frustrated. There is an official (read $$$) support channel, and there are unofficial support channels (like here). Here is provided by community members and a few people from Adobe, basically (as I see it) on a best effort basis. This is not the place to report bugs (though it's useful to report them here too for everyone to see). > questions then I have had answered, I participated in the alpha > testing, I've reported bug's in this forum. All this I'm very willing > to do, and continue doing. However your community support people > could at least take the time and read the question, and either > confirm it as a bug, not possible, or give an idea of where to look. I agree with you right up to the last bit - Adobe should not have to respond to every single post. Just rest assured they really do read them all. > Why are there no tutorials except the few you have done to get people > up to speed, where is all the learn by example stuff, tips, general > community building. Surly you can invest in some full time community > support personnel. I'm sure there will be a ton of this e.g. DevNet articles, later this month. Assuming Adobe really are planning the Flex2 release announcement for CFUNITED. > A > couple of questions answered here, and there will not do it. I think thats rather on the low side :-) > questions. Any answer is better then none. I've said before that I try and go back over no-child posts older than a few days and say at least *something*, but sometimes it's over my head, doesn't have a simple cut'n'paste test case, or just a case of needing to read the manual (hell, it's got a search button !) in which case I've got tired of saying the latter :-) Overall, Adobe are certainly going in the same good, open, direction MM were - and I'm, sure there is more to come. -- Tom Chiverton This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. For more information about Halliwells LLP visit www.halliwells.com. We are pleased to announce that Halliwells LLP has been voted AIM Lawyer of the Year at the 2005 Growth Company Awards Yahoo! Groups Sponsor ~--> Yahoo! Groups gets a make over. See the new email design. http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/nhFolB/TM ~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
Re: [flexcoders] Please Adobe. Unanswered questions, and building the community
Hello Sourcecodia,
Just my own 0.02 here:
The way i see a community is that it is a
community. I mean that Adobe has not the entire responsability of answering one
and every question posted in this forum.
Myself, i had a few questions which have never been
answered, well, then what ? I ask again, i reformulate... But in no ways i'm
gonna complain about Adobe.
If you need help, or have questions which need to
be adressed in a professional and timely way, go buy a Gold Support at Adobe,
and i assure you that you'll get what you want. And it will be worth your
money.
I'm trying myself to build the french community
around Flex, and i'm working on an everyday basis with Adobe France, i can
assure you that their implication in developping the community is
total.
Keep in mind that Flex is due out next week, they
have a planning to respect, a lot of work to do, abunch of things to finish for
the launch date, i'm sure that you'll be impressed by Adobe's commitment to
the community after Flex is released.
Let's take Cairngorm for instance. Steven always
claimed that they are doing all they can to get Cairngorm and all the docs ready
for Flex release. And they will.
We all appreciate (as developpers) your commitment
to the beta's and your postings to this list. But please give us and Adobe the
time for building this community. It's all new for them. They have been in
the community thing for only a few months.
I am not affiliated with Adobe in any ways, i am
just throwing in my two cents as an enthousiastic french
developper.
Best,
Jean-Luc.
- Original Message -
From:
sourcecoderia
To: flexcoders@yahoogroups.com
Sent: Thursday, June 22, 2006 10:16
AM
Subject: [flexcoders] Please Adobe.
Unanswered questions, and building the community
IMHO a community is not at all built this way, any answer is better
then no answer. For developers we ask a question if it goes without
response we think either they are ignoring the question, can't be
bothered, or it's a bug. Since the first thought is that they can't be
bothered we continue to try and find a solution to the problem, until
completely frustrated. Theses things are very important (to me at
least) when choosing to switch from a dot net development environment to
something such as flex. I've been working with flex for a year now, and of
course I'm very happy with it, however I feel that the community
involvement from adobe is rather lacking. You can't hope to build
a solid community that supports it self, we are not the experts, you are.
We need your help, and you need our help. But; the communication, and
participation in the building of the community has to work both way's.
I've answered far more questions then I have had answered, I participated
in the alpha testing, I've reported bug's in this forum. All this I'm very
willing to do, and continue doing. However your community support people
could at least take the time and read the question, and either confirm
it as a bug, not possible, or give an idea of where to look. I'm not
unhappy with Flex, I'm rather impressed and energized. Learning a new
language, and platform is difficult, and time consuming. Why are
there no tutorials except the few you have done to get people up to speed,
where is all the learn by example stuff, tips, general community building.
Surly you can invest in some full time community support
personnel.Flex is moving Adobe into a developer realm, as apposed to
the designer realm. I think if you hope to convince the developer realm
(a more demanding task) community involvement from Abode needs to be
greatly increased. A couple blog entries a week will not do it. A
couple of questions answered here, and there will not do it. We need
to see that your behind us, that you want to help us succeed with your
product, that you continue to listen, and that you're doing everything
humanly possible to help get us up to speed. Flex has the potential to
be more then just some other platform. In order to go head to head with
MS, and unlock the dedicated developer community they've built, you need
to greatly increase your community involvement.Hopefully in
posting this I've not managed to get on the spam/ignore list of all Adobe
support :)Here are some example things with no response, I'm sure if
asked, every person in this forum could repost at least 1 or 2 unanswered
questions. Any answer is better then none.Garbage collection and
removeChild [Flex 2 beta 3]?http://groups.yahoo.com/group/flexcoders/message/40262E4X
Interpreter:http://groups.yahoo.com/group/flexcoders/message/40342?threaded=1&var=1&p=1I
can't get a xml chain to bind here.[Bindable]public var
boundtarget:XML = new
XML(Jason);private
var owatch:ChangeWatcher;private function
Init_TargetBinding():void{//build the array for the property
c
