Here is an example of creating an activity and then performing a simple operation using a bean to load data:
@EActivity(R.layout.main)
@OptionsMenu(R.menu.main_menu) @Fullscreen public class MainActivity extends Activity { @Bean(MyAPIImpl.class) MyAPI mAPI; @AfterInject void loadData() { mAPI.getData(); } @Click(R.id.startButton) void startClicked() { NextActivity_.intent(this).start(); } }
So what you'll notice in the code is that it's very clear what this Activity is doing, no need to scroll through lists of Views being initialized and endless availability checks. Also, the click listeners that are normally splattered throughout the code is contained in a simple method with the @Click annotation. Here you just define the resource id of the item that you would like to associate with the click event and then a method to handle the click.
Furthermore, this Activity references a view in the R.layout.main layout file, without having to define the typical onCreate() method. It also defines which menu file it's going to use with the @OptionsMenu annotation. Pretty simple, right? In a future post I will show additional examples of how using AndroidAnnotations makes your code more maintainable. Have you tried this library yet? If so, please let me know what you think. Curious to find out what others think of it.
No comments:
Post a Comment