We are building a community-written O'Reilly Cookbook about how to build great Android applications. It will be full of how-to information along with code snippets that illustrate the ideas presented. It will be complete, featuring both how-to's that overlap with the official documentation, and material that goes beyond this to be more tutorial, more in-depth, or explaining "lessons from the trenches": what actually works to get the application functioning well. Unlike most books written by one, two or a few individuals, this will have input from hundreds of contributors, who will be able to view and comment on each others' recipes before the book is printed. And after the book is printed, this site will continue to exist - with a larger collection of recipes than will fit in the printed book - and serve as an Android developer resource site long after.
We welcome contributions from anybody who has something useful to say about how to make usable and successful Android applications. There are several ways of contributing: experienced Android developers can write recipes; newer ones can suggest recipes that they'd like to see; anybody can read and comment on recipes; anybody can vote for existing recipes (voting indicates that you like the recipe and/or think it should be included in the printed edition of the book). All we ask of contributors is the following:
From the authors of the German book "JSF@work" (see http://jsfatwork.irian.at). A lightweight framework for J2EE web applications which makes a clean step out of session handling problems when using persistence frameworks. Also features like aspect oriented JSF are introduced. All provided by a best-practice web application.
Oooh - sbd has realised this old idea: To let sourcode sound. Anyway, great it's done... "CodeSounding: computer generated music sounds from a source code structure Consider CodeSounding as a way to make computer-generated music, or as a sonification libr