Unknown user at 22:50, 11 April 2022

2022-04-11T22:50:46Z

← Older revision		Revision as of 22:50, 11 April 2022
Line 5:		Line 5:
	EventBus is an open-source library for Android using the publisher/subscriber pattern for loose coupling. EventBus enables central communication to decoupled classes with just a few lines of code — simplifying the code, removing dependencies, and speeding up app development.When we set one event as publisher and subscribe some classes or fragment for that event.So when the publisher is posting something EventBus automatically invoke subscribers.		EventBus is an open-source library for Android using the publisher/subscriber pattern for loose coupling. EventBus enables central communication to decoupled classes with just a few lines of code — simplifying the code, removing dependencies, and speeding up app development.When we set one event as publisher and subscribe some classes or fragment for that event.So when the publisher is posting something EventBus automatically invoke subscribers.

	~~There is 3 steps in EventBus~~

	1~~. Define events~~		==The EventBus API is as easy as 1-2-3==

	public ~~static~~ class MessageEvent { ~~/* Additional fields if needed */~~		Before we get started make sure to add EventBus as a dependency to your project.

			===Step 1: Define events===

			Events are POJO (plain old Java object) without any specific requirements.

			public class MessageEvent {

			public final String message;

			public MessageEvent(String message) {
			this.message = message;
			}
	}		}

	2. Prepare subscribers~~: Declare and annotate your subscribing~~ method~~, optionally specify~~ a thread ~~mode~~		===Step 2: Prepare subscribers===

			Subscribers implement event handling methods (also called “subscriber methods”) that will be called when an event is posted. These are defined with the @Subscribe annotation.
			Note that with EventBus 3 the method name can be chosen freely (no naming conventions like in EventBus 2).

			// This method will be called when a MessageEvent is posted (in the UI thread for Toast)

	@Subscribe(threadMode = ThreadMode.MAIN)		@Subscribe(threadMode = ThreadMode.MAIN)
	public void onMessageEvent(MessageEvent event) {/~~* Do something *~~/};		public void onMessageEvent(MessageEvent event) {
			Toast.makeText(getActivity(), event.message, Toast.LENGTH_SHORT).show();
			}

			// This method will be called when a SomeOtherEvent is posted

			@Subscribe
			public void handleSomethingElse(SomeOtherEvent event) {
			doSomethingWith(event);
			}

	~~Register~~ and unregister ~~your subscriber~~. ~~For example on~~ Android, activities and fragments should usually register according to their life cycle		Subscribers also need to register themselves to and unregister from the bus. Only while subscribers are registered, they will receive events. In Android, in activities and fragments you should usually register according to their life cycle. For most cases onStart/onStop works fine:

	@Override		@Override
	public void onStart() {		public void onStart() {
	super.onStart();		super.onStart();
	EventBus.getDefault().register(this);		EventBus.getDefault().register(this);
	}		}

	@Override		@Override
	public void onStop() {		public void onStop() {
	~~super.onStop();~~		EventBus.getDefault().unregister(this);
	EventBus.getDefault().unregister(this);		super.onStop();
	}		}

	3. Post events		===Step 3: Post events===

	~~EventBus~~.~~getDefault()~~.~~post(new MessageEvent());~~		Post an event from any part of your code. All currently registered subscribers matching the event type will receive it.

	~~Here I added basically how to added~~ EventBus ~~to your project~~.~~Now we can discuss how to effective when both Retrofit and EventBus come to play together.~~		EventBus.getDefault().post(new MessageEvent("Hello everyone!"));
	When it’s come to API call handling we can use two OnEvent methods to complete the related action.one OnEvent method uses to send the Request parameters to Retrofit Request method and other OnEvent method use to get API response to the related activity of fragment.
	~~So need to worry about threads and other stuffs whenever the API call finish EventBus fire the related activities of fragments using OnEvent function.~~
	~~Bellow I added a example which I selected from this blog.So you can get far better idea about what was discussed above paragraph~~.


Line 43:		Line 66:
	==Referensi==		==Referensi==

			* https://greenrobot.org/eventbus/documentation/how-to-get-started/
	* https://medium.com/@rajithaperera_81165/android-how-to-use-eventbus-with-retrofit-e0c6ac85654e		* https://medium.com/@rajithaperera_81165/android-how-to-use-eventbus-with-retrofit-e0c6ac85654e

Unknown user: Created page with "I think to share some facts with you which I collected from my current android project.I have to handle lots of API callings while developing that app.So when we come to netwo..."

2022-04-11T22:45:58Z

Created page with "I think to share some facts with you which I collected from my current android project.I have to handle lots of API callings while developing that app.So when we come to netwo..."

New page

I think to share some facts with you which I collected from my current android project.I have to handle lots of API callings while developing that app.So when we come to networking part of our Android app we can not neglect Retrofit because that has a capability to handle API callings smoothly without affecting UI thread.But today I’m not going to talk about Retrofit instead of that worth to discuss Relation between EventBus with Retrofit.

==Actually, what is the EventBus?==

EventBus is an open-source library for Android using the publisher/subscriber pattern for loose coupling. EventBus enables central communication to decoupled classes with just a few lines of code — simplifying the code, removing dependencies, and speeding up app development.When we set one event as publisher and subscribe some classes or fragment for that event.So when the publisher is posting something EventBus automatically invoke subscribers.

There is 3 steps in EventBus

1. Define events

public static class MessageEvent { /* Additional fields if needed */
}

2. Prepare subscribers: Declare and annotate your subscribing method, optionally specify a thread mode

@Subscribe(threadMode = ThreadMode.MAIN)
public void onMessageEvent(MessageEvent event) {/* Do something */};

Register and unregister your subscriber. For example on Android, activities and fragments should usually register according to their life cycle

@Override
public void onStart() {
super.onStart();
EventBus.getDefault().register(this);
}
@Override
public void onStop() {
super.onStop();
EventBus.getDefault().unregister(this);
}

3. Post events

EventBus.getDefault().post(new MessageEvent());

Here I added basically how to added EventBus to your project.Now we can discuss how to effective when both Retrofit and EventBus come to play together.
When it’s come to API call handling we can use two OnEvent methods to complete the related action.one OnEvent method uses to send the Request parameters to Retrofit Request method and other OnEvent method use to get API response to the related activity of fragment.
So need to worry about threads and other stuffs whenever the API call finish EventBus fire the related activities of fragments using OnEvent function.
Bellow I added a example which I selected from this blog.So you can get far better idea about what was discussed above paragraph.

==Referensi==

* https://medium.com/@rajithaperera_81165/android-how-to-use-eventbus-with-retrofit-e0c6ac85654e

MQTT: Android EventBus - Revision history

Unknown user at 22:50, 11 April 2022

Unknown user: Created page with "I think to share some facts with you which I collected from my current android project.I have to handle lots of API callings while developing that app.So when we come to netwo..."