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 -----
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/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
(<item><namex>Jason</namex></item>);
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());
}

<mx:TextInput id="text1" width="100%"/>

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/message/38461

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to