![]() ![]() ![]() Still, we were and are hopeful that GAE-Studio will be useful for our developers. Since we love and have been using Objectify for years, we didn’t want to become their commercial competitor. Then some time later, Objectify-Insight came out, and our visualization engine would be in competition with it. Last summer, Google IO announced a new console for Google App Engine that removed much of the pain that GAE-Studio was designed to help with. It was planned to be our very first product that wasn’t going to be open sourced. One year later, after finding other users were feeling the same pain as we did using Google App Engine, we set out to improve GAE-Studio user experience. At the time, Google App Engine didn’t have any hooks on which we could build one, so we hacked our way around and built something useful for our own work. We were using Google App Engine heavily, and the lack of a good datastore admin console was a big problem. ![]() We’ve first started this venture almost 3 years ago when Arcbees was still in its inception. Some may wonder why we chose to open source what was going to be our first official product. You can also read our documentation to learn more about how to install GAE-Studio in your Google App Engine application. We released an official, stable version 1.0 a couple of days ago that you can see in action on our demo website. You can find the source code under our Arcbees github organization as well as on maven central. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |