udg Expert Licensed User Longtime User Jun 7, 2018 #1 Hi all, what do you think if those paths would allow multiple folders? I'd like to organize Modules in a way where B4X classes are kept separate from B4J/B4A specific ones. Another roption could be the introduction of a new B4X-dedicated folder. I don't know. Just an idea. TIA
Hi all, what do you think if those paths would allow multiple folders? I'd like to organize Modules in a way where B4X classes are kept separate from B4J/B4A specific ones. Another roption could be the introduction of a new B4X-dedicated folder. I don't know. Just an idea. TIA
Erel B4X founder Staff member Licensed User Longtime User Jun 7, 2018 #2 Don't use shared modules at all. This feature is only kept for backward compatibility. You can put the modules in any folder you like and link them. https://www.b4x.com/android/forum/threads/b4x-modules-files-groups-and-folders.86587/#content The ability to reference modules is a game changer for cross platform development in B4X.
Don't use shared modules at all. This feature is only kept for backward compatibility. You can put the modules in any folder you like and link them. https://www.b4x.com/android/forum/threads/b4x-modules-files-groups-and-folders.86587/#content The ability to reference modules is a game changer for cross platform development in B4X.
udg Expert Licensed User Longtime User Jun 7, 2018 #3 Right. I should have posted this time ago..eheh
S sorex Expert Licensed User Longtime User Jun 14, 2018 #4 Erel said: The ability to reference modules is a game changer for cross platform development in B4X. Click to expand... I used this for years by just pointing B4A & B4i to the same shared modules folder which was in my sources folder just like the B4A, B4i & B4J folders. But indeed a little bit structure keeps things more clean, in my case it's a mess of 1 folder with a lot of these .bas files.
Erel said: The ability to reference modules is a game changer for cross platform development in B4X. Click to expand... I used this for years by just pointing B4A & B4i to the same shared modules folder which was in my sources folder just like the B4A, B4i & B4J folders. But indeed a little bit structure keeps things more clean, in my case it's a mess of 1 folder with a lot of these .bas files.
udg Expert Licensed User Longtime User Jun 14, 2018 #5 I used to keep Additonal Libraries and Shared Modules folders separate for each B4x product. Now I introduced a new folder "B4X" where I store B4X-only and XUI-B4x modules letting the link mechanism manage how to collect them when needed. Something like this: Code: Copy Development B4A ExtraLibs ExtraModules .... Projects Tests B4J same as above B4X xModules xuiModules This way I can still distinguish between pure-B4A/B4J modules/libs and B4X ones.
I used to keep Additonal Libraries and Shared Modules folders separate for each B4x product. Now I introduced a new folder "B4X" where I store B4X-only and XUI-B4x modules letting the link mechanism manage how to collect them when needed. Something like this: Code: Copy Development B4A ExtraLibs ExtraModules .... Projects Tests B4J same as above B4X xModules xuiModules This way I can still distinguish between pure-B4A/B4J modules/libs and B4X ones.
