fredo Well-Known Member Licensed User Longtime User Nov 21, 2023 #1 I am currently familiarising myself with DSE. After looking at the sample projects, I see the possibility of saving a lot of time in the development of the UI components in the future. Especially the "DDD.AddClass(...)" function seems to make it very clear and time-saving to implement the Material3 standards. In this context, I'm unsure about using the DSE in multiple B4xPages when they all have their own layouts. 1. Is it sufficient to define "Public dd as DDD" in B4XPages.MainPage and use it by reference ( B4XPages.MainPage.dd ) by all other B4xPages? 2. Or does it make more sense to use a "Private dd as DDD" in each B4xPages module?
I am currently familiarising myself with DSE. After looking at the sample projects, I see the possibility of saving a lot of time in the development of the UI components in the future. Especially the "DDD.AddClass(...)" function seems to make it very clear and time-saving to implement the Material3 standards. In this context, I'm unsure about using the DSE in multiple B4xPages when they all have their own layouts. 1. Is it sufficient to define "Public dd as DDD" in B4XPages.MainPage and use it by reference ( B4XPages.MainPage.dd ) by all other B4xPages? 2. Or does it make more sense to use a "Private dd as DDD" in each B4xPages module?
William Lancee Well-Known Member Licensed User Longtime User Nov 21, 2023 #2 @Erel confirms that DDD is just like any other class. https://www.b4x.com/android/forum/threads/b4x-dse-designer-script-extensions.141312/post-895745 As such, an instance can be created anywhere. For convenience, I would make one in each B4Xpage that needs it. Then, any view names that that have different meaning in different pages could be used without conflict in the various look-up tables. Upvote 1
@Erel confirms that DDD is just like any other class. https://www.b4x.com/android/forum/threads/b4x-dse-designer-script-extensions.141312/post-895745 As such, an instance can be created anywhere. For convenience, I would make one in each B4Xpage that needs it. Then, any view names that that have different meaning in different pages could be used without conflict in the various look-up tables.
