Moving all hardcoded strings to strings.xml

[opticod]

You should be moving all the existing necessary hardcoded strings to strings.xml.
Anyone want to help me out here?

[octacode]

I would like to work on it.

[codingblazer]

If still need help, I will be happy to help.

[rijuldhir]

I can help too.

[codingblazer]

@opticod I think there are too many lint issues also. We can add those too if you feel so.

[opticod]

@octacode @codingblazer @rijuldhir , Cool, then lets distribute these works among us all.
@octacode Can you fix all hard coded strings in first 10 folders(alphabetically sorted order)? viz. activity to matchtemplate folder.
@rijuldhir Can you fix all hard coded strings in last 7 folders(alphabetically sorted order)? viz. model to views folder. + ToolkitApplication + all files in res folder if any.
@codingblazer Can you fix lint issues except the "HARDCODED String" issue ?

Guys let me know, if anyone wants any modification.

[octacode]

Awesome @opticod. ^^

[octacode]

@opticod. We only need to hard code those strings which we have to display as a message to the user. Right?

[jainkuniya]

If still there is any unassigned issue, let me know I will be happy to work on that.

[opticod]

@octacode Yes, and rest wherever possible but not all declare them as constant globally.

[opticod]

@vishwesh3 Cool, Can you replace all hardcoded dimes into dimen.xml ?

[opticod]

Guys when replacing them please minimise the redundancy of newly added strings or dimen, by this what i mean is ...if there already an existing entry of it then better use that rather than adding one more entry in xml file.

And make noun as non translatable.

[jainkuniya]

Yes.

[opticod]

I realised that, most of you are creating minute mistakes while making PRs but they can be critical in production, so will not merge any big change before DEC-2016 release.

[sm86]

Is the issue closed? Can I help in any way

[opticod]

@sm86, this issues is already assigned.