Month: January 2015

Theme “Leaves” added to “KDE – Pairs”

“Leaves” is the newest theme I created for KDE-Pairs as a part of my ongoing project ‘Theme Designing of Pairs’. This is done under the guidance of my mentor “Heena Mahour” who initially gave the idea about leaf structures. This will only work in 3 game modes namely, pairs, relations and logic.  You can download the theme from here.

pairs-leaves-pairs pairs-leaves-logic pairs-leaves-relation

Advertisements

Theme ‘Stationery’ added to ‘KDE – Pairs’

As a part of my ongoing project “Adding new themes for KDE Pairs game”, a new theme ‘Stationery’ is added. The motivation behind selecting the particular theme lies on its simplicity. Stationery objects are very much familiar with pre-school children rather than other objects. Hence these stationery items can be used in the ‘Pairs’ game to develop their logical skills, rather than worrying about their familiarity with the domain.

The stationery objects I have used for this are; book, pen, pencil, paint brush, paint tube, ruler and scissor. The theme can associate four of the six game modes. They are pairs, relations, logic and words. Few screen shots of the theme will be as follows;

In 'Pairs' game mode

In ‘Pairs’ game mode

In 'Logic' game mode

In ‘Logic’ game mode

In 'Relation' game mode

In ‘Relation’ game mode

In 'Words' game mode

In ‘Words’ game mode

This theme can be downloaded from here.

Devise vs. authentication from the scratch

One of the main advantages in Ruby on Rails is as I mentioned in my earlier blog post, is not re inventing the wheel. For example for the authentication in a web app, you can use devise gem and have the full functionality of it in a few seconds. So what is the use of doing authentication from the scratch?

If you are a new developer to Ruby on Rails, I highly suggest that coding the authentication from the scratch. RailsCast have a very good tutorial on this.  By doing this you can have a full understanding of how ruby on rails works. If you are a seasoned developer and know enough you can use devise which also has lots of features.

In my project for Learn IT, Girl I first did the authentication part with devise. Then I got that I don’t really get a full understanding and then I followed the above tutorial and learned to make it from the scratch. It gives me the flexibility to change the system as I wish and most of all given me a good understanding on how Ruby on Rails works.

Why RoR?

For about a month now I am learning Ruby on Rails and doing a web application as a part of the Learn IT, Girl mentoring program. When I tell this to my friends almost everyone asked why ruby? Even it has been considered a cool geeky programming language and web development framework in the world in general, it has not been a great hit in Sri Lanka. (I wonder why? But may be because none of the major software companies in Sri Lanka is using Ruby or Rails as far as I know.)

Rails is a web application development framework which follows MVC (Model, View, Controller) architecture. The thing I love most about RoR is that you don’t have to reinvent the wheel. RoR is a full stack framework that covers both front end and back end design while taking care of the boring stuff you have to do with every app like user authentication. In RoR you can simple use devise gem and have an up and running user authentication system for your application in few minutes.

When considering the statistics Ruby developers have high demand and high salaries. Most popular applications like Amazon, BBC, Scribd are built with or have some component of Ruby along with it. So if you have a free time or willing to learn a new language or framework, select RoR. It will be useful in the future.