Anboto adds multiple additional features to U++ so that your projects can be developed faster. It includes the next libraries:
- General use
- Engineering and scientific
The code is tested daily to ensure full functionality without disruption. However, to ensure the best performance it is advisable to put Anboto first in the package list on Assembly setup/Package nests.
All anboto packages are (or will be, some of them are part of uppsrc still, I was considering to move them later this year) also available through UppHub. We will attempt to track anboto changes and merge them with UppHub nests.
I would like to add that the situation with Anboto is very sad to me. The problem here is that we need to speed additional very limited resource to support for UppHub. For many users UppHub will constitute the first source of this packages. The anobo project adds unnecessary indirection. It is much easier to once click to download package, instead of configuring custom assemby from custom repository. Backing to resources, Mireks time is very valuable I would see that the time he will spend on maintaining Anboto UppHub packages on our side will be spend on new functionality or article about Upp.
Koldo please rethink the whole situation again. We will provide any information and help you need. I think that anobo packages should be develop under Libraries4U organization. Each package should be develop as separate repository. As I said the learning curve is not so big, so after one week it should be substitute for single assembly.
We are also open to any UppHub improvements you found useful in context of package development. During all these years with Upp I didn't agree with certain decision made by Mirek and I have never decided to create real fork with exclusive content, because I was thinking that it will be bad for community. Unity is our strength.