ArcBees est fière de présenter la 1ère édition du Tech&Whisky!

Ne manquez pas la 1ère édition du Tech&Whisky présentée par ArcBees, en collaboration avec Québec International, la VETIQ et la JCCQ qui aura lieu le 4 novembre prochain!

Il s’agit d’une occasion unique de découvrir le monde centenaire et mystérieux du Whisky, en compagnie des pros de l’équipe de Whisking, tout en réseautant avec des startup du domaine des technos.

Les places sont limitées alors ne tardez pas et inscrivez-vous en ligne dès maintenant!

TEC - Publicity - Email2013lv001-WIP004

GAE-Studio newsletter #2

Good morning, kickass GAE-Studio beta testers!

We’re excited to be releasing our next version of GAE-Studio. Our last iteration of testing went great, and we were able to enable a new GAE-Studio feature. For those of you who were in our first group of testers, we want to thank you for the time you put into GAE-Studio, and the feedback you have given us. We hope you and all you new testers who are joining us will push GAE-Studio even harder this time around, so it can evolve into a tool that will really make all our lives easier when it comes to managing Google App Engine development.

In this release, we’ve worked to enhance the visualisation tool, and we have also enabled the profiling tool. You’ll experience fewer bugs and will be able to integrate GAE-Studio with even more projects! The profiling tool itself will be completely reviewed to be more useful, but by activating the current version, you can already use it to see what is being pushed into the datastore as well as what is being pulled.

The ArcBees team has been working very hard, and most of them are going to head out for awhile on some well-earned vacations, so the upcoming iteration will be a really simple one. We’ll be working on a new authentication service for GAE-Studio that will let us operate it more like SaaS. In the future, we plan to release GAE-Studio as a commercial product, but it will remain free until all of you are satisfied that the user experience and feature set it offers make it a true Pro tool.

We’re starting to think about enabling Python, Go and PHP. If you think this is important, please vote for the language of your choice on our Bitbucket issue tracker so that we can know what to prioritize when we start that.

That wraps up another GAE-Studio newsletter! As always, log your issues and feature requests right within our Bitbucket issue tracker. That’s where all the action is. If you’re starting to become a heavy GAE-Studio user, we want to hear from you! We’re ready for some pretty deep conversation and collaboration with heavy users. We invite everyone to get in touch with us and tell us how GAE-Studio is helping you, and what you would like to see added or improved. Join our GAE-Studio Community on Google+, and meet other developers working on the leading edge of GAE development. While the community is for discussing GAE Studio, the people you meet there can help you in all things GAE-related.

Have fun Google App Engine-eering!

GAE-Studio newsletter #1

Good morning GAE-Studio users!

These are exciting days for us at ArcBees. We’re getting tons of great feedback about GAE-Studio from you, and we really, really appreciate it. We’re also excited to launch this first edition of our GAE-Studio newsletter (in future editions it will be redesigned to look more and more awesome). But most importantly, we’re excited because we are already ready to announce a new release of our software: GAE-Studio 0.3!

Our focus for this release was to integrate GAE studio with other existing projects. We’re almost satisfied with the outcome, but there are still some things that need doing. In the next release, we will make GAE-Studio even more usable from projects using Java and will try to avoid as much as possible conflicts with your own versions of dependencies that you could be using. This will add a lot to the usability and serviceability of the offering.

Besides these improvements, we’ve also moved the whole system from RPC to a REST API. This change lays the groundwork for two things. First, it provides an API you can use within your own applications, and second, it becomes easier to use a language other than Java this way. Think about it, Python, Go and PHP are the three other runtimes used in Google App Engine and it is on our roadmap to fully support those runtimes.

Many more changes are in the works for later releases. There’s been a lot of interest in our Profiler, so we plan to introduce a preview of it to those of you in our current beta group. We will also work to make sure that GAE-Studio can be used from Google App Engine directly, replacing the current datastore administration console. To do this, we have to create several security features to make sure only registered users can access GAE-Studio. While we’re reading back what we just wrote… Someone of the team already did it and it is available through using Google App Engine native security feature!

We are moving to a three-week release cycle from this point forward, until the project stabilizes, at which point we will publish daily builds. I know that documentation is lacking right now, so if you have any questions or problems, don’t hesitate to let us know. We’ll get back to you as soon as we possibly can, and we are genuinely interested in anything you might have to say about the product.

That’s all for now folks! As always, I invite you to log issues and feature requests right within our public issue tracker on Bitbucket. If you’re extensively using GAE-Studio already, please get in touch with us and tell us more about how it is helping you, and what you would like to see added or improved. Finally, I eagerly invite you to join our GAE-Studio Community on Google+ . We have a great group of people using the product, and the best way for you to meet all of them is by joining that Community.

Have fun Google App Engine-eering!

GWTP-Platform 1.0.1

Hi everyone,

We just released GWTP 1.0.1! In this release, we’ve fixed few bugs and improved some already existing feature.

Here’s a list of those changes for GWTP:

Here’s a list of those changes for GWTP Spring:

I would like to thanks all contributors to this release, especially +Lalit Mishra +Mathieu Clavel +Björn Moritz +Brandon Donnelson +Julien Dramaix +Christopher Viel +Maxime Mériouma-Caron +Mrabti Idriss. If I’ve forgot anyone, just let me know 😀

Have a great time with the new release!

GAE-Studio 0.2 is out!

Great news today!

We’ve just released GAE-Studio 0.2 wish include namespaces bulk action and a review user experience! That also means that a new wave of beta tester will be invited to join in today! It’s been a month since the last invitation wave and we’d great feedback from them. For that, we want to thank everyone so far and everyone else that didn’t got in for their patience.

User experience is still moving around and we’d like ask that you don’t hesitate to let us know how we could improve your experience with the application!

We’re also adding a new GAE-Studio public community on which we invite you to ask questions, discuss about the product and tell us what you think.

Have fun folks!

Are you ready for GAE-Studio?

I’m really excited today to share the tool with you that has helped us the most in developing Google App Engine web applications over the past two years: GAE-Studio! Most of us have had trouble managing local data through the GAE admin console in development mode. Non indexed columns aren’t shown, the table that displays your values can get ugly as it expands from left to right, and you can’t easily add, remove or modify values.

Those problems can all be left behind now, thanks to GAE-Studio! Some lucky beta users will be invited to use it for free, while we tweak the application based on what we learn from their usage. A full release will follow, after we add the features our closed beta users most asked for.

So keep your eyes on your inbox; the first set of invitations will be sent really shortly!

In the meanwhile, thanks for your support and your patience over the past few months. I and all the other Bees in the Hive know we’re really lucky to have your participation and support. If you didn’t subscribe to our beta, it is still time and can be done through our GAE-Studio website.

Have a great days fellas!

New GWTP milestone, GWTP 1.0

Today, we’re pleased to announce a new milestone – the launch of a major new version of GWTP. Over the past three years, we’ve had incredible input and collaboration across the GWTP community. We’ve also heard from GWTP users around the world, developing awesome and innovative web applications. All have contributed to making GWTP the solid, professional web application development framework it is today. All have helped make it one of the most-used GWT MVP frameworks in the world. Thank you all for your insights and collaboration.

We added many major new features in the update from GWTP 0.7 to 1.0. Here are just some of the improvements we made:

You can find the migration document here.

We are also launching a new GWTP website: gwtp.arcbees.com. The new site describes core product features, and introduces warranty protection packages for business users.

We believe in GWTP, and use it ourselves to build mission-critical business applications. We want you to have same confidence we do. Purchase a protection package, and we will both backup your projects and provide a warranty against platform defects. If some defect in GWTP threatens your product or your delivery schedule, we will investigate immediately, remedy the situation, and assume responsibility for the disruption. We trust that GWTP works as documented, and will stand behind that promise so you can be confident too.

Despite this new release, and the countless web applications that have been developed using GWTP over the years, we’re far from being out of ideas for further development. Join our open source network, and be part of the ongoing story of the evolution of GWTP.

Exactly three weeks from today, we will set up a Google Hangout to share the future of GWTP. We have a lot we want to discuss, and would highly value your input and participation.

See you in three weeks, and happy coding!

Jukito 1.2 is out!

It’s been a while since we had a release of Jukito and I’m excited to say that we finally released a new version! Jukito 1.2. Jukito is heavily used in GWTP for all unit test and is really an awesome product that can tag along your front end development as well as your backend development.

One new big feature has been added in Jukito 1.2 and it’s the ability to use Named @All. You can find the documentation on this new feature here: https://github.com/ArcBees/Jukito/wiki/@All

A complete list of what has been fixed from Jukito 1.1.2 here:
https://github.com/ArcBees/Jukito/issues?milestone=1&state=closed

For a high level tour of Jukito to I invite your to its official website:
http://jukito.arcbees.com/

Special thanks to przemekgalazka, sclassen, +Maxime Mériouma-Caron and +Brandon Donnelson that have greatly contributed to this release.

Structure for innovative businesses

When we first started ArcBees, we had a crazy idea to have independent cells of 10 to 12 people inside the business that could take on any projects they wanted.

This management style and choice was highly influenced by great precursors of our time like Robert C. Martin through his book “The Clean Coder“, Valve and their employee handbook  and now +Seb Paquet shared this interesting article that depicts exactly what I had in mind.

It’s a little bit funny how the author compare cells to state in United State, but in a sense, it’s not too far from the truth. Give the power to skilled individuals to take over their own dreams and they will achieve greatness. The difference between that kind of structure and starting your own business? You work hand to hand with other “states” in a direction where everyone will achieve their dreams. In a society where less than 4% of the startup ecosystem really get out of the incubator, it’s more important then ever to work together toward building businesses that is focused on the greatness of every single individuals rather than building a businesses that is focused on the well being of the stakeholders.

I would add a little bit of open source to this structure. Having several cells like those will, without a doubt, create a small internal economy for developer tools to help them work everyday and I can easily see cells immerge only to create projects that will help everyone else gets things done in the right way.

If we come back to the CEO or the “government”, they are there to serve and help the states to get their projects done. By creating a structure and giving the right amount of resources needed, we help them to achieve their goals while reducing any risk related when starting new projects. In the end, its about nurturing the right amount of skills to deliver continously successful projects.

Must read on GWT CellRenderer.

Fancy UI

Before GWT 2.5, writing a custom CellRenderer to present data in a certain manner was very complicated and very difficult to achieve.

All the custom UI code had to be written inside a Java class that inherits from the AbstractCell class, using HTML strings concatenation, which is a pretty clunky solution. If you want something cleaner you could choose to use the @Template class, but still it is very difficult to write and to maintain.

I always said, if only Google would add in GWT the ability to define the UI of a custom CellRenderer using XML, just like they did with the introduction of UiBinder, and to have the possibility to bind the UI components using the @UiField and to hook event processing using @UiHandler ==> Hooraaahhhh !!!! This dream came true with GWT 2.5, and it is called the UiRenderer.

In this article I’ll show some snippets of codes of a…

View original post 347 more words