Why not???I will soon publish the library for B4A.
I already created and works on the B4I version, but I'm not entirely convinced of publishing it.
Mainly because I believe there is something similar with a native view.Why not???
Thats because, i publish it as a class, so i can modify the class, members can help me on bugs or new features and i dont need to tell it the remote compiler.I also observed that iOS libraries have few downloads so they are not in demand. Third, i use the AnyWhere remote compiler and each library must first be authorized to be compiled (it's a boring thing)
In some cases I chose to publish it as b4xlib. But not all circumstances are the same and one does not always decide to share the source.Thats because, i publish it as a class, so i can modify the class, members can help me on bugs or new features and i dont need to tell it the remote compiler.
agreed, i had created a business plan for me, but the separation would have been too time-consuming. My considerations was a free version with limitations and without source code and a premium version with source code and more features. On the end I have agreed to take everything that I do as a reference for later projects and give the chance to learn the forum from my views to create their own views. If i use other sources, then i put a link to the source in the code.In some cases I chose to publish it as b4xlib. But not all circumstances are the same and one does not always decide to share the source.
Thinks are differentHowever this is not the only reason why I am considering not to run the ios version
Which issue have you encountered with xCLV and B4J? There are no known issues. Worth start a new thread with the information.because it depends on the XCLV and this is not working well on B4J