This page provides a curated list of namespaces used by published 4D components, created by both 4D and the developer community.
With the growing number of available 4D components and the 4D Project Dependencies feature, it’s easier than ever to work with updated components. However, the increase in components also means more namespaces, raising the risk of duplicate namespaces and potential conflicts.
ⓘ Note:
A namespace ensures no conflict arises when a project uses different components that may have classes or functions with identical names.
By registering your namespace here, you can:
- Avoid Conflicts: Prevent issues that occur when two components share the same namespace.
- Stay Organized: Ensure your component can be integrated smoothly with others in larger projects.
- Promote Consistency: Help the 4D developer community maintain a clear, organized system for components.
Before selecting a namespace for your component, we highly recommend consulting the list below to avoid duplicates. Once you’ve chosen a unique name, submit it for inclusion in this registry. For details on how to contribute, please refer to our Contribution Guidelines.
| Namespace | Component |  |
|---|---|---|
Build4D |
Build4D | |
color |
Color with Classes | |
mcro |
4D Macros | Compatible |
NetKit |
4D NetKit | |
pop |
4DPop | Compatible |
popm |
4DPop Macros | Compatible |
popq |
4DPop QuickOpen | Compatible |
rgx |
Regex with Classes | Compatible |
svg |
SVG with Classes | |
ui |
UI with Classes |
We welcome contributions! If you'd like to add your namespace to this list, please follow our contribution guidelines.
Your participation helps us keep this registry accurate and up-to-date. Thank you for helping the 4D developer community thrive!