Sept. 2014 end AEBL update

Well, a lot has been going on in the AEBL world.

It's hard to even remember what has been happening, let alone where to begin.

There have been a significant number of enhancement tests for AEBL, so let's start with mentioning that we've moved our primary project page and we have now made direct access available to the AEBL image for those who would like to try it out or actually use it in a real world application.
 

So beginning with the change of the project page, we are still maintaining the Source Forge project page as a mirror, but all the direct updates are happening on the Github project page:
https://github.com/krattai/AEBL

Personally and professionally, we (I) don't have any issue or concern with SourceForge, which is why SourceForge remains the mirror.  And in all fairness, there are certain things that a project and code repository with the time and experience in the industry provides, that newcomers like github may not, either by choice or because github still hasn't developed the enhanced features.

That said, a lot of developers have switched to github, for many reasons, and for that reason, in order to reach the maximum open source developer audience which will help with further advancements of AEBL, we've chosen to make our main home at Github.

OK, enough about that.  On to, how can you get your hands on an AEBL. For the "do it yourself" type, we'll direct you to the AEBL project wiki and the page on making your own:
https://github.com/krattai/AEBL/wiki/Installation

Of course, not everyone has the time, skill, or energy, or maybe some people just have better sense than those who like to tinker, for those, we will direct you to contact us by email and we can either provide a ready to go AEBL for you, or can help you find someone in your area who can make one for you.  Contact us at aeblmobile@gmail.com and we will help you out.

And for everything else?  Well, there is too much to mention in a single blog article, and some of what we have been up to probably deserves its own, dedicated post, so we will simply end this post by saying...

Stay tuned!