Fixes part of #2003: Modified the use of space_20

[Arjupta]

Explanation

Fixes part of #2003
This commit removes the use of dimension space_20 with the dimensions of use-case specific names.

Checklist

• The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
• The PR follows the style guide.
• The PR does not contain any unnecessary auto-generated code from Android Studio.
• The PR is made from a branch that's not called "develop".
• The PR is made from a branch that is up-to-date with "develop".
• The PR's branch is based on "develop" and not on any other branch.
• The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

[rt4914]

@Arjupta considering that you are now a collaborator. Please make sure that you Keep the Assignnees section up-to-date as per these guidelines.
https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section

[rt4914]

@Arjupta considering that you are now a collaborator. Please make sure that you Keep the Assignnees section up-to-date as per these guidelines.
https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section

[rt4914]

Also, @Arjupta You can work on other issues meanwhile we start discussion about the the naming on this PR with other team mates.

@BenHenning Can you have a look at the naming convention for dimensions and leave your thoughts?

[Arjupta]

@Arjupta considering that you are now a collaborator. Please make sure that you Keep the Assignnees section up-to-date as per these guidelines.
https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section

Okay, I will follow them from now on. Mistakenly closed this PR while using the Github Mobile App

[BenHenning]

Thanks @Arjupta & @rt4914. I find these much clearer. Left some comments on the specific naming.

[aggarwalpulkit596]

@Arjupta could you assign me as well for all of your future PR's.
Thanks

[Arjupta]

@Arjupta could you assign me as well for all of your future PR's.
Thanks

Okay, I will take care of that.

[Arjupta]

@BenHenning PTAL

[BenHenning]

The names LGTM. Thanks!

[rt4914]

@Arjupta One nit and rest all is good.

[Arjupta]

@rt4914 I think this is ready to merge, shall I proceed with PR related to other dimensions now?

[rt4914]

LGTM, thanks.

You can start creating other parts but make sure they are still smaller PRs as it will create less merge conflicts and fast approvals.

Roughly I think you can change nearly 10-15 files for such issues in single PR.

[Arjupta]

LGTM, thanks.

You can start creating other parts but make sure they are still smaller PRs as it will create less merge conflicts and fast approvals.

Roughly I think you can change nearly 10-15 files for such issues in single PR.

Sure will take care of that. Can I know whether I should ask for a review on this issue from you or Ben?

Thanks

[rt4914]

LGTM, thanks.
You can start creating other parts but make sure they are still smaller PRs as it will create less merge conflicts and fast approvals.
Roughly I think you can change nearly 10-15 files for such issues in single PR.

Sure will take care of that. Can I know whether I should ask for a review on this issue from you or Ben?

Thanks

You can ask me and if I will have any doubt I will add @BenHenning too.