Difference between revisions of "Complexity"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
|coordimg1=0, 0, 0 | |coordimg1=0, 0, 0 | ||
|simploduction=<ul> | |simploduction=<ul> | ||
| − | <li> | + | <li>How to handle complex processes or content.</li> |
| − | <li>Extensive or complex content can be better understood if it is broken down into | + | <li>Extensive or complex content can be better understood if it is broken down into parts.</li> |
| − | <li>Long processes that | + | <li>Long processes that need user input should be split into several simpler processes.</li> |
| − | <li> | + | <li>A saving function should allow users to pause long processes and resume them later without losses.</li></ul> |
|coordsimplo=0, 0, 0 | |coordsimplo=0, 0, 0 | ||
|testimonial=It seems that there is no testimonial for this topic yet. <a href="https://lehmannmax.de/Survey/survey.html">If you want to contribute, click here to get in touch.</a> | |testimonial=It seems that there is no testimonial for this topic yet. <a href="https://lehmannmax.de/Survey/survey.html">If you want to contribute, click here to get in touch.</a> | ||
| Line 21: | Line 21: | ||
<div class="text_content"> | <div class="text_content"> | ||
==simple introduction== | ==simple introduction== | ||
| − | * | + | * How to handle complex processes or content. |
| − | * Extensive or complex content can be better understood if it is broken down into | + | * Extensive or complex content can be better understood if it is broken down into parts. |
| − | * Long processes that | + | * Long processes that need user input should be split into several simpler processes. |
| − | * | + | * A saving function should allow users to pause long processes and resume them later without losses. |
==testimonial== | ==testimonial== | ||
It seems that there is no testimonial for this topic yet. | It seems that there is no testimonial for this topic yet. | ||
| − | If you want to contribute, click [ | + | If you want to contribute, click [https://lehmannmax.de/Survey/survey.html here] to get in touch. |
==[[Complexity_References|Reference Collections for Complexity]]== | ==[[Complexity_References|Reference Collections for Complexity]]== | ||
Revision as of 13:34, 3 June 2021
| headline | Complexity |
|---|---|
| headline coordinates | 1.000, 290.903, 0.000 |
| image | /wiki/images/Complexity.png |
| image coordinates | 0, 0, 0 |
| simple introduction |
|
| simple introduction coordinates | 0, 0, 0 |
| testimonial | It seems that there is no testimonial for this topic yet. <a href="https://lehmannmax.de/Survey/survey.html">If you want to contribute, click here to get in touch.</a> |
| testimonial coordinates | 0, 0, 0 |
| links to | |
| belongs to | Attention |
| contains | Complexity_References |
simple introduction
- How to handle complex processes or content.
- Extensive or complex content can be better understood if it is broken down into parts.
- Long processes that need user input should be split into several simpler processes.
- A saving function should allow users to pause long processes and resume them later without losses.
testimonial
It seems that there is no testimonial for this topic yet.
If you want to contribute, click here to get in touch.