Ferreteria/v0.6/sys/Registry: Difference between revisions
< Ferreteria | v0.6
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
* {{l/sub|class}} registry | * {{l/sub|class}} registry | ||
* {{l/sub|object}} registry | * {{l/sub|object}} registry | ||
==Notes== | |||
==={{fmt/date|2025|10|16}}=== | |||
I think the way this needs to work is that we should have two main clades for each registry-type: | |||
# Main registry | |||
# Per-class-slug roster: | |||
#* Roster for class-names | |||
#* Roster for objects | |||
Revision as of 13:39, 16 October 2025
|
Registries different types and how they work
|
There are two primary types of "registry": class and object. Both of these are basically just arrays in which stored items follow a specific rule-set. In general, though, you have a list of things -- either classes or objects -- where the specific thing needed depends on context and identity.
The exact means of determining the context is perhaps the piece with the most variation in how it is implemented. It can be done by separate Registry classes or by using a "class slug" in a master-array.
The identity is simpler: the Registry (assuming the context is already specified) accepts a slug-string and returns the thing requested.
Pages
Notes
2025-10-16
I think the way this needs to work is that we should have two main clades for each registry-type:
- Main registry
- Per-class-slug roster:
- Roster for class-names
- Roster for objects