incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Harfleet <dharfl...@yahoo.com>
Subject Re: Website - Flex Ecosystem Products
Date Mon, 09 Apr 2012 13:07:04 GMT
Hi Keith,

thanks for this; I have noticed a few that have not been included:


Saucelabs
http://saucelabs.com/docs/flex-getting-started

Hamcrest AS3
https://github.com/drewbourne/hamcrest-as3/wiki

ASMock
http://asmock.sourceforge.net/wiki/Main_Page


 
Daniel Harfleet
____________________________________
http://www.linkedin.com/in/dharfleet



________________________________
 From: Keith Sutton <keith@spoon.as>
To: flex-dev@incubator.apache.org 
Sent: Wednesday, 4 April 2012, 17:43
Subject: Re: Website - Flex Ecosystem Products
 
In the spirit of 'just do it' here is a pretty comprehensive list of Flex ecosystem partners
and their products/services: http://www.spoon.as/flex-ecosystem-products/

This was not a trivial tasks because digging for and connecting with the Product Managers
of these organizations and getting descriptions/links/icons ironed out took time. Clearly
some design finesse is needed.

I was envisioning summarizing this list on an Apache Flex page similar to http://wiki.apache.org/hadoop/HadoopUserGroups

Happy to work on this page on Apache Flex wiki while the discussion on a web site goes on.
At least the data will be there.

Any disagreements?



On 4/4/2012 5:49 AM, Ivan Ilijašić wrote:
> On Wed, Apr 4, 2012 at 2:46 PM, Martin Heidegger<mh@leichtgewicht.at>wrote:
> 
>> Imho the order is not right. The structure of a page is crutial for
>> starting the design process. So how about collecting things that need to be
>> shown on the Flex homepage, here is what I can think of:
>> 
>>   - Download the SDK
>>   - Documentation to the SDK (big topic)
>>   - Team (&how to join)
>>   - Examples
>>   - Twitter/Google+/Mailinglist/**etc. (socializing)
>>   - Source access (svn/github mirror/etc.)
>>   - License
>>   - FAQ
>>   - Coding Standards
>> 
> I agree with Martin. Also I would suggest adding showcase subpage.
> 
> Cheers,
> Ivan
> 
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message