mirrors/TiddlyWiki5
1
0
Fork 0
mirror of https://github.com/Jermolene/TiddlyWiki5 synced 2024-11-27 03:57:21 +00:00
Code Issues Releases Wiki Activity

Add startup sequence diagram

Browse Source
This commit is contained in:
Jermolene 2014-05-05 17:06:34 +01:00
parent b24ec8009d
commit 95def8b857
3 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
editions/tw5.com/tiddlers/images/Startup Modules.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 11 KiB

3
editions/tw5.com/tiddlers/images/Startup Modules.svg.meta Normal file
View File

@ -0,0 +1,3 @@
title: Startup Modules.svg
type: image/svg+xml
tags: picture

10
editions/tw5.com/tiddlers/mechanisms/StartupMechanism.tid
View File

@ -15,16 +15,16 @@ Modules with their ''module-type'' field set to `startup`:
* May export a `name` property that is used to identify the task * May export a `name` property that is used to identify the task
* May export a `after` property containing an array of names of dependent tasks that must be run before this one * May export a `after` property containing an array of names of dependent tasks that must be run before this one
* May export a `before` property containing an array of names of tasks that must be run after this one * May export a `before` property containing an array of names of tasks that must be run after this one
* May export a `platforms` property containing an array of names of platforms that are required in order for the startup module to be executed. The defined platforms are ''node'' and ''browser'' * May export a `platforms` property containing an array of names of platforms that are required in order for the startup module to be executed. The defined platforms are ''node'' and ''browser''. If the `platforms` property is not provided it defaults to `["node","browser"]`
! Startup Processing ! Startup Processing
The startup mechanism begins by sequentially executing the tasks that have no dependencies. It then continues executing tasks as they are unlocked by the completion of their dependencies. Startup modules are executed in sequence according to their declared dependencies.
There is no guarantee of the execution order of tasks that share the same dependencies. There is no guarantee of the execution order of tasks that share the same dependencies.
! Startup Tasks ! Startup Modules
The core defines the following sequence of named startup tasks: The core defines the following startup modules:
|!Task Name |!Description | {{Startup Modules.svg}}