ilan Expert Licensed User Longtime User May 24, 2017 #1 hi i have really small knowledge in Java but i still want to contribute more on this forum so i make libs with b4x language and compile them with b4x. the problem is that when i have the latest b4a version installed (and i do) the lib that i compile will be depended on this b4a version. even if it can run on a much lower b4a version. in microsoft excel you have an option to choose the minimum excel version to be compatible with when you save your file. i think b4a should also have that option so when you compile a lib with b4a 6.8 but you dont use any 3rd party libs only the core lib then it should run also on a smaller version of b4a. there is also another problem. if i compile a lib with b4a 5 and people use them but after 1 year i make a small modification in this lib with a newer version then people will not be able to use it on their b4a version until they update it. so is there any way to make a compiled lib run on the smallest b4a version it can run and not on the b4a version it was compiled? thank you, ilan
hi i have really small knowledge in Java but i still want to contribute more on this forum so i make libs with b4x language and compile them with b4x. the problem is that when i have the latest b4a version installed (and i do) the lib that i compile will be depended on this b4a version. even if it can run on a much lower b4a version. in microsoft excel you have an option to choose the minimum excel version to be compatible with when you save your file. i think b4a should also have that option so when you compile a lib with b4a 6.8 but you dont use any 3rd party libs only the core lib then it should run also on a smaller version of b4a. there is also another problem. if i compile a lib with b4a 5 and people use them but after 1 year i make a small modification in this lib with a newer version then people will not be able to use it on their b4a version until they update it. so is there any way to make a compiled lib run on the smallest b4a version it can run and not on the b4a version it was compiled? thank you, ilan
DonManfred Expert Licensed User Longtime User May 24, 2017 #2 You can have multiple installations of B4A. But seeing the issue with your lib and the reason for this thread i can aggree that it may be irritating...
You can have multiple installations of B4A. But seeing the issue with your lib and the reason for this thread i can aggree that it may be irritating...
ilan Expert Licensed User Longtime User May 24, 2017 #3 DonManfred said: You can have multiple installations of B4A. Click to expand... i dont think this should be the right solution. i would prefer b4a would store all core libs somewhere in a hidden folder and use the MINIMUM version that is needed when compiled.
DonManfred said: You can have multiple installations of B4A. Click to expand... i dont think this should be the right solution. i would prefer b4a would store all core libs somewhere in a hidden folder and use the MINIMUM version that is needed when compiled.
DonManfred Expert Licensed User Longtime User May 24, 2017 #4 ilan said: i dont think this should be the right solution Click to expand... As a workarount it IS a solution.
ilan said: i dont think this should be the right solution Click to expand... As a workarount it IS a solution.
Erel B4X founder Staff member Licensed User Longtime User May 24, 2017 #5 ilan said: so is there any way to make a compiled lib run on the smallest b4a version it can run and not on the b4a version it was compiled? Click to expand... No. The minimum version that it can run is the current version as this is the core library the IDE uses. You can release the source code together with the library if you want to support older version.
ilan said: so is there any way to make a compiled lib run on the smallest b4a version it can run and not on the b4a version it was compiled? Click to expand... No. The minimum version that it can run is the current version as this is the core library the IDE uses. You can release the source code together with the library if you want to support older version.
ilan Expert Licensed User Longtime User May 24, 2017 #6 Erel said: You can release the source code together with the library if you want to support older version. Click to expand... have not thought about this. i think its a great idea this will also allow others to improve the lib but it will also expose my bad coding style
Erel said: You can release the source code together with the library if you want to support older version. Click to expand... have not thought about this. i think its a great idea this will also allow others to improve the lib but it will also expose my bad coding style
Erel B4X founder Staff member Licensed User Longtime User May 24, 2017 #7 Releasing the source code is the best option. It also allows you to create cross platform modules using: Code: #If B4A ... #Else If B4J ... #Else If B4i ... #End If
Releasing the source code is the best option. It also allows you to create cross platform modules using: Code: #If B4A ... #Else If B4J ... #Else If B4i ... #End If
ilan Expert Licensed User Longtime User May 24, 2017 #8 Erel said: Releasing the source code is the best option. It also allows you to create cross platform modules using: Code: #If B4A ... #Else If B4J ... #Else If B4i ... #End If Click to expand... Done! https://www.b4x.com/android/forum/threads/spotlight-popup-menu.74901/page-3#post-505883
Erel said: Releasing the source code is the best option. It also allows you to create cross platform modules using: Code: #If B4A ... #Else If B4J ... #Else If B4i ... #End If Click to expand... Done! https://www.b4x.com/android/forum/threads/spotlight-popup-menu.74901/page-3#post-505883
