This week, Gozde Gulsah and me worked on the chat part and fixed some bugs. Now, a chat user can close a chat tab , disconnect from chat. Moreover, the user can chat with more than one friends, if a friend opens a dialog and he is not on the chat tab list, a new chat tab dialog occurs.
We have implemented new listeners and changed some flow of the chat process.
derya
This week, I was responsible for the showing map views of the events (Event module) and I took place in a little part of the Chat module. There are two kinds of events, namely events that are recommended by Last.fm and events that are created by Finger Tune users. When we retrieve the recommended events from Last.fm, we can keep the latitudes and longitudes of the event locations. But unfortunately, user created events are not defined with their lat&long. In order to fix this problem, I have used “Geocoder” class of “android.location”. With the help of this class, The address of an event is converted to its geographical coordinates.
Finally, as I did in the map views of the Stores, I have used “MapOverlay” class that extends “ItemizedOverlay” class of “com.google.android.maps” in order to show the location of the event on the Google map and also to put a marker on it. When the marker is clicked, event details are written in a Toast box. Then we have integrated the parts of Event module with Betul.
Next week, we will work on Turkcell integration and the web site of the stores.
This week we have finished event with Gozde. Gozde has prepared the map view of the event addresses. I have finished “not/attend, maybe” parts for any event.
While preparing attending part, I had two separate implementation for Database events and Lastfm events. I have added a new table to our database about the attending. Then, Database implementation connected to the new table and set the user’s status. For Database Events it is possible that the user can see attending Last.fm friends on the screen as a ListView. Secondly , I have used Last.fm API and asked for event.attend method. The important thing is that. Even the user can see the attending friends while looking to database events, the user will not be able to see his/her attending friends for Last.f event. The reason is the event.attendees method returns sometimes millions of people if the event is so popular for example. So searching for the friends is so costly and can take time, so we do not let the user see his/her Last.fm friends while looking details of Last.fm events
Shortly,event has finished :))
This week, I worked on again ChatScreen with Derya and Gozde. Last and the most important bugs fixed about chatting and some features(e.g Closing a tab, disconnecting from chat) are added.
We think chat part is totally over, some minor bugs may be detected during a detailed test and will be handled than.
Next week, I may work on Turkcell Api, especially sending SMS.
After the implementation of the delete event part, now update event part is also ready. The user logins to the system. Then clicks update event menu item. The user sees all the events he created. After that, he chooses the event which he wants to update. The update screen is seen. The user can change any information from any part.
Then clicks the “update it!” button, the event is changed on the database.
Next week, I will finalize the event part with the last thing: attending/ not attending..
Note: Actually server side processes are easy but sometimes problematic. The reason why i am just a bit late is that.
This week I have dealt with Delete Event part of our project. Actually, with the help of the event module’s current position I could have done it easily.
Now, if a person has any event in the database, and he wants to delete it, clicks from menu item to “delete event”. All the events created by him are taken from database and listed. Then s/he chooses the event to delete. The last change is given to him to stop deleting. If he really wants to delete it, the next window’s OK button is clicked and the event is deleted permanently.
Also I add a window to update event part of the project, however I could not finalize it. Again all the events are listed to the person. If he wants to update it, he will be able to..
This week, I have worked on the “Chat module” again. The part that I was responsible for was handling the chat messages coming from an online friend. When an online friend of the user wants to send an instant message, packet is handled immediately by “PacketHandler” class. While processing the packet, user is directed to the chat screen where his/her friend writes messages. Apart from the previous screens, chat screens are shown in the “tabbed” screens which was related with Gulsah’s part.Thus, Gulsah and I have integrated the two parts and made two people talk on Android in a more user friendly way than previous chatting. But it has still some problems, we will work on fixing these problems next week.
This week, I did some research on Android Tab view to make our chat screen tabbed. I implemented some simple examples. The in our project, I moved our friendlist screen inside of the tabbed view.
After that, Gozde and I, combined our works and came up with a list screen, when a friend is selected the chat window with that friend is opened as a new tab. Of course we need to do may improvements on it. But proof of concept is achieved i think.
Next week we will try to make it a complete working buglesstabbed view.
As you know, last week I have worked with Gozde, and we dealt with Store and album access. This week I am working alone on Event creation. We have already taken the events from Last.fm. And we could be able to list them and give the details.
Now I can as a Last.fm user create an event on FIngerTune, and share with my friends. If any of my friends create any event I can see them and look at the details.
Cretating and Deleting options are on the Menu Options again.
After clicking the Event button from main menu, the friends events (above), and last.fm recommended events welcome the user. If the user wants to see the details of the events, s/he just clicks the wanted one.
Note : DatePicker is used for creation page. This is actually important , i think, because of the SDK that we are using, the DatePicker does not seem as planned. So our datepicker is a bit different
Last week, Betul and I worked on the Album Access module. We retrieved the list of the stores from the database which have intended album. We added extra retrieval methods to Java server. After showing the list of the stores, we prepared a user interface that shows the Google map views of the store clicked with the help of the latitude and longitude of the stores kept in our database. We worked on the overlays (e.g. ItemizedOverlay) for putting placemarks on the locations of the stores.
This week, I have participated on the Chat part of our project. After examining the code that Gulsah and Derya wrote, I searched over the chatting between two Finger Tune users over Open Fire server. Derya and I made a connection between two users and make them talk on Android. In order to do that, we connected the users to a global Open Fire server and port, then implemented packet listeners to handle the incoming instant messages and outgoing instant messages. We have performed chat view by using refreshing multi line lists. But chatting part has still problems,next week we will go on to work on this.