Without doubt, the examples posted in the forum are VERY useful. But I would like to make one small "wish"...
All the examples typically use the packagename of "b4a.example".
If you are just working with one example app, this is not a problem.
But I often run into problems, and I see that others do to (especially newbies).... if there is an example app already installed on the device and the user tries to install a newer version with the same B4a.example package name, it fails with an error that doesn't really do a good job of explaining the real cause of the error.
Also, I will often leave an example app on my phone because I reference it a lot for whatever reason. But, if I install a new example, it will trash the other app and then I have to remember where I stored the other app's source code so I can reinstall it again.
So my wish is to simple set the packagename of examples to something descriptive of what the app does when posting the example, like:
b4a.example.Smtpdemo
or
b4a.example.clvdemo
All the examples typically use the packagename of "b4a.example".
If you are just working with one example app, this is not a problem.
But I often run into problems, and I see that others do to (especially newbies).... if there is an example app already installed on the device and the user tries to install a newer version with the same B4a.example package name, it fails with an error that doesn't really do a good job of explaining the real cause of the error.
Also, I will often leave an example app on my phone because I reference it a lot for whatever reason. But, if I install a new example, it will trash the other app and then I have to remember where I stored the other app's source code so I can reinstall it again.
So my wish is to simple set the packagename of examples to something descriptive of what the app does when posting the example, like:
b4a.example.Smtpdemo
or
b4a.example.clvdemo