Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
| en:modul:m291:learningunits:lu04:theorie:01 [2025/01/21 11:26] – gelöscht vdemir | en:modul:m291:learningunits:lu04:theorie:01 [2025/03/07 07:57] (aktuell) – vdemir | ||
|---|---|---|---|
| Zeile 1: | Zeile 1: | ||
| + | ====== LU04a - Framework VS Library ===== | ||
| + | |||
| + | ===== Learning objectives ===== | ||
| + | - Explaining what a software library is | ||
| + | - Definingwhat a framework is | ||
| + | - Naming the differences of both | ||
| + | - Explaining the Who-Calls-Who Principle | ||
| + | |||
| + | ===== Introduction ===== | ||
| + | Libraries and frameworks streamline software development by providing reusable code and predefined structures. Libraries focus on specific tasks, enabling modularity, while frameworks establish an overall application architecture, | ||
| + | |||
| + | First, however, it is important to distinguish between the terms. “Library” and ‘framework’ are often used interchangeably - which, strictly speaking, is wrong. Even if the transition is indeed fluid in many respects, there are fundamental differences between the two. | ||
| + | |||
| + | ===== Library ===== | ||
| + | A software library is a collection of pre-written, | ||
| + | |||
| + | |||
| + | ===== Framework ===== | ||
| + | A framework is a structured platform or foundation for developing applications, | ||
| + | |||
| + | {{ : | ||
| + | ===== Summary ===== | ||
| + | |||
| + | {{: | ||
| + | {{: | ||
| + | |||
| + | Libraries and frameworks are tools that simplify software development by providing pre-written code. Libraries offer reusable functions for specific tasks, giving developers control over when and how to use them. Frameworks, on the other hand, define a structured architecture, | ||
| + | |||
| + | ===== Who-Calls-Who Principle ===== | ||
| + | There is also another aspect, which claims to explain the difference between frameworks and libraries: The Who-Calls-Who-principle. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | The " | ||
| + | |||
| + | 1. **Library**: | ||
| + | |||
| + | 2. **Framework**: | ||
| + | |||
| + | This distinction highlights the differing roles and levels of control in using libraries versus frameworks. | ||
| + | |||
| + | ===== Frameworks vs. Library ===== | ||
| + | ^Library ^Framework ^ | ||
| + | | Library is a set of reusable functions used by computer programs. | Framework is a piece of code that dictates the architecture of your project and aids in programs. | | ||
| + | | You are in full control when you call a method from a library, and the control is then returned. | The code never calls into a framework; instead, the framework calls you. | | ||
| + | | It’s incorporated seamlessly into existing projects to add functionality that you can access using an API. | It cannot be seamlessly incorporated into an existing project. Instead, it can be used when a new project is started. | | ||
| + | | They are important in program linking and binding process. | They provide a standard way to build and deploy applications. | | ||
| + | | Example: jQuery is a JavaScript library that simplifies DOM manipulation. | Example: AngularJS is a JavaScript-based framework for dynamic web applications. | | ||
| + | |||
| + | ===== Additional Material ===== | ||
| + | You will find a list with JavaScript-Libraries und Frameworks including an explaination and a rathing as follows: [[https:// | ||
| + | |||
| + | ---- | ||
| + | [[https:// | ||