Component Registry - Revision history

GHXX at 11:45, 22 August 2026

2026-08-22T11:45:16Z

← Older revision		Revision as of 11:45, 22 August 2026
Line 26:		Line 26:
	</syntaxhighlight>		</syntaxhighlight>

	{{Navbox content}}		== Notes ==
			Technically the component registry is not a component, but it still is listed in this category as it is closely tied to this topic.{{Navbox content}}

GHXX at 12:20, 18 August 2026

2026-08-18T12:20:55Z

← Older revision		Revision as of 12:20, 18 August 2026
Line 1:		Line 1:
	The Component Registry allows accessing all currently available [[Component\|Components]] and is the most convenient way of accessing components.		The Component Registry allows accessing all currently available [[Component\|Components]] and is the most convenient way of accessing components. Every Lua vm instance contains a global variable called <code>components</code> which contains this object.

	{\| class="wikitable"		{\| class="wikitable"

GHXX at 23:54, 1 August 2026

2026-08-01T23:54:36Z

← Older revision		Revision as of 23:54, 1 August 2026
Line 24:		Line 24:
	end		end
	end		end
	</syntaxhighlight>{{Navbox content}}		</syntaxhighlight>

			{{Navbox content}}

GHXX at 23:54, 1 August 2026

2026-08-01T23:54:26Z

← Older revision		Revision as of 23:54, 1 August 2026
Line 6:		Line 6:
	! Name !! Type !! Description		! Name !! Type !! Description
	\|-		\|-
	\| style="white-space: nowrap;" \| <code>:list()</code> \|\| <code>~~iterator~~ -> (string, userdata)</code> \|\| Returns an iterator function that, in each invocation returns a string representing the type of the current component along with the actual userdata instance.		\| style="white-space: nowrap;" \| <code>:list()</code> \|\| <code>function() -> (string, userdata), table, nil</code> \|\| Returns an iterator function that, in each invocation returns a string representing the type of the current component along with the actual userdata instance.
	\|-		\|-
	\| style="white-space: nowrap;" \| <code>:getFirst(componentType:string)</code> \|\| <code>userdata</code>\|\| Returns the first component of the given <code>componentType</code> or <code>nil</code> if no matching component exists.		\| style="white-space: nowrap;" \| <code>:getFirst(componentType:string)</code> \|\| <code>userdata</code>\|\| Returns the first component of the given <code>componentType</code> or <code>nil</code> if no matching component exists.
	\|}		\|}

			While <code>:list()</code> looks very intimidating, it can simply be used in a for-loop in place of <code>ipairs(*)</code>. The built-in [[UEFI]] uses the following code to iterate over all components to find any bootable devices:<syntaxhighlight lang="lua" line="1">
	{{Navbox content}}		local bootables = {}
			for compType, elem in components:list() do
			print("- " .. compType)
			if compType == "massStorage" then
			if elem:fileExists("boot.lua") then
			-- we found a bootable medium, use it as default if not already set
			defaultBoot = defaultBoot == nil and idx or defaultBoot
			bootables[idx] = elem
			end
			idx = idx + 1
			end
			end
			</syntaxhighlight>{{Navbox content}}

GHXX at 23:43, 1 August 2026

2026-08-01T23:43:59Z

← Older revision		Revision as of 23:43, 1 August 2026
Line 6:		Line 6:
	! Name !! Type !! Description		! Name !! Type !! Description
	\|-		\|-
	\| style="white-space: nowrap;" \| <code>:list()</code> \|\| <code>~~function~~ -> (string, userdata)</code> \|\| Returns an iterator function that, in each invocation returns a string representing the type of the current component along with the actual userdata instance.		\| style="white-space: nowrap;" \| <code>:list()</code> \|\| <code>iterator -> (string, userdata)</code> \|\| Returns an iterator function that, in each invocation returns a string representing the type of the current component along with the actual userdata instance.
	\|-		\|-
	\| style="white-space: nowrap;" \| <code>:getFirst(componentType:string)</code> \|\| <code>userdata</code>\|\| Returns the first component of the given <code>componentType</code> or <code>nil</code> if no matching component exists.		\| style="white-space: nowrap;" \| <code>:getFirst(componentType:string)</code> \|\| <code>userdata</code>\|\| Returns the first component of the given <code>componentType</code> or <code>nil</code> if no matching component exists.

GHXX: Created page with "The Component Registry allows accessing all currently available Components and is the most convenient way of accessing components. {| class="wikitable" |+ ComponentRegistryUD methods |- ! Name !! Type !! Description |- | style="white-space: nowrap;" | `:list()` || `function -> (string, userdata)` || Returns an iterator function that, in each invocation returns a string representing the type of the current component along with the actu..."

2026-08-01T23:42:11Z

Created page with "The Component Registry allows accessing all currently available Components and is the most convenient way of accessing components. {| class="wikitable" |+ ComponentRegistryUD methods |- ! Name !! Type !! Description |- | style="white-space: nowrap;" | <code>:list()</code> || <code>function -> (string, userdata)</code> || Returns an iterator function that, in each invocation returns a string representing the type of the current component along with the actu..."

New page

The Component Registry allows accessing all currently available [[Component|Components]] and is the most convenient way of accessing components.

{| class="wikitable"
|+ ComponentRegistryUD methods
|-
! Name !! Type !! Description
|-
| style="white-space: nowrap;" | <code>:list()</code> || <code>function -> (string, userdata)</code> || Returns an iterator function that, in each invocation returns a string representing the type of the current component along with the actual userdata instance.
|-
| style="white-space: nowrap;" | <code>:getFirst(componentType:string)</code> || <code>userdata</code>|| Returns the first component of the given <code>componentType</code> or <code>nil</code> if no matching component exists.
|}

{{Navbox content}}