@Martin I was following your advice and added a table for listing of the app code examples [1].
Regarding a dictionary for "Nanoarchitectures / Architectural Patterns" ... for "Design Patterns" a commonly excepted dictionary already exists [2]. Creating a dictionary for "Architectural Patterns" [3] like: - "Model-View-Controller" (MVC) - "Model-View-Presenter" (MVP) - "Presentation Model" (PM) - "Domain-Driven Design" (DDD) [4] - ... etc. would be great, but, I have doubt that there will be a commonly excepted dictionary as well. Never the less, working on a dictionary for "Nanoarchitectures / Architectural Patterns" would be great, because, when using the words out of this dictionary, it would improve the communication inside a developer team, and it would reduce the time and cost when working in a Flex project. -- Sebastian [1] https://cwiki.apache.org/confluence/display/FLEX/App+Examples [2] http://en.wikipedia.org/wiki/Software_design_pattern#Classification_and_list [3] http://en.wikipedia.org/wiki/Architectural_pattern [4] http://en.wikipedia.org/wiki/Domain-driven_design On Sun, Feb 12, 2012 at 8:22 AM, Martin Heidegger <[email protected]>wrote: > On 12/02/2012 16:03, Sebastian Mohr wrote: > >> from what I have seen in the industry there could be many different >> "Application Coding Standards" around, and, all of them have there own >> "Nanoarchitectures / Architectural Patterns" and "Coding Conventions". >> > > The idea of patterns is basically an idea of a dictionary. Words that we > can use in daily > conversation. A dictionary that is spread over various locations is not > really effective imho. > > ... Hosting ... would be quite a challenge >> > Why? Wikis are perfect for that. > > > ... not sure how long Google Code will last for. >> > > Google code is not a problem i guess. http://one-persons.com/blog might > be. And the later one > is a URL much alike. > > yours > Martin. > >
