Hacked Google Calender addon for Thunderbird

I was trying to get the add-on 'Provider for Google Calendar' to work reading steps from , but was not able to do so since the option for Google Calender setup as shown in was not coming up. So finally after around 2 hrs of fight looking for help at FAQ, IRC, I finally got the hit and hacked the config file of the extension a bit and was able to do it all.

1. Checked the presence of the 'install.rdf' in the /home/sawrub/.thunderbird/xxxxxxxx.default/extensions/ directory that contained the data corresponding to the calender sync like a snip from it read liek "The Original Code is Google Calendar Provider code"
grep -i google \{xx12xx12x1x-5fdc-40c2-873c-223b8a6925cc\}/install.rdf
2. Once the file was there, read through for the dependencies and there the problem was.I was ok with all other things mentioned in the config file except this.

<em:requires>
      <Description>
        <!-- Lightning (also Sunbird via extension stub) -->
        <em:id>{e2fda1a4-762b-4020-b5ad-a41df1933103}</em:id>
        <em:minVersion>1.0b1</em:minVersion>
        <em:maxVersion>1.0b1</em:maxVersion>
      </Description>
    </em:requires>


3. It was found the Lightning version that I have is 1.0b2pre and the add-on was just good enough to support Lightning to version 1.0b1 as said in '1.0b1' so i just thought of playing around.I edited the line to '1.0b3' saved the file and restarted the Thunderbird. I hope you understand why i did it to 1.0b3.

4. Followed the steps mention in the blog, and now the option for the Google Calender was with me, rest was a child's play.

Hope this helps some one. Cheers to the open source.

Comments

Post a Comment

Popular posts from this blog

Chrome @ Fedora

Image
Installing Chromium on Fedora isn't really all that much harder than it is on a Debian-based system. But with Fedora you have a couple of different options. You can either install from command line or you can install using the yum package management too. The benefit of installing via yum is that you will be able to update Either way the installation is simple. Let's take a look at the Yum. You have to follow the following steps: Open your vi editor and enter the gain 'root' access. Create the '/etc/yum.repos.d/chromium.repo' file. Add the following contents to the file: [chromium] name=Chromium Test Packages baseurl=http://spot.fedorapeople.org/chromium/F11/ enabled=1 gpgcheck=0 Save the file. Update the yum database using : 'yum update' Finally fire the install : 'yum install chromium -y' Doing this all will install Chromium on your fedora 11 system.Which can be accessed from under Applications -> Internet -> Chromium Web Browser The
Read more

Dock the Appications

Image
The day can be called successful one again as found a application that works with any kind of window managers having being tested with Gnome, KDE, XFCE as mentioned by the developer/s. So considered to give a try. 1. Installation was quick as its just a 95k package. # yum install -y kdocker.i586 2. Using it to Dock. The Docker application was found under Applications > Accessories > KDocker. Selecting the Docker turned my pointer into a kind of stock gun target. Decided to dock thunderbird, hence clicked the mouse on the application window, and it was done. 3. The icon looked a little bad but considering the work done can be acceptable.Here is the screen shot of how the docked thunderbird looked like. 4. Once docked the application can be undocked  by a single click on the docked icon of the application. 5. As seen in the above screen shot there is a terminal also docked along with the thunderbird. Great thanks to the development team.A small info about the appl
Read more

Bash Scripting Cookies

- Passing arguments to a Bash script. `basename $0` in the script will list the name of the script without the path. `dirname $0` in the script will list the absolute path of the script without the name. `$0` will list the full path 'URI' of the script. `$#` will list the count of the arguments passed to the script. `$*` will be listing all the arguments passed to the script. `$1` will be listing the first argument passed to the script. - If conditional statements Condition Meaning [ -a FILE ] True if FILE exists. [ -b FILE ] True if FILE exists and is a block-special file. [ -c FILE ] True if FILE exists and is a character-special file. [ -d FILE ] True if FILE exists and is a directory. [ -e FILE ] True if FILE exists. [ -f FILE ] True if FILE exists and is a regular file. [ -g FILE ] True if FILE exists and its SGID bit is set. [ -h FILE ] True if FILE exists and is a symbolic link. [ -k FILE ] True if FILE exists and its sticky bit is s
Read more