GitLab

scrolling and dragging

MapEscape[1].
* Set up a js callback to automatically move Google maps controls
out of the scroll area (LEFT_CENTER, opposite of scroll helper).
* Use a simple jquery plugin to auto-limit map height to usable viewport
height upon load/resize/rotation (perhaps use CSS3 in the future).

[1] http://labs.codecomputerlove.com/MapEscape/

page and elsewhere).

This was just too complicated and presented a number of quirks for non fixed-
height overlayed elements.

A few fixes for parse_institution_xml management command

Change the ERROR write to an explicit reference to self.stderr.write - to
always report an error message (and use stderr for doing so).

Replace a leftover print with a call to the write reference (conditional on verbosity).

Recent changes to parse_intitution_xml (b0d86558) make log output go via write reference, conditional on verbosity settings.  However, this reference is defined in the handle method, but used in the parse_and_create method.

This breaks the parse_institution_xml script, failing with:

  File "/djnro/edumanage/management/commands/parse_institution_xml.py", line 70, in parse_and_create
      write('Created inst %s\n' % institution_obj.pk)
  NameError: global name 'write' is not defined

Fix this by explictly passing write from handle() to parse_and_create() as an additional argument.

Requirements: ask for latest Django 1.4

In 37d1c011 / #3, I fixed a Django issue by updating the Django requirement to 1.4.22

Later, 0a077ebc was I assume aiming to generalize this by pointing to "latest
1.4", but unfortunately, points to 1.4(.0) instead.

Fix requirements again, this time explictly asking for:

 Django>=1.4,<1.5

to parse_institution_xml

time in the past...

rather from settings.

Simplify some things in that script, while we're at it.

South migrations: add PostgreSQL issue workaround

Add workaround for an issue with running South Migrations on PostgreSQL.

Migration 0022_auto__chg_field_institutiondetails_number_id__del_field_instrealmmon_i.py breaks on PostgreSQL with:

ERROR:  column "realm_id" cannot be cast automatically to type integer
HINT:  Specify a USING expression to perform the conversion.
STATEMENT:  ALTER TABLE "edumanage_instrealmmon" ALTER COLUMN "realm_id" TYPE integer,
            ALTER COLUMN "realm_id" SET NOT NULL, ALTER COLUMN "realm_id" DROP DEFAULT;
This is a known problem: http://south.aeracode.org/ticket/484
(PostgreSQL will not automatically convert and conversion must be provided with the USING clause)
Workaround: For PostgreSQL invoke a direct SQL statement amended with a USING clause to do the converion explicitly.

Rely on db._get_connection().vendor to determine if we are running on PostgreSQL.

Credits:
* Workaround via db.execute:
  http://codeinthehole.com/writing/altering-postgres-table-columns-with-south/
* USING syntax to convert integers:
  http://stackoverflow.com/questions/13170570/change-type-of-varchar-field-to-integer-cannot-be-cast-automatically-to-type-i

Update requirements.txt to Django 1.4.22

Django 1.4.22 (latest in the 1.4 branch) fixes issues with running in the
English locale without explicit English translations compiled.