EMMAWiki/TermsAndConcepts/ForDevelopers: Difference between revisions

From BRF-Software
Jump to navigation Jump to search
No edit summary
 
imported>MichaelDondrup
No edit summary
Line 3: Line 3:


== Synopsis ==
== Synopsis ==
This chapter is intended as an introductory overview for people intending to start programming with !EMMA. Although there is a lot of documentation around e.g for the API, it is often hard to find out how the system really ''works''. Knowing that it might be easier to figure out which part of the documentation one has to read and which part of the system is in need of a major improvement (or even a complete re-design). By presenting the architecture in a graphical way we try to make clear the interactions between the components.
This chapter is intended as an introductory overview for people intending to start programming with EMMA. Although there is a lot of documentation around e.g for the API, it is often hard to find out how the system really ''works''. Knowing that it might be easier to figure out which part of the documentation one has to read and which part of the system is in need of a major improvement (or even a complete re-design). By presenting the architecture in a graphical way we try to make clear the interactions between the components.
If you are just curious but never intended produce any sensable code you are of course also invited.  
If you are just curious but never intended produce any sensable code you are of course also invited.  


== Contents ==
== Contents ==

Revision as of 16:09, 20 April 2005

Terms and Concepts for Developers

Synopsis

This chapter is intended as an introductory overview for people intending to start programming with EMMA. Although there is a lot of documentation around e.g for the API, it is often hard to find out how the system really works. Knowing that it might be easier to figure out which part of the documentation one has to read and which part of the system is in need of a major improvement (or even a complete re-design). By presenting the architecture in a graphical way we try to make clear the interactions between the components. If you are just curious but never intended produce any sensable code you are of course also invited.

Contents