2009-12 Mapbender Development Sprint

From MapbenderWiki

Jump to: navigation, search

Mapbender developers' meeting


Join us via IRC


Contents

Participants

Agenda

0915 Introduction

0945 Hacking

  • set up trunk at Telascience
  • create new application
  • post updates into IRC (SQLs etc), so everyone can keep their copy of the application up to date
  • etc.

1230 Pizza and Q&A

  • Discuss what needs to be done
  • Agree on goals for the remaining time
  • General, informal Q&A

1300 Hacking

  • Finish tasks
  • commit code
  • check documentation
  • Testing

1430 Wrap up

  • Upload fotos
  • Update wiki
  • Write blog entries
  • E-Mail to mailing lists

1500 proposed end

Links to Blog, Report and Pictures

Blog
Picture

[1] [2]

What we did

New application using jQuery UI

Today the Mapbender development sprint took place in Bonn, Germany. We had discussed our roadmap at previous IRC meetings and started to work on it right away.


We have for example created a new application at Telascience. It uses several jQuery UI components, like accordion, slider or dialog. It furthermore uses jQuery effects to create a pseudo slippy map, along with double click zoom in/out or mousewheel zoom. We have also made use of the jQuery UI CSS framework for theming.

Mapbender Dev Sprint
Mapbender Dev Sprint


It's still a very basic and experimental application, but it was a great team effort. We will continue to improve this application over the next months, until it is released in Mapbender 2.7. A big thanks to all who were involved!

Improve Mapbender update process

We had a look at the update SQLs for mapbender.

  • We modified the SQLs so they have effect on the user elements too.
  • We modified the SQLs so they can be run several times without destroying the application.
  • we wrote a new script update.sh that runs only the update files (you can define a cron job to checkout the actual files from the svn and run the actual update scripts to keep you Mapbender up-to-date

Rund the script like this (you can set up a cron job which runs the script regularly):

./update.sh <dbversion> <host> <port> <database> <user>
./update.sh pgsql localhost 5432 mapbender postgres
You can define a cronjob to handle the updates 
crontab -e
# m h  dom mon dow   command
*/10 * * * * svn up /data/svn/mapbender
*/10 * * * * /data/svn/mapbender/resources/db/update.sh pgsql localhost 5432 mapbender postgres

OR

# m h  dom mon dow   command
*/10 * * * * svn up /data/svn/mapbender
*/10 * * * * psql -U postgres 2.7 -f /data/svn/mapbender/resources/db/pgsql/UTF-8/update/update_2.6_to_2.6.1_pgsql_UTF-8.sql
*/11 * * * * psql -U postgres 2.7 -f /data/svn/mapbender/resources/db/pgsql/UTF-8/update/update_2.6.1_to_2.7rc1_pgsql_UTF-8.sql



We set up an installation of Mapbender trunk on telescience.org where this process is run.

Have a look at: http://mapbender.telascience.org/mapbender_trunk/

Integration of CSW in Mapbender

Views
Personal tools