Re: [flexcoders] Flex2 :: 3rd party Components :: Adobe comments

[Michael Schmalle]

Jesse,

In a nutshell that is all I meant. No disrespect to Adobe or
Macormedia. Developers need tools just like the tools they are giving
all their clients.

As a component developer, you must swallow the fact that your client is
going to make big bucks off your measly 200$ a license to them.

Once, you get past that, yes most component developers are inventors at
the core. So, these 'docs' would only speed up our Flex implementation
into the WORLD.

Since competition is technology these days, Adobe has already done
awsome to even do public betas(I know this the trend but still..)

"I've spent 3 years learning the MX 2004 / 8 v2 
component framework, and it makes sense to me... most of it.  I never cared 
for the DataSet and binding classes, but everything else has allowed me to 
create applications I couldn't have without knowlege of using them and the rest 
of the framework."

I have created components with v2 also, plus a container framework(that
never got used becasue it was to much for me). So, yes the v2 has it's
strengths and if you have heard from me the last 3 years I spent
learning Flash and it's component framework, you know where I am
comming from.


Peace, MikeOn 5/1/06, JesterXL <[EMAIL PROTECTED]> wrote:









I've spent 3 years learning the MX 2004 / 8 v2 
component framework, and it makes sense to me... most of it.  I never cared 
for the DataSet and binding classes, but everything else has allowed me to 
create applications I couldn't have without knowlege of using them and the rest 
of the framework.
 
Macromedia made a strong effort to listen to the 
community's feedback upon it's release, and eventually documented it.  Too 
little too late for some of us, but at least they did what they said they were 
going to do.  Upon the release of Flex 1, they had apparently learned from 
that mistake because the Flex 1 documentation for components was top notch 
compared to Ellipsis (Flash 7.2).  This put up or shutup attitude was nice 
to see; for everyone who asked a question that was directly answerable from the 
docs, people on the Flexcoders list pointed them to RTFM manual, and it 
was good to see they had faith in what they produced.  Upon reading 
the documentation for Beta 2, and seeing Sho's blog post on the revamp for Beta 
3, I think Adobe is continuing that quality in documentation.
 
Granted, documenting the API for a List component 
and documenting not only how to USE that List component, but USING that List 
component with OTHERS are 3 totally different things.  I think we are 
getting the latter after reading pages about utilizing item renderers, and 
UIComponent API changes.  Granted, you can't judge it yet since it's not 
done, nor is the source code publicly released in this build to compare and 
contrast.
 
While I personally think it's up to the developer 
to invest their own personal time to learn the framework on their own, I would 
still prefer docs written that help get us up to speed as soon as possible to 
provide a better cost to time invested ratio, ecspecially since the scope of 
this component framework is much larger than v1 & v2 combined.
 
----- Original Message ----- 
From: 
Michael 
Schmalle 
To: flexcoders@yahoogroups.com 
Sent: Monday, May 01, 2006 10:20 AM
Subject: [flexcoders] Flex2 :: 3rd party Components :: Adobe 
comments
Hi,Adobe says they want a rich 3rd party componenty 
community. I have one question;Is Adobe going to give developers 
a road map of their framework ? Macromedia severly failed when trying to 
proliferate those quasi components named v2. Us developers spent 6 months 
figuring the rats nest out(in the end it didn't make any sense 
anyway).Do we Flex2 component devs get a road map(whitepapers) of the 
framework or do we have to waste 6 months learning code alogrithms when the 
source for the flex2 framework comes out?Peace, MikePS This 
comment stems from the fact Manish just pointed out the dropdownFactory of the 
ComboBox. Which is modular development at its best!  I mean, looking at the 
10,000 pages of api docs I do see it listed but common! You have to have 
something that your internal devs use. (this could have saved me hours)-- What goes up, does come down. 





--
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



   Visit your group "flexcoders" on the web. 
   To unsubscribe from this group, send an email to: 
[EMAIL PROTECTED] 
   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.




  








-- What goes up, does come down.






--
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



   Visit your group "flexcoders" on the web. 
   To unsubscribe from this group, send an email to: [EMAIL PROTECTED] 
   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.