Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Section
Column
width30%
Page Tree
rootDocumentation
expandCollapseAlltrue
startDepth0
Column
width70%

Weekly logs

Info
title07/09 - 16/09
  • This week I've been fixing bugs and preparing the code for the first release.

It's still not as smooth as it's desirable so, probably I need to work a bit more on this.

Problems:

  • None

Work for the next week:

  • Check the development with my mentor and write documentation
Info
title01/09 - 06/09
  • This week I've tried to make work the disk and memory cache for vector features in gvSIG Mini. This means that whenever a request is made to POIProxy, the results are saved in disk and the most recent ones in memory, so one the request needs to be done again, first it looks in memory, then in disk and finally if the vector features are not available the request is made to POIProxy.

It's still not as smooth as it's desirable so, probably I need to work a bit more on this.

Problems:

  • None

Work for the next week:

  • Finish the cache system for vector features.
Info
title17/08 - 23/08
  • This week I've been developing the user interface to allow a user select a POIProxy service. At the moment a request is performed each time the button at the top bar is touched. With this functionality any time a new service is added to POIProxy it can be visualized into gvSIG Mini without the need to re-build the application

When the user taps on the top bar button, it makes a request to the available services in POIProxy, then the application presents a ListView to the user with the name of the available services. When the user taps on any item in the ListView a new POIProxy overlay is added to the map. At the moment just on overlay can be added at the same time. This is because performance issues that I'm not sure to be able to solve from here to the end of the summer.

Problems:

  • I've tried this week to add some kind of disk cache, to speed up the load of POIs, but I'm facing problems while accessing file system in Android. It is almost coded, but I need to make some tests to make sure that it really makes the application go faster.

Work for the next week:

  • Next week I'm taking holidays, I've talked to my mentor and is OK for him. So, I'll be back on September 2nd to continue with the final part of the project (smile)
Info
title11/08 - 16/08
  • This week I've developed a connector with the describe services operation of POIProxy, so that any layer supported by POIProxy can be viewed on gvSIG Mini. This is important because there is no need to change the Android application when a new service is supported by POIProxy, it is some kind of GetCapabilities for POI services.

I'm still playing a bit with the API demos of Android mainly the layouts and ListViews stuff.

Problems:

  • There was a problem with the JSON document returned by POIProxy when requesting for the describeServices operation, it seems not to be a valid JSON. So, at the moment I'm working against a test JSON, next week I will try to modify POIProxy itself.

Work for the next week:

  • Connect with the DescribeServices operation of POIProxy and build the UI to select a service
Info
title04/08 - 10/08
  • This week I've started to read documentation about Android. Until know I've been coding plain Java
    code to connect to POIProxy services and a bit of Java code using the gvSIG Mini API.

From now I'm going to start to write the Android app itself, mainly user interfaces.
I've been playing a bit with some of the Android API demos, to see what kind of things I can do with the SDK. Next I've converted the project I've been developing during the first part of the GSoC into an
Android Library and I've created another project that depends on it and that will contain the UI.

Problems:

  • None, but lots of documentation to read, so no much productive this week.

Work for the next week:

  • Connect with the DescribeServices operation of POIProxy and build the UI to select a service
    Additional documentation of my project can be found here 1
Info
title27/07 - 03/08
  • Implemented a first version of a reverse-geocoding control, that given a point, requests POIProxy for
    the geographical name.
  • Fixed some bugs on the POIProxy layer, some others are still there...

Problems:

  • None

Work for the next week:

  • Validate the first part of the project with my mentor
  • Test, test and test
Info
title20/07 - 26/07
  • Finally spent all the week fixing bugs on the POIProxy overlay and polishing things for the mid-term
    evaluation. Continuous revision of the bug catching process by my mentor helped a lot.

Problems:

  • None

Work for the next week:

  • Start the implementation of the geocoding control.
Info
title13/07 - 19/07
  • Validated current status of the POIProxy layer with my mentor. Several bugs found.

We have detected a 'usability' problem... as the user navigates the map, more and more requests are made to POIProxy, that slows down the map loading. An improvement to solve that problem would be to implement a disk or at least memory cache, to not repeat requests to POIProxy. At the moment we have decided don't implement that feature, but take it in account at the end of the summer if there is available time.

  • Studied the controls API of gvSIG Mini

Problems:

  • Again lack of documentation on the Control API

Work for the next week:

  • Fix bugs on the POIProxy layer.
  • Implement the geocoding control.
Info
title06/07 - 12/07
  • First version of a complete POIProxy layer in gvSIG Mini. Requests are made as the map pans. Tested several services and all seems to work smooth.

Problems:

  • None

Work for the next week:

  • Validate the current development status with my mentor
  • Create a gvSIG Mini control to request a geocode and reverse-geocode operation to POIProxy.
Info
title29/06 - 05/07
  • Implemented a layer that connects to a POIProxy service. Now the layer draws points from Foursquare. A fixed bounding box strategy is used at the moment.

Problems:

  • None

Work for the next week:

  • Add support to a dynamic bounding box strategy, so that as the maps pans, new requests are done to POIProxy
Info
title22/06 - 28/06
  • Created a simple layer that draws points into a gvSIG Mini map with the possibility to define the symbols

Problems:

  • Due to the lack of documentation of the gvSIG Mini layer model, I've spent several days on building a simple point layer example. Direct communication with the mentor has helped a lot.

Work for the next week:

  • Connect the point layer to a POIProxy service
Info
title17/06 - 21/06

Familiarize with the gvSIG Mini projects, wiki, SVN and Github, maven, Google App Engine...

  • Built the gvSIG Mini workspace
  • Read POIProxy documentation and play a bit with it

Problems:

  • No further problems at the moment

Work for the next week:

  • Study the gvSIG Mini layers model
  • Design a new layer to connect to POIProxy services
  • Start writing code to connect to a random POIProxy service