RE: [flexcomponents] 3rd Party Component Explorer

Thu, 07 Sep 2006 11:10:42 -0700

Ok,

 

So maybe we allow for some extensibility here:

 

I see a couple of requirements forming:

 

  1. Support Classic Explorer features via URLs plus Descriptions.
  2. Support Image Previews and Descriptions for complex UI/Workflow type components.

 

I realize that we cannot fit everyone in the same app but if we leave room using Image previews and text, this will be good enough.

 

  1. Tree on the left
    1. Tree contains paths per company/developer of components.

                                                               i.      Components > Farata Systems > UI Components > SuperGrid

                                                             ii.      Components > Farata Systems > FDS > Generator

  1. Panel on Right
    1. Classic Explorer PREVIEW / MXML in Tabs with new INFO Tab
    2. Preview Images in Tabs with new INFO Tab

 

Thoughts?

 

Ted Patrick

Flex Evangelist

Adobe Systems Incorporated

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of Anatole Tartakovsky
Sent: Thursday, September 07, 2006 9:49 AM
To: [email protected]
Subject: Re: [flexcomponents] 3rd Party Component Explorer

 

Ted, everyone

    I had some problems posting to exchange in the past for the following reason - it is geared toward components that, while important, are a fraction ( major, but not really crucial for commercial decision makers) of 3rd party marketplace. In some cases it prevented me from posts. Examples of the components we build that have obvious problems:

 

1. Code generators - back end and some "helper" components on the client side - specialized collections hardly make good UI sample

2. Heavy Components - SuperGrid, PropertyBag,, etc  - can be demoed, but require dedicated pages with help, demos, white papers, etc.

3. Tools - Ant build automation, Debugging/tracing pannels - are not components, but rather something we (and I am afraid most of Java folks) can not build code without.

4. Vertical solutions based on the combination of the parts/framework/crossmarketing of the components

 

We are moving some of the components to the SourceForge as they have established solution for the above issues.

 

I understand that there should be structure, I believe we can benefit if we build in some "unstructured" blog/community part in it to resolve the forementioned

 

Sincerely,

Anatole Tartakovsky

 

 

----- Original Message -----

From: Ted Patrick

Sent: Thursday, September 07, 2006 12:02 PM

Subject: [flexcomponents] 3rd Party Component Explorer

 

After you get your component added to the Flex Exchange at http://www.adobe.com/exchange/ ...

 

I have been thinking about putting together a 3rd Party Component Explorer and XML document containing all 3rd party components for Flex. The application would contain working examples and allow developers looking for component to try them out.

 

I am looking at the workflow for this so that it is easy to maintain and automated:

 

  1. Post a Form on Flex.org
    1. Author/Company
    2. Contact Information (URL/Email)
    3. URL to crossdomain.xml
    4. URL to SWF Example
    5. URL to MXML Example Source
  1. Approval Process
  2. Posted

 

This would all be wrapped into an app identical to the current component explorer.

 

Thoughts?

 

Ted Patrick

Flex Evangelist

Adobe Systems Incorporated

 

 

 

__._,_.___


SPONSORED LINKS
Software development tool Application development software Development software
Development outsourcing software Embedded software development

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___

Reply via email to