Langsung ke konten utama

[DIY] Using Log On Android ~ DroidUMM

Sometimes to find the error in android using logcat not enough for us to give an error or debugging information we want. Therefore, we can use the Log class to describe the error or debug what we want.
private static final String TAG = "Sending Email";
Code above is used to describe the TAG Error that we use. Suppose that tag to describe the "Sending Email" and you can create a new TAG variable according to your needs


code above is used to describe the TAG Error that we use. Suppose that tag to describe the "Sending Email" and you can create a new TAG variable according to your needs.

Now you add the log information in that class with the following code

Log.i (TAG, "Success");

Log is a class for describing error. "i" is used error in the show. There are some errors that we can describe.

ASSERT
Priority constant for the println method.
DEBUG
Priority constant for the println method; use Log.d.
ERROR
Priority constant for the println method; use Log.e.
INFO
Priority constant for the println method; use Log.i.
VERBOSE
Priority constant for the println method; use Log.v.
WARN
Priority constant for the println method; use Log.w.

Komentar

Postingan populer dari blog ini

WhatsAppSniffer Hack WhatsApp

Who uses WhatsApp Messenger? From The look of the  Play Store listing , a  damn lot  of people. Considering it's so popular, it's probably a pretty secure app, right? Think again. WhatsApp actually sends all chats in  plaintext , so anyone on the same Wi-Fi network can easily pull your entire conversation - including pictures and videos - straight out of the air. And now, that process is even easier than ever thanks to a new app called  WhatsAppSniffer . It's basically just a packet sniffer, but it makes the process of pulling WhatsApp chats out of the sky stupid-easy, and that's never a good thing. You might as well just shout your private conversations across the room.

[Concept] Model View Present (MVP) Pattern for Architecture Android~ DroidUMM

 Model-View-Presenter (MVP) is an architecture pattern for the presentation layer of software applications. The pattern was originally developed at Taligent in 1990s and first was implemented in C++ and Java. In MVP, the View and the Model are neatly separated and the View exposes a contract through which the Presenter access the portion of View that is dependent on the rest of the system.  [Next Article Implement MVP on Android] The Model is the component which preserves data, state and business logic; it just exposes a group of service interfaces to Presenter and hides the internal details. The View is the user interface, it receives user’s action and contract to Presenter to achieve user’s need, and then the View responds user by result information. The Presenter sits in between the View and the Model; it receives input from the View and passes commands down to the Model. It then gets result and updates the View trough the contracted View interface.

[App] Papyrus Android Note

As part of my job, I spend a lot of time in meetings with potential customers, and taking lots and lots of hand-written notes. My problem has been that I’ve had to use a physical book and never had an easy way of taking electronic hand-written notes. Until now.