How to create your own background for Google Docs

As i was making documents to share with my students using Google Docs, i wanted to create a background for all these documents. Hence i had to do the necessary research to achieve this. I would like to share it with you which may help the Google docs user.

Step I:

Load the background image to the google drive.

Step II:

Create a URL for this image. To do that first go to the sharing option of that image in google docs and make it publicly available. Then open the website

http://www.gdurl.com/ and copy the sharable link to this site to create a permalink.

Step III:

Open the website https://chrome.google.com/webstore/category/apps in chrome browser and search for Stylish extension.



And install this extension. It will add an icon on the right side of the address bar.

Step IV:

• Open any google docs and click on the stylish icon.

• Click the first link Find more styles for this site

• You may search for Linen Background for Google Docs and click the link

• Now open your Google docs and you will see a nice background

• Click on the Stylish icon on the right hand side of the address bar and this time click “Manage installed styles”

• Then in the right pane click the button edit.

• Replace the background url with the permlink that you have got in step II. It will look something like the following

#docs-editor {

background: url(http://gdurl.com/lQ3I) !important;

}

.docs-title-inner {font-family: Georgia !important;}

.docs-menubar {height:28px !important;}

Step V:

Refresh the open google docs and enjoy the background you have just created.

The Designing of a Software System from scratch with the help of OOAD & UML - A Restaurant System

The story of a dream chaser

Here is my story of the journey to become an able software engineer...

Watch...

Generic Asynchronous Task for HTTP connection in Android

Structural Relationship between Content Resolver and Content Provider - an example of Proxy Design Pattern...

As i was digging into the source code of Content Provider and Content Resolver, i found a nice structural relationship among the two and it closely resembles the Proxy Pattern of the GoF book. We need Proxy Pattern whenever there is a need of a sophisticated reference to an object other than the simple pointer.

The class diagram of the Proxy Pattern is something similar to the following:

What it actually does is that it adds a level of indirection when accessing an object. Whenever a client needs to interact with an object of a RealSubject, it instead interacts with a Proxy of it. The proxy forwards the request to the RealSubject.

Now let us dig into the source code of Content Resolver and Content Provider to understand how it resembles the Proxy Pattern. The Content Provider offers the client of it all of the CRUD (create, read, update & delete) functionalities. Internally what it does it forwards these functionalities to the Content Provider. There is an one to one mapping between the CRUD functions of the Content Resolver with the Content Providers. A simplistic version of the structural relationship between the Content Resolver and the Content Provider can be depicted as follows.

Whenever the client calls any of the above functions on the ContentResolver, it just gets a reference to the appropriate Content Provider by the function called aquireProvider and then delegates that function to that of the ContentProvider. In each of these CRUD functions, the ContentResolver also manages the lifecycle of the ContentProvider it acquires through a function called releaseProvider.

Thus we can say that to a client, the ContentResolver works as a proxy of ContentProviders.

Implementation of a State machine for a long running background task in an Android service

Implementation of Half Sync Half Async design pattern in Android Asynctask...