Tasks on Eclipse ( TODO, FIX, Etc.)

I had never used Tasks on Eclipse and yesterday one workmate told me about this feature of Eclipse.

Simple, easy and handly!

One case to explain: Imagine that you want commit your changes on the server but you still have some errors in the code. You decide comments all this error but How you could remember next day where were these commented errors?

Simple, you can add a tag like  // TODO + any comment that you want   ,  and the next day, if you open the eclipse view Tasks (Windows->Show View->Tasks) you can see all these lines where you added the //TODO tag.

Simple, easy and handly!

Also, you can configurate the kind of tags that eclipse will remember for you in his Tasks View.

To setting differents tags you need open Preferences of Eclipse and take a look to the path:  General->Editors->Task Tags.

In this window you can setting new tags and also the priority.

Special Trick!!! If you want use this feature also in .xml, .css or whatever kind of files you have to activate one check box in the previous windows. The text of these check box is  "Enable searching for task tags"  and you can add in the bottom list all the files that you can want that eclipse look for new tags.


To include a task in a .xml file you have to use something like this:   <!-- //TODO Comment-->

This is all!

Modified Google Play Store Removes Country Restrictions

Some developers are working in a custom version of Google Play which allow to jump the countries restriction that we can find in the oficial google play.

I am not testing this yet but I will...

Original Font:

http://www.xda-developers.com/android/modified-google-play-store-removes-country-restrictions/

http://forum.xda-developers.com/showthread.php?t=1582422

What is Weak References? Good to know

This is the typical question that you should  respond in the last job's interview.

There are a lot references in internet about it...good luck!

http://weblogs.java.net/blog/2006/05/04/understanding-weak-references

Android Lint : new tool to detect possible errors

Android Lint is a new tool introduced in ADT 16 (and Tools 16) which scans Android project sources for potential bugs. It is available both as a command line tool, as well as integrated with Eclipse. The architecture is deliberately IDE independent so it will hopefully be integrated with other IDEs, with other build tools and with continuous integration systems as well.

Here are some examples of the types of errors that it looks for:

• Missing translations (and unused translations)
• Layout performance problems (all the issues the old layoutopt tool used to find, and more)
• Unused resources
• Inconsistent array sizes (when arrays are defined in multiple configurations)
• Accessibility and internationalization problems (hardcoded strings, missing contentDescription, etc)
• Icon problems (like missing densities, duplicate icons, wrong sizes, etc)
• Usability problems (like not specifying an input type on a text field)
• Manifest errors

and many more.

More details:  

http://tools.android.com/tips/lint