Due to our last discussion about code examples, I would like 
to discuss the procedure we should follow when writing these 
code examples. 

I also would like to point out that there is a difference between 
writing Component Code Examples which should illustrate the 
functionality of a component (Spark-DropDownList or MX-
ColorPicker), and, Application Code Examples which should 
illustrate how to build (large-scale) Flex applications.

I am personally more interested on writing Application Code Examples
with or without the use of Microarchitectures, because I think the community 
and Adobe already created lots of Component Code Examples:

Flex 3, http://livedocs.adobe.com/flex/3/html/index.html
Flex 4.6, http://help.adobe.com/en_US/flex/using/index.html

...

Proposal: Code Example / Application Development Procedure

This is the proposal for writing (large-scale) Application Code Examples:

'Before working on your Application Code make sure you have specified the 
requirements of the application in a Specification Document, and, you have 
defined an Application Coding Standard. An "Application Coding Standard" 
consists of a set of Nanoarchitectures / Architectural Patterns which describe 
the structure of your application, and, some coding guidelines collected in a 
Coding Conventions document.'

For more information please check out the diagram on this site:

http://code.google.com/p/masuland/wiki/ApplicationDevelopmentProcedure

I would be happy to find some kind of consensus on this topic here in Apache 
Flex.


-- Sebastian



On Jan 16, 2012, at 8:37 AM, Peter Elst wrote:

>> And thus, we should probably not use application frameworks in our examples
>> on the project website.  The application framework vendors should have
>> their
>> own examples on their website.
> 
> 
> Maybe we could have a wiki with references to those application framework
> vendor examples, and other Apache Flex specific articles, tutorials, sample
> code.
> 
> I'd be happy to work on that if it there is no objection to that getting
> set up.
> 
> - Peter

Reply via email to