Google Developer Day 2011 was a great opportunity to show QAFE to developers and get some instant feedback. We, QAFE team, are true Google Webtoolkit fans and we showed what we did with that technology. Furthermore, we made it really easy to deploy to App Engine (App Engine has some restrictions which might result in serious code refactoring). We took care of the restrictions so that everybody can deploy to App Engine in a matter of seconds!
The developer Day really was not about sales. We got usual feedback and some very good questions.
The QAFE showcase was the QAFE Runtime, the Technology Independent implementation (in this case using Adobe Flex) and the Developer Environment. The Eclipse IDE was extended with the latest QAML Builder Plugin, which not only has a drag-n-drop from the UI but also for the Service Oriented Architecture, integrating with resources. The fact that the this was graphically shown, was a huge surprise for many. QAFE workspace is fully maven based, so having unit tests/selenium or debugging is quite easy. Also, not having compile time, but a simple reload of the applications, was an eye-opener for many visitors to our sandbox location.
In between giving demonstrations, we had some time to visit some of the sessions, which were of excellent quality. See: http://www.google.com/events/developerday/2011/berlin/agenda.html Especially Eric Bidelman’s session with the teasing title “These Aren’t the Sites You’re Looking For: Modern HTML5 Web Apps ” was excellent. Another one was about BigQuery, live demos of the new GoogleTV, HTML5, Android, etc. All about what we make of the web, and we still have a lot to do: for developers next year will be even more interesting!
For pictures of GDD11, and to connect with us on Google Plus, see: https://plus.google.com/108191651333422386424/
Google Developer Day 2011 Berlin was amazing!
QAFE on Google Developer Day 2011 #GDD11
Is anyone going to the Google Developer Days 2011 in Berlin this weekend ? If so, we can meetup. QAFE was invited to showcase in the Developer’s Sandbox. We’ll be there from early morning until the end…
BTW, If you are not there, I’ll try to make some pictures and share it with you (Google style also of course on https://plus.google.com/112797501883261863370/).
Regards,
QAFE-team
Go Cloud with Google App Engine
One of the cool features of the new QAFE 1.4 release is Google App Engine Compatibility. Why is this cool, how did we do it, and what does this mean for you? Here are some answers:
First of all, according to us the Google App Engine Platform is one of the most advanced and reliable cloud service available for Java Web Applications. There are others of course, like the solutions from Amazon and the CloudFoundry from VMWare/Spring, but we particularly like Google App Engine because it is a complete solution including scalable storage and some really nice API’s (like the new Task API).
To be compatible to run on Google’s App Engine, typical webapplications meet some real challenges. The most striking is that App Engine follows the JEE spec quite closely. Specifically the Webcontainer specification. A Webcontainer implementation like Jetty or Tomcat allow you the write code which isn’t JEE compliant, for example, the log4j (which can be found in lots of Java webapplications) is a violation of the “write to disk” restriction of JEE specification. We needed to tackle a couple of these violations to get QAFE running on App Engine.
We managed and the result is that the QAFE Engine is now App Engine (>=1.5) compatible: so what does that mean for you?
The QAFE Engine now allows you to use Google’s Webtoolkit Technology without having to learn all the details about Google’s App Engine. Writing Enterprise WebApplications is usually cumbersome and most of the times it’s boilerplate code (parsing request, etc). Whereas QAFE offers the quick and easy way to create Enterprise Applications that are instantly deployable.
You will be pleased to find out the QAFE engine scales very well. For example, when writing modern Webapplications the use of Javascript libraries is default. The more Javascript you write, the longer the download time becomes. In GWT Javacode is transformed to Javascript code, which is good, but for large applications the same goes: the Javascript needs to be downloaded (although, the GWT team already is doing a great job to improve this). The difference with the QAFE Engine is that QAFE stays the same size, no matter how many applications are deployed. So the use of memory space will grow, but not the engine size itself.
This keeps QAFE as a platform for writing Enterprise Applications, running on Google for Java Web Applications, a lean as can be; offering you all you need to get the job done faster, without the hassle.
With the increased chance that your business is moving to the cloud as well, this feature of the QAFE Engine should make you want to sign up for that Free Trial today.
New demo in GWT and Flex
We are happy to announce that you can now try out the latest demo environments of QAFE. In three flavors: GWT, Adobe Flex and Adobe AIR. Discover for yourself that QAFE’s declarative way of developing is easy. Test a live Oracle Forms Conversion from an FMB file. Or simply have a look around. For a more elaborate demonstration of the QAFE framework for Enterprise Applications or QAFE Forms Conversion, either in GWT or Flex, please contact us!
Update from QAFE Team
QAFE Demo: "Try Me" (part 1)
When you click on the “Try Demo” on the main page, you’ll see the showcase “QAFE” application and some code snippets.
In the menu bar (see image) you’ll find the “Try Me” menu-item. This will open the a window which is meant purely for demo purposes and maybe even prototyping (e.g., for business analysts).
(more…)
QAFE Basics: Declarative SOA (part 1)
When you go to http://demo.qafe.com, the first application that starts is the “Showcase” Application.
This Showcase application is a QAFE Application, written in QAML. In the tree on the right, you’ll see Components and Events. (more…)
Declarative SOA + UI in one go: QAFE!
Declarative UI has been buzzing lately in the serveral Web UI communities (like Google’s GWT-incubator project). We know there is a need for this. Nevertheless, eventhough you have your declarative UI ready, you still have to program the serverside in the language of that technology.
Wouldn’t it be great if you could easily access your database or any other backend in a declarative way ? (more…)
