Websites

Yes, you are right. I am asking you to shift to using Twitter module instead of Twitter Block that I developed.

The reason is simple - Twitter module does a lot more than provide a Twitter block. It allows you to post directly to Twitter from your Drupal site. Just note that to use Twitter module as a Twitter block, you will need to install and activate Views and Views UI module.

It may seem like complicating things, but if you need flexibility and reliablity of a large team of Open Source enthusiasts, you should opt for the one that gets more effort put into.

You may not notice any change on my homepage sidebar, but I have shifted to using the Twitter module and it looks as my custom module with minimal change to the CSS. (I just changed the class to id supplied by the View).

Perhaps, I will write some basic documentation of what I got using the Twitter module.

This is related to the Twitter status you see on my homepage.

Update: There will be no support for Twitter Block module. Please use Twitter module instead. Read the reasoning here.

I was browsing around, when I came across Aaron's on adding Twitter to a Drupal site. Since I am in the process of redesigning my site, I was a little more aware of the closure variable and hence I commented so on his post. He nudged me on his respone through Twitter.

Thus, I created the Twitter Block module. It is quite minor and straight forward at this moment and advanced modules have already been coded. (See the modules download page over at Drupal.org).

Download module: Twitter Block

I am yet to put the license files, but it is provided under GPL. The installation is simple - just copy to your modules or sites/all/modules folder. You should get the Twitter Block menu in the admin/settings once you enable it. It lets you configure:

• Twitter User Account
• Twitter Block Title
• Disable/Enable Follow Me link
• Text of the Follow Me link

As far as the comment goes, I was able to add the Javascript references to the $closure variable. For a background, you can see from Twitter page, that putting the Javascript references near the footer increases the page load times.

Hot tip! To ensure loading of your page even in the case of twitter.com non-loading, move the two lines that start with <script type="text/javascript"... to the bottom of your page (just above </body>).

While coding this module, I took a wrong turn with the drupal_add_js() function, and after some trial and error, use the hook_footer() to get these Javascripts into the $closure variable properly.

Once you install and configure this module, you can sytle it by lathcing on to the block-twitterblock class. You can see the result of my current theming on the Twitter Block:

Credit goes to DryIcon via SmashingMagazine for providing the Twitter icon.

Finally, I got to the point where I upgraded to Drupal 6 for this website.

The regular readers might have noticed that there is a starking change in the theme. Earlier, I was using another theme, Alek 2.0. A beautiful theme, but it seemed to have problems with Drupal 6.x - or atleast with the set of modules I had installed.

Hence, I thought I would do "a quick and simple" theme myself. The result is here, and it can be called to be in a beta state - not sure if I would release it or not because the CSS is a bit messy. It turned out to be not that simple.

There are a few things I will be fixing in terms of styling the links (you can see a lot of blue and purple sprinkled around currently) which would all go monotone and be harmonized. Drupal, striving towards flexibility gives a lot of class attributes to the numerous elements and I am yet to have a full understanding of the theming architecture to do it efficiently.

I still remain impressed though - the theme as it is currently requires only one style CSS file, one tempate file (page.tpl.php) and the .info file.

Expect few more changes around here.

After almost one and a half years of writing articles and tutorials on art at KalaaLog.com, it has resulted in more than 180 blog posts at this point in time. Around 100+ of them are all tutorials.

The tutorials range on different difficulty level and different styles, apart from taking up different subjects. It can be quite a lot of them, if you are trying to focus on only one type of tutorials. Hence, I am trying to find a way to better organize these tutorials, and present them in an accessible manner.

After a recent upgrade to Wordpres, the blogging engine that powers the site, I was able to make use of the tag features and it has turned out quite well. As I explain in the post, Tutorials, Tags and more, I have basically categorized the tutorials based on their difficulty level (beginner, intermediate, advanced) and the style (vector or painting). Apart from that, I also have another tag to identify if the tutorial consists video content or not.

It is quite manegable now, and function flawlessly. But when it comes to seeking tutorials on specific subject - I am not sure how I can use tagging. The number of tags would make it too cluttered by sheer number. Moreover, art is quite subjective, and the subject matter of a particular artwork might depend from person to person.

That is when I took the effort to ritualistically tag and bundle all the tutorial links at del.icio.us - the social bookmarking site. I created a separate account for KalaaLog to be solely used for organizing the tutorials written at that site.

I now need to find a way of coaxing the readers to file these tutorials the way they want it. This way, at least for the subject matter, the community would decide how these tutorials should be organized.

It is too early to say how it will go.

For those curious, head over to KalaaLog's del.icio.us page.