EMMAWiki/TermsAndConcepts/ForDevelopers: Difference between revisions

From BRF-Software
Jump to navigation Jump to search
imported>MichaelDondrup
No edit summary
imported>MichaelDondrup
No edit summary
Line 4: Line 4:
== 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 to produce any piece of code you are of course also invited.  


After reading this chapter you will know:
After reading this chapter you will know:
Line 10: Line 10:
* what are the main components of the software
* what are the main components of the software
* how the components interoperate
* how the components interoperate
* which module make EMMA a web-application
* which modules make EMMA a web-application
* what are the main classes and objects
* what are the main classes and objects
* how do Tools, Jobs and Functions work
* how do Tools, Jobs and Functions work
Line 21: Line 21:
* have an impression of [[EMMAWiki/TermsAndConcepts/ForUsers| Terms and Concepts from a User's perspective]]
* have an impression of [[EMMAWiki/TermsAndConcepts/ForUsers| Terms and Concepts from a User's perspective]]
* have some basic programming skills even though there are not many code examples
* have some basic programming skills even though there are not many code examples
* know about how object-oriented programming and design works


== Contents ==
== Contents ==
* /ProgrammingLanguages
* /ArchitectureOverview
* /ModularDesign
* /WebApplicationAndCGI
* /O2DBI
* /BRIDGE
* /ToolsJobsAndFunctions

Revision as of 14:29, 21 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 to produce any piece of code you are of course also invited.

After reading this chapter you will know:

  • what are the main components of the software
  • how the components interoperate
  • which modules make EMMA a web-application
  • what are the main classes and objects
  • how do Tools, Jobs and Functions work
  • how interoperability with other software works
  • what kind of programming skills will be neccessary
  • where to look to improve a certain functionality

Before reading this you should

Contents

  • /ProgrammingLanguages
  • /ArchitectureOverview
  • /ModularDesign
  • /WebApplicationAndCGI
  • /O2DBI
  • /BRIDGE
  • /ToolsJobsAndFunctions