Praeda & Co.

This week I completed the location selection(actually areaS selection) module for clients. This module will be used by clients for indicating their preferred locations when getting venue suggestions or seeing their friends inside these areas.

The main features of this component is that it supports multiple location adding / updating / deleting. This means clients can indicate more than one location and adjust the size of those areas whatever and whenever they want.

I plan to write a how to for handling polygons on Google Maps asap.

As a surprise, I saw that JSPs are not capable of handling multipart form data. So, I have spent some time on figuring out how to upload a file to the server using JSP/Servlet.

There are two known libraries to use to be able to handle multipart form data; Apache Commons’ FileUpload and OReilly’s COS. I have found latter easy to use. At COS, there are two approaches to handle multipart request; push and pull model. You can either use MultipartRequest class  to handle the request (push model) just like you do at a regular request (i.e. using req.getParameter()); or use MultipartParser class to do the job by iterating among request objects (pull model). › Continue reading

Last week, as a whole team we focused on the last updates on database and determined the friendship and the suggestion system functions.

Then each member tried on to patch the failures because of the changes. I focused on the comment part. Next week, I am going to try to implement turkcell support for our project.

I’ve just finished the networking part of the MuzikMekan application. Now, users are able to send friendship request to others, display them and accept or reject them. This is implemented using two database tables: Friend and FriendRequest. First table consists of user pairs who are friends in the system. If user with id=1 and id=2 are friends, Friend table include two entries as (1,2) and (2,1). This technique is used to facilitate database operations when checking friends of a user. Second table is used to keep friendship requests. If user with id=3 asks for friendship to user with id=4, an entry with columns (3,4) will be exists in the FriendRequest table.

This week, we needed to make a huge database refinement for our system. After modifications, system can now achieve all features that is intended.

One of these features was Tag Cloud. Before this week, our tags had no importance values so they are all treated equally. But now, thanks to database modifications, I have implemented a Tag Cloud logic for tags. I used jquery tagcloud to represent the information.

Also, our sign-up system had still some issues that are needed to be fixed. And I decided that it will be easier to re-implement it than try to bug-fix, since we have some flow control modifications as well. So, I have implemented sign-up again. Hopefully next week, I will finish EditProfile, EditNetworkAccounts and EditVenue features.

This week I have integrated a star rating widget into our project that is a plugin of jquery. I have integrated it into 2 screen. One is comment venue screen that we get the rating for a venue from the user and the another one is venue profile screen that we monitors the average rating of a venue.

You can get the plugin and its documentation by following:
http://www.fyneworks.com/jquery/star-rating

Moreover we, as all of the group members, did a meeting and we have adjusted database that can handle our new plans. And also we have decided into detailed suggestion system. Next week I am going to work on the suggestion algorithm

I have been working on search feature of MuzikMekan for about two weeks now. Last week I have added the intended functionality, but representation of search results were weak.

So this week I have worked on this issue. After fixing a tiny css bug, I have finalized the representation aspects of search results for Users, Venues and Events. I believe it is much more informative now.