wq-django-template 2.0

wq-django-template 2.0.0 is the first stable release of the wq-django-template 2.0 series! Be sure to check out the latest documentation and the release notes for wq 2.0 when upgrading.

This release is functionally equivalent to the alpha release.

wq-django-template 2.0 alpha

wq-django-template 2.0 alpha is a preview of the next version of wq-django-template, as part of the wq.create 2.0 alpha release. This release contains minor updates for compatiblity with wq.db 2.0 alpha and wq.app 2.0 alpha.

All changes by @sheppard.

• Don't wrap wq.db.rest.router.urls in include() (f77e016)
• Import LabelModel from wq.db.rest.models (c498a5a)
• Leverage new nav menu and icon configuration options in wq.app (a1b0388)

wq-django-template 1.3.0

wq-django-template 1.3.0 is the first stable release of the 1.3 series! Be sure to check out the latest documentation and the release notes for wq.create 1.3 when upgrading.

All changes by @sheppard.

Changes since wq-django-template 1.3 beta

• Update to Django 3.2 style settings; remove references to wq.db.default_settings (#30)
• Add example survey application (#27)
• Move all config customization to Python (wq/wq#54)
• Add deploy.bat for windows use (#20, wq/wq.build#3)

Other changes since wq-django-template 1.2.1

• Changes in Alpha
  • Replace AMD/RequireJS integration with ESM build
  • Replace jQuery Mobile with Material UI
  • Replace PhoneGap Build and ApplicationCache with ServiceWorker
• Changes in Beta
  • wq start renamed to wq create
  • Allow specifying site title via wq create
  • Update default map bounds to [lng, lat] order

wq-django-template 1.3 beta

wq-django-template 1.3.0b1 is the beta of the next version of wq-django-template, as part of the wq.create 1.3 beta release. See the wq.create release notes for details on the included changes.

wq-django-template 1.3 alpha

wq-django-template 1.3 alpha is a preview of the next version of wq-django-template, as part of the wq.start 1.3 alpha release. The app/ folder in particular has been completely reorganized (c68524f):

• For wq start --without-npm, the RequireJS build has been replaced with ES modules that can be deployed with ./manage.py collectstatic (#6, #21, and wq/wq.app#111)
• For wq start --with-npm, the Create React App template has moved to @wq/cra-template in the wq.start repository.
• The new @wq/react + @wq/material renderer is registered by default in both templates
• Service workers are now supported, while PhoneGap Build and Application Cache support has been removed (wq/wq.app#63, wq/wq.app#107, wq/wq.app#121)

wq-django-template 1.2.1

wq-django-template 1.2.1 fixes various action buttons that cannot use require() in npm-based projects (wq/wq.create#6).

wq-django-template 1.2.0

wq-django-template 1.2.0 adds support for the --with-pgb flag added in wq.start 1.2.0, and updates the provided package.json to @wq/app 1.2.0 and @wq/map 1.2.0.

wq-django-template 1.2 beta

wq-django-template 1.2.0b1 includes an alternative project layout based on Create React App (CRA). This makes it possible to leverage NPM to manage JavaScript dependencies, and CRA's Webpack/Babel configuration to build and debug the application. See wq/wq#44 and the release notes for wq.start 1.2 beta for more information this feature.

Other Changes

• Add [project_name].sqlite3 to the .gitignore (#26 via @tubaman)
• Update SPATIALITE_LIBRARY_PATH for Ubuntu 18.04 compatibility (ec124cc)
• Update plugin hook usage for wq.app 1.2 beta (34cae67, d0792a6, 96244e3)

wq-django-template 1.1.1

Together with wq.start v1.1.1, wq-django-template 1.1.1 incorporates the ability to disable GeoDjango (django.contrib.gis) which makes it easier to get started without having GDAL installed (see wq/wq#34).

To use the new feature, upgrade wq.start and run:

wq start --without-gis myproject

wq-django-template 1.1.0

wq-django-template 1.1.0 brings Django 2 support (together with wq.db 1.1.0), as well as a restructuring of the settings to better match best practices. The old settings.py would attempt to import local_settings.py and ignore any errors. The new settings structure flips the order around: settings/dev.py and settings/prod.py each import from settings/base.py.

This approach makes it easier to use dev settings when first getting set up with wq and then switch to production settings when deploying on a public URL. The new dev settings assume SQLite/SpatialLite while the prod settings still contain a default PostgreSQL/PostGIS configuration.