#include "week5"

This week was continuous commits and fixing the issues. Most of the part can be found here . It's the pull request which I gave and Diaspora people aided me a lot with the issues. They wanted me to change the methodology because it would create a lot of complication and confusion in the tags following path. We even came to final conclusion that adding a filter on top of it may disturb the existing tags functionality. However the code written for Language selection and detection was considered useful and they want me to build everything on top of it. Fetching any variables from publisher page to status message controllers is still ongoing and seems pretty tough. Adding a normal select dropdown list makes the css look like

Dropdown
List

It messes up the front end even after trying to fix the CSS and doesn't get the work done. I am finally trying to get it by adding some javascript. They even asked me to do the Language selection while signing up totally client side. I worked on it and managed to get it but we're still deciding on how to store it in back-end as the plan of storing it as followed tags has been crossed off. 

#include "week4"

This week was mostly about the backbone.js part for the implementation of translation and a dropdown list for the modification of language after posting a post.

Mainly a couple of changes have to be made to this file. Still the backbone part is new to me and the I need to study it for some time to implement. Besides this I am finalizing the UI for this and authorization about who can change the language. Also I am in discussion about how to implement the translation part.  Although the UI for this part will be very trivial, back-end storage will be somewhat complicated and take much time.

I am also working on the css part for language display. I had some discussion with diaspora people regarding the review of what I have done so far. They asked me to send a pull request for a detailed discussion base. Currently , they're reviewing the code and said they will get back to me with a solution. 

#include "week2 && week3"

Last week  I had some work progress but most of them were left  incomplete and I had to solve the bugs to bring them to this stag.

Testing WhatLanguage Gem :

As I mentioned earlier it turned out that I had to use language field in status method so I planned on going ahead and adding another line in status message itself to see if this gem works.
After including the gem in Gemfile and using it for detection it works juts fine. Mostly the detection goes wrong for normal English sentences. However we have option for manual tagging to control it.


Tag while post feature : 

I have changed the view for the main stream .

I have added another field called Language and selected "Auto Tag" by default so that if without changing it if a user posts, it uses the gem to autodetect language. I tried using some standard haml dropdowns but they din't work on this view so I had to use their standards to not make the view go berserk. Currently I am working on fetching the selected field to status_messages_controller.rb. 


Sign_up page modifications : 

As mentioned in the proposal I was about to make changes to the sign_up page to add preferred languages.

I added the field to do so. Due to some errors in Javascript the autocomplete feature is not working for it . Currently I am having discussions about it in Diaspora-dev and with my mentor. Will come up with an update soon .


PS: I have updated my git repo . You can have a look at the commit history or pull the latest one and try to have a look at the added features. :) 

#include "week1"

This week was mostly about getting acquainted with codebase and reflecting small changes while working on it.

Initially I wanted to add a column "language" to the existing posts model. I tried it many ways but failed initially. By declaring it as "xml_attr" worked but then I failed to assign value like "english" etc. due to validations . Then skipped validations by using .update_attribute and then it worked. Turns out that only existing attribute types from existing model can be declared.

This might work now but will certainly create issues in future as we don't need language as a xml attribute, so I didn't reflect any changes and searching for alternatives.

I decided to proceed similarly as the existing "/tags" field. Will add relevant js files and controllers in coming weeks.

I finally found out the template being used to display stream and comments. It's a format I am not very used to so still exploring how to exactly reflect changes.

I have created a new branch language_filter. I have added the model, spec and migration for language. One can either add model and use rake db:migrate or the existing application and run "rake db:seed" (this part should be done in both the cases) to add all the entries to the language table. Changes can be seen by opening the branch.

#Begin

I have been selected for the project Language Filter for Diaspora by SMC . I am super excited about this and have been exploring the codebase and their formats.

Hopefully GSOC with Swathanthra Malayam Computing is going to be fun. I am mentored by Ershad K. and Praveen. Short description about my project can be found here .

To start with there were many views and it was really hard to find relevant ones so I'll be using RailsPanel to find relevant controllers and views and use them accordingly.

I have already implemented emoticons support for diaspora so I am slightly aware of their coding standards and will try my level best to keep up with it.