Hacking A Startup DroidRules HackedLabs Posts My Google Knols
There are some details I cannot reveal as of yet. However, I am being asked to discuss an ‘opportunity’ mid-week next week that would lead to a more formal developer contributing role to the Android Project and OHA. I can tell you it might be the webkit area. Better than Mozilla wanting to talk to me about having Fennec on Android as it is more realistic about what can be accomplished. It is very exciting.
![Reblog this post [with Zemanta]](https://i0.wp.com/img.zemanta.com/reblog_e.png)
I am in the final phases of refactoring the reports look for AndCooper and the 0.1 release of AndCooper should be shortly. Looks like this before the final adjustments such as company logo, reports.css, and etc:
Plus, the reports should have a similar look to them to guide the developer as easy to read analysis reports. For example, adding summary explanations to some reports telling the viewer how to use the report.
I have choose to use a Continuous Integration Server as the platform to allow me to extend it beyond the first few versions to enable the easy on-the-fly-analysis. Basically, two modes. One mode allows the AndCoooper tool to run as a JavaBuilder in your IDE. The other mode allows you to run AndCooper in the Hudson Continuous Integration Server.
Last year, 2008 or 2007, I had the idea of integrating Tiddlywiki with Eclipse to somewhat drive the build/development process. However, for whatever reason that is just too brittle of a combination. But, picture this an Eclipse Continuous Integration Server.
You start with e4 project as the front end combined with RCP. Than of course part of e4 extends towards the backend but also inclduing say jetty, Sqlite, Eclipse BiRT, and etc. Than you take the API Modular principes of the Glean project and move that form in pure ANT to say groovy. enable the Dashboards as Groovy/grails integrated with e4. It would be aprefect test of e4.
Now for the engineering part, how does one talk Motorola into doing a Mobile Application version that targets an Eclipse Continuous Integration Server for Android developers? Damn it I want one.
When I started developing AndCooper I certainly did not intend to build a continuous integration server. But, along the way it seemed that Android Application development might need one. Not in the sense that it attempts to solve all problems but problems that are specific to Android Application Development.
What does a mini-continuous integration server look like? Its very small in Ant build script size and made to act as a Java Builder within modern IDE tools to get that incrmental set of builds as the developer is coding and thus generate code analysis reports as the develpoer is developing code. The analysis is specifically adjusted to pertain to Android developer challgnes, for example a new set of PMD rules beyond the PMD provided ruleset for Android, such as a rule checking for services leaks in code.
On the ease of code analaysis report use and etc, a web dash board to view reports and eventually BiRT functionalities to query analysis data. The mini-continuous integration server for Android application development looks different in that there is no server really deploy just drop it in yoru project folder and point the IDE JavaBuilder to use the build script, its just that simple.
As I finish version 0.1 over the weekend I am wondering how AndCooper will be received by Google, OHA members such as Motorola and etc as having a mini-continuous integration server for Android application development is kind of a new concept. And having support for javascript analysis for webview Android applications is a even neweer concept. Its a trail that no-one has trail-blazed before.
SAP has developed a memory porfiler for java applications that takes a java memory dump, a hprof file a heap dump, and analyses that data both visually and otherwise to allow us to do queries of that data to analyze trends and change code. Earier this year they had open sourced this technology and donated it to the Eclipse Project as the sub-project called Eclipse MAT(Memory Analyzer Technology). A the same time the Android Project started working on a converter that converted Dalvik heap dump data to the hprof file format.
Several bloggers have instructions in how to use it in Android SDK 1.5( Such as here and here), the caveat being that the multiple-processes data is not yet converted to hprof format, I would imagine that would be completed in time for ANdroid SDK 2.0.
What you may have noticed that the profiling tools for Android are becoming Eclipse enabled. There is also a profiling data converter to take the traces.txt data and allow you to analyze that data using Eclipse TPTP. Notice tha the underlying data tool engine for both projects is Eclipse BiRT. That will become important in integrating with an Android Application Build System.
MobileBytes 