You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Busula could be transformed into a CRD rendering engine with an outer navigation part. The "kernel" would focus purely on rendering CRDs and could be reused in both ApeiroRA and the new version of Busula. In ApeiroRA, this kernel would provide the rendering for CRDs, while in Busula, the same kernel would be used along with its own additional navigation system. This approach would allow Busula to leverage the CRD rendering capabilities effectively while maintaining its distinct navigation features, leading to greater consistency and reusability across different environments.
Since Busula already supports deep links, we can leverage this functionality to address specific CRD objects or any other content within the Busula kernel directly without needing to use the navigation bar. These deep links, configured within OpenMFP’s navigation, can point to specific content within Busula (e.g., a single CRD object or a detailed view), ensuring that when a user selects a link from OpenMFP’s navigation, Busula will load and display the corresponding content dynamically.
Reasons
Busula currently loads and renders its own navigation system alongside its core content. This works well for standalone use where Busula operates independently with full control over the navigation and interface. However, in environments like ApeiroRA, which relies on the OpenMFP micro-frontend framework, Busula's navigation becomes redundant. OpenMFP already provides its own outer frame and navigation system, and in this scenario, the double-loading of Busula’s own navigation causes unnecessary resource usage and performance overhead.
Even though it’s possible to hide Busula’s navigation through configuration, the navigation elements are still loaded in the background, leading to performance degradation. This is especially problematic in integrated environments like OpenMFP, where the navigation system is already handled by the parent framework, making Busula's additional UI elements unnecessary and inefficient.
The text was updated successfully, but these errors were encountered:
Description
Busula could be transformed into a CRD rendering engine with an outer navigation part. The "kernel" would focus purely on rendering CRDs and could be reused in both ApeiroRA and the new version of Busula. In ApeiroRA, this kernel would provide the rendering for CRDs, while in Busula, the same kernel would be used along with its own additional navigation system. This approach would allow Busula to leverage the CRD rendering capabilities effectively while maintaining its distinct navigation features, leading to greater consistency and reusability across different environments.
Since Busula already supports deep links, we can leverage this functionality to address specific CRD objects or any other content within the Busula kernel directly without needing to use the navigation bar. These deep links, configured within OpenMFP’s navigation, can point to specific content within Busula (e.g., a single CRD object or a detailed view), ensuring that when a user selects a link from OpenMFP’s navigation, Busula will load and display the corresponding content dynamically.
Reasons
Busula currently loads and renders its own navigation system alongside its core content. This works well for standalone use where Busula operates independently with full control over the navigation and interface. However, in environments like ApeiroRA, which relies on the OpenMFP micro-frontend framework, Busula's navigation becomes redundant. OpenMFP already provides its own outer frame and navigation system, and in this scenario, the double-loading of Busula’s own navigation causes unnecessary resource usage and performance overhead.
Even though it’s possible to hide Busula’s navigation through configuration, the navigation elements are still loaded in the background, leading to performance degradation. This is especially problematic in integrated environments like OpenMFP, where the navigation system is already handled by the parent framework, making Busula's additional UI elements unnecessary and inefficient.
The text was updated successfully, but these errors were encountered: