Skip to content
This repository has been archived by the owner on Jan 8, 2019. It is now read-only.

General informations

Jump to bottom
Xennis edited this page Feb 21, 2015 · 3 revisions

Model

Messages

Message models shall include the following:

  • Title
  • Content
  • Author (user that posted it)
  • Radius
  • Timestamp
  • location
  • ID (not visible to user)

When creating a message, the user can set the message’s content, and visibility radius. Author, timestamp, location and message ID shall be set automatically.

In future versions, the messages shall also contain:

  • Message expiration date/time (optional)
  • Privacy settings (which come from user settings, unless otherwise edited at posting time)
  • Author set by logging in from Facebook or Twitter account
    • Choose a custom message marker :)

In future versions, the user model shall have:

  • Friend list
  • Privacy settings

Users

User models shall include:

  • Profile name (must be unique)
  • Email address (for password resets etc., will not be public)
  • Age
  • Gender
  • Nationality (optional)
  • Password

Interface requirements

There shall be two primary views

  • A map view
  • A list view

There shall be a settings and help menu, accessible through the action bar.

On the settings page, the user shall be able to set:

  • default message radius
  • default message time limit (is there a default limit? if so, what is it?)

In future versions, the settings menu shall allow the user to set profile information and default privacy settings.

The map view shall contain the following:

  • A map view that is centered on the user’s current location and set at a zoom level of [TBD].
  • A button over the map view, to create new messages

On the map view, the following will be visible:

  • Messages which have been posted around the user’s current location, within the current map zoom level
  • If the user is within a posted message’s radius, the user may see the message data (visible state). Message data includes: content, author, radius, post location and timestamp
  • If the user is outside a message’s specified radius, the user may see the existence of the unknown message, but not access its data (invisible state).
  • The user shall be able to choose whether to visualize the boundaries of the messages, or just the message center.

When the user taps on a visible message center marker, a message preview shall appear. The message preview contains the message title, and the first x characters of the message. If desired, the user may tap on the preview to display the full message content and other message data (timestamp, location, expiration date, if any).

The user shall be able to dismiss the message data.

In future versions:

  • The user shall be able to filter messages which they see in the map view at their current location based on message tags, timestamps, and radii (other criteria?)

When the user taps on the text field, a dialog shall appear. In this dialog, the user shall be able to:

  • Set message content.
  • Choose message radius (optional, otherwise will use default)

In the List View, the user shall be presented with a list of messages that are visible in their current location, along with distance from current location. This list shall be orderable first by timestamp and also by distance from message center to current location.

In future versions, there may be an additional list view which contains the location and timestamp data of messages that are invisible to the user, but within a certain distance.

More

Update Apache server

Change server

cd GO-TO-DJANGO-APP-DIRECTORY
sudo git pull
sudo service apache2 reload

If you have some new lines in requirements.txt, then additionally, before reloading the apache-server:

source /var/opt/venv/ink-server/bin/activate
pip install -r requirements.txt

...and if you add/change a line in ink/settings.py, then you will also have to do it manually on the server.

Clone this wiki locally