StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9244680
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-11T22:42:16.567
FavoriteCount
0
LastActivityDate
2012-02-11T22:42:16.567
LastEditDate
LastEditorUserId
0
OwnerUserId
115145
ParentId
9244583
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> I've been researching ways to store global settings for my Android application and so far the best way seems to extend the Application class and store the shared data inside it, as described here. </blockquote> Except that you're not doing that. <blockquote> I've discovered that instead of using (CustomApplicationClass)getApplicationContext().getSomething() i can do the same thing by referencing directly to the static method inside the class like this: CustomApplicationClass.getSomething() and both ways work just fine. </blockquote> Of course. You could just as easily had <code>CustomApplicationClass</code> extend <code>Object</code>, then executed <code>CustomApplicationClass.getSomething()</code>. You are gaining nothing by your current approach versus just using an ordinary singleton pattern in Java, and you are losing flexibility, as an application can only have one custom subclass of <code>Application</code>. <blockquote> Is the second way safe to use, or is it inadvisable? </blockquote> The first way is pointless, since your data member and methods are static. Either: <ol> <li>Make your stuff in <code>CustomApplicationClass</code> not be <code>static</code>, and then use <code>getApplicationContext()</code>.</li> <li>Refactor <code>CustomApplicationClass</code> to not extend <code>Application</code>, and then use the static data member and/or accessor methods, or switch more formally to <a href="http://www.techrepublic.com/blog/programming-and-development/using-the-singleton-pattern-in-java/449" rel="nofollow">the Java singleton pattern</a>.</li> </ol> Personally, I would go with option #2.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing getApplicationContext() vs. referencing to custom Application class in Android
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCommonsWare
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing getApplicationContext() vs. referencing to custom Application class in Android
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.