On Mon, Dec 27, 2010 at 7:12 PM, Kevin Gaudin <[email protected]> wrote: > All comments and new ideas about ACRA are welcome !
You have one ACRA feature that, IMHO, is huge: the ability to post the errors somewhere other than a Google Spreadsheet via the formUri parameter. However, the POSTed data is keyed based on Google Spreadsheet rules, making it a bit awkward for anyone else. It'd be cool if the error-to-Map munging could be pluggable, or at least have Google Spreadsheet versus less-cryptic key sets, just to make alternative back-ends a bit more maintainable. Even better would make the whole error submission process pluggable, with your Google Spreadsheet implementation being the stock implementation. I could easily see options to: -- log it to a custom Web service (e.g., a tiny Ruby/Sinatra Web app) -- log it to a hosted MongoDB or CouchDB server in JSON format -- multiple log handlers (e.g., log to Spreadsheet plus send a tweet to help let the developer know to go check the sheet) -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
