<EditText
    android:id="@+id/editText"
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:layout_alignParentStart="true"
    android:layout_alignParentTop="true"
    android:layout_marginStart="32dp"
    android:layout_marginTop="23dp"
    android:ems="10"
    android:inputType="textPersonName"
    android:text="Name" />

<Button
    android:id="@+id/button2"
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:layout_alignEnd="@+id/editText"
    android:layout_below="@+id/editText"
    android:layout_marginTop="16dp"
    android:text="Button" />

    android:layout_alignEnd="@id/editText"
    android:layout_below="@id/editText"
    

@Override
public void onBindViewHolder(ViewHolder holder, final int position) {
    final ContentItem content = values.get(position);
    holder.txtName.setText(content.getName());
    holder.txtHeader.setText(content.getDescription());
    holder.txtFooter.setText("Footer text is here!");

    holder.setIsRecyclable(false);

    vAdapter = new VariantAdapter(content.getVariants());
    vRecyclerView.setAdapter(vAdapter);
}

public class ViewHolder extends RecyclerView.ViewHolder {
    // ... codes redacted

    private RecyclerView variantRecyclerView;

    public ViewHolder(View v) {
        super(v);
        // ... codes redacted
        variantRecyclerView = (RecyclerView) v.findViewById(R.id.variant_recycler_view);
    }
}

    @Override
    public void onBindViewHolder(ViewHolder holder, final int position) {
        // ... codes redacted
        variantLayoutManager = new LinearLayoutManager(holder.view.getContext());
        holder.variantRecyclerView.setLayoutManager(variantLayoutManager);
        variantAdapter = new VariantAdapter(content.getVariants());
        holder.variantRecyclerView.setAdapter(variantAdapter);
    }

Just click next and accept all the default option. Just make sure that it targets phone and tablet and MainActivity class is created by the wizard.

Add Dagger 2 dependency to gradle app module.

    
    configurations.all {
        resolutionStrategy.force 'com.google.code.findbugs:jsr305:1.3.9'
    }

compile 'com.google.dagger:dagger:2.11'
compile 'com.google.dagger:dagger-android:2.11'
compile 'com.google.dagger:dagger-android-support:2.11'
annotationProcessor 'com.google.dagger:dagger-android-processor:2.11'
annotationProcessor 'com.google.dagger:dagger-compiler:2.11'

Add quick start code to Live Templates

Use the file menu to open Settings => Editor => Live Templates

Select "user" and add a new user Live Template as per bellow image. Set Abbreviation to something easily remembered. This example use "DA" as the shortcut, so that you can type DA and press TAB key to generate the code.

Use bellow code as the template by copy and paste into Template text.

public class App extends Application implements HasActivityInjector {

    @Inject
    DispatchingAndroidInjector<Activity> dispatchingAndroidInjector;

    @Override
    public void onCreate() {
        super.onCreate();
        DaggerAppComponent.create().inject(this);
    }

    @Override
    public DispatchingAndroidInjector<Activity> activityInjector() {
        return dispatchingAndroidInjector;
    }

    //Move this interface to its own class file and do Build => Make Project
    @Component(modules = { AndroidInjectionModule.class, AppModule.class})
    public interface AppComponent extends AndroidInjector<App> {
    }

    @Module
    public abstract  class AppModule {
        @ContributesAndroidInjector
        abstract MainActivity mainActivity();
    }
}

Create App Class and Set the Manifest

Add a class that extend Application class. This can be done by right clicking the application package and use context menu to add a new Java class. Refer to bellow pictures.

Use Live Template to Add Boilerplate Codes

Open the App class so that we can add codes saved earlier as Live Template. Just delete bellow code.

public class App extends Application {
}

Type abbreviation that we set previously; in this case DA and press TAB on the keyboard. You should get the code as bellow picture.

As in above picture, blue box will popup to resolve missing import. Just press ALT + ENTER until they are all resolved.

However DaggerAppComponent (line 14 in the picture) will not resolve. Dagger has to generate DaggerAppComponent class. For this to happen we need to move AppComponent interface to its own file.

To do this cut bellow codes from your App class.

//Move this interface to its own class file and do Build => Make Project
@Component(modules = {AndroidInjectionModule.class, AppModule.class})
public interface AppComponent extends AndroidInjector<App> {
}

Create a new interface and name it AppComponent. We will not need AppComponent code generated in this file. Simply delete and paste code that we cut in above step.

Use keyboard shortcut  CTRL+F9 to make the project. After make is completed, DaggerAppComponent in App class should be successfully resolved.

Create a TestService Class and Inject it to MainActivity for testing.

Use bellow code for TestService class. Take note of the @Inject decoration usage. TestService constructor will be called when it is injected into MainActivity class.

public class TestService {

    private TestUser user;

    @Inject
    public TestService(){
        user = new TestUser();
        user.setName("Test User");
        user.setEmail("test@user.com");
    }

    public TestUser getUser() {
        return user;
    }

    public class TestUser {
        private String name;

        private String email;


        public String getName() {
            return name;
        }

        public void setName(String name) {
            this.name = name;
        }

        public String getEmail() {
            return email;
        }

        public void setEmail(String email) {
            this.email = email;
        }
    }
}

Ensure that MainActivity layout file have the following TextView widget

<TextView
    android:id="@+id/text_hello"
    android:layout_width="wrap_content"
    android:layout_height="wrap_content"
    android:text="Hello World!" />

And implement codes as in bellow picture in exact order as highlighted.

Bellow codes for copy paste.

public class MainActivity extends AppCompatActivity {

    @Inject TestService testService;

    @Override
    protected void onCreate(Bundle savedInstanceState) {

        AndroidInjection.inject(this);

        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

        TextView textHello = (TextView)findViewById(R.id.text_hello);
        if(testService != null){
            textHello.setText("SUCCESS! User is " + testService.getUser().getName() +
                    " and email is " + testService.getUser().getEmail());
        }else{
            textHello.setText("FAILURE!");
        }

    }
}

gradlew -q dependencies app:dependencies --configuration compile

To err is human, to forgive is DEVELOPER.

The Step Taken Manually

First of all desktop is no logger in the background. This is now the browser since it was the last opened window. Other editable Gimp window are also hidden by the browser window. So to get back to having Desktop as background with all edit window open will require lots of adjustment. More works when navigating through many open application at the same time.

Distraction Abounds

It is not enough to wrestle with making windows bubble up to the foreground. When ever changing background is most of the time a distraction. Only way to rid that distraction is by maximizing current edit windows. There goes the advantage of viewing multiple image at the same time. To the chagrin of the user, the maximized window does not stay on top. But covered by utility windows that function as short cut to various functions of Gimp. 

The prominent example is Tool window. But typical users will have more than one of such utility window opened. These utility windows will overlaps each other, vying for your attention! Editing large image or zooming in for detail will then become an exercise of  moving stuff out of the way. As well as clicking here and there to get the tool you need in front.

In short, the UI tends to get in your face instead of getting work done!

The Taskbar is the Tab

Not to forget the most annoying feature of Gimp. It economically and efficiently use Windows taskbar as a way to navigate between edit windows. Yes, I am talking about that Window taskbar that have Start Bar, commonly use application ico and list of currently open application. When using Gimp; all those window clutter will also clutter the taskbar! 

To be fair. Gimp was originally developed for Linux on Gnome Desktop Environment. Which have been enjoying Virtual Desktop functionality built in and by default. In such environment, Gimp works well as one can open it in a virtual desktop with its own taskbar.

Not so for Windows user. The more you love it, the more cluttersome it become. Just awesome!

The Solution

In Closing

Program Flow

• A group or student have a starting point.
• They should find a mosque as their first check point. If the mosques is not found, it is OK to go back home.
• They should run around the mosque 3 times, at every time checking in to the first check point.
• On the third round they will be given something.
• If that something is the treasure they can go home. Otherwise have to repeat again running 3 time around the mosque. Perhaps because too slow :D

• Edit E:\PostgreSQL\9.1\pg_hba.conf and set the localhost method to trust instead of md5.  Do not forget to save.
• Use the usual Windows way to reset the password of windows user account.
• Open up a command prompt and use runas to open another command prompt as postgres user.
• open up Services manager and restart postgresql service. There might be need to update the postgres user account password setting in the service property at this step.
• Now running psql will not ask any password.
• Use the following sql to set the user password

• Revert the pg_hba.conf localhost method back to md5 .
• Restart postgresql service in Services manager.

1. Edit E:\PostgreSQL\9.1\pg_hba.conf and set the localhost method to trust instead of md5. Do not forget to save.

3. Run pgAdmin and connect to the database. Note that it will not ask the password since we are in the trust mode.

4. Scroll down to look for postgres database user under Login Roles and open up the properties windows.

5. Surprisingly there is a tab named Definition that allow for password change. Do the necessary!

6. After this is done, revert back changes to pg_hba.conf file to md5 and restart the postgresql service in Services manager.

7. You should be able to connect to the database. This time using the new password!