geodan/cow

Concurrent Online Workspace

cow's Issues

Rename some names

Herd -> Project
Store -> Project (only in the messaging)
feature -> Item

Add support for roles

This is a big one.
Start by designing a role/permission system.

Ultimately roles can be defined by any peer and propagated to other peers.
For a start roles can be baked into the code. An owner starts by selecting a role and is consequently presented with an interface with some functionality enabled based on the permissions for that role.

Add 'type' object to item

Write API docs

Add functionality for multiple languages

• Add variables for strings
• Make translations (Dutch)

Use local stored maptiles

Opanlayers is able to do this with indexeddb. This could dramatically increase map update speed and enhances offline use.

Repair funcionality on creating new records

Some fields are not filled on first creation of record (notably created and owner)

Create group object and syncing methods in COW core

Groups will get a seperate table per project (formerly Herd)
Syncing like herd syncing
Groups are an object per project
Add methods to set/retrieve groups

Avoid code injections from forms

At the moment any code can be inserted into the text fields and executed upon parsing. That is NO good.

an item loaded from the database is always a feature

The itemStore.loadItemsFromDb sets the item type always as 'feature' this way we cannot load items with another type and get those back

Clean up cow.peer.js

There seems to be a lot more code going on than needed for adminstering the extent of the peer.

Redraw positions upon own location change

At the moment positions are only updated/redrawn when someones else's position changes.

Sharing text messages

Text messages should be shared. This means a core update.

Make links between messages and map-features. That could be done in the clients via tagging.

Create GUI for sharing text (kind of chat interface)

Add audio/video with peerjs

Waiting for the peerjs library to deliver a more stable version with AV support.

Add video support via peerjs

• Get stable peerjs lib
• Make fit in GUI
• add peerjs server to own nodejs server

Add phoenix client

Nils is working on this, should be ready for DLG demo.

Replace current indexeddb with POUCHDB and add groupsdb in the process

Do for:
projectDB
groupDB
itemDB

TODO for progideon

• [OK] Add 'Add feature' functionality
• [OK] Startpage for login and group choosing
• [OK] Add extended label on hovering over features
• [OK] Add logout button
• [OK] Messages only visible when permitted (view or edit)
• [OK] Add group info (colors) to messages
• [WF] Add relevant icon / linecolor to messages
• [OK] Add measurement tool
• [OK] Make 'gedeeld beeld' functionality work:
  Fixed set of groups (o/p/e)

Deal with feature ownership (creator/updated by)

Make sure ownership is stored in the feature.
Update map/feature widgets accordingly.

Improve D3 layer

Make a more robustly configurable maplayer.
Certainly fix the weird envelope folding behaviour of the extent.

Admin panel/functionality needed

Functionality:

• Set all feats to (un)deleted
• Clear whole database
• Restart nodejs
• Set maximum age of features
• See peer activity (movements, features etc)
• Force peers to extent
• Lock on peers extent

Expiration time in Sketch layer

Features that haven't been updated for xx ms. should not be showing up or be distributed anymore.

Add external libs

libs like jquery, openlayers etc. should be included minified

Add location to core object

me().location() is not available when disconnected. Therefore it should be (like username) be added to the core.

Add admin functions to core

Redesign desktop interface

Interface needs some new design, especially on the level of menus.

Add permission object to items

item.permissions = {read: [groupids],write: [groupids], share: [groupids]}

and method to set them?

Add alpha peer check

Peers should only broadcast 'answers' when they know they are the alpha peer.
With COW2 it is no longer needed for alpha to be inside the same project so we might be able to implement the old findalpha routine again in the websocket.js

Treat the map as a widget

The map is in fact nothing more than a replaceable screenwidget that displays the data that goes around in COW. Therefore all references to the map (e.g. OpenLayers lib) could be better put into the widget.
To keep in mind: some COW functionality depends on the map, for instance your viewextent that is being sent to other peers.

Write a stresstest

Stresstest automates processes like adding/remove features, updating location, extent name etc...
Also usefull as a DEMO

Create featurelist widget/addin

Not a must-have:
Features should be in a list, default ordered by time but other orders possible.

Correct behaviour after a peer disconnects

• Remove from d3 layers (refresh on basis of peers() might do)
• Remove from peerwidget (same)

Make use of Identifications

Add an identification parameter to cow
Currently we have
CID which is the websocket ID, changes very often
UID which is the client ID, changes upon page reloa
add:
PID will be any string that identifies the person behind the client. Only changes on user request.

At the moment is is good enough to use the owner().name parameter as PID. It is not a big problem when people have the same PID but should be avoided in the future.

Objects that will make use of PID:
project.groups().members[pid list]
item.creator() -> pid
item.owner() -> pid
core.pid() -> pid

Add method to COW to set UID

Re-create webscocket after disconnect

After a disconnect the websocket object is gone. Needs to be recreated somehow with options earlier given.

Rewrite featureStore and localDB

Update the code to JQuery standards.

Add chat functionality

Involves new messagetype in cow and interface implementation.
How should messages be stored?
Should there be a link between messages and features?
Is a message very different from a feature anyway?

Needs to be implemented for IPO demo

Set correct texts to extents on first draw

The correct text is only prolongated after the peer moves the extent. This should be done when the d3 layer is initialized the first time.

Install peerjs server along websocket server

Source and doc:
https://github.com/peers/peerjs-server

Redraw d3 layers on mapCenter

When map is programmatically ceneterd (like after clicking on center to peers location) the d3 layers are not updated.

GUI and method for adding herds

Extra functionality geolocator

Add options:
poll continuously/in intervals/no polling

Button to zoom to own location (also when no websocket available)

Add initial extents on mapload

After the mapwidget is loaded, update the me() peer with the extent

Create populator add-in

Best would be when directly accessible from any polygon on the map.

Result should give an indication on the map of how many people are inside that polygon

Add prioritization option for items

• Items can have different priorities. (likely 1 to N)
• Priorities can be entered from interface.
• A priority filter can be applied to map/itemlist

Localdbase not always behaving correct

Localdbase is more often than not empty where it should have records.
Not sure what causes this but quite a showstopper.

Find way to return a historical situation of a record

Based on the deltas.
Mind: we cannot change the data object since that would be changing the recent status.

Make lines easier selectable for touch on map

For lines the touchable area is very small. Set this to more pixels.

Improve GUI for mobile

Add icon set

• Eenrichtingsverkeer aangeven dmv pijlen (liefst die je in de richting van de weg kunt draaien; als draaien niet kan, dan standaard borden met pijlen in elke windrichting; liefst witte pijlen gegoten in een blauwe achtergrond, zodat het lijkt op de 1 richtingsverkeerborden)
• Afsluiten weg: verboden toegang verkeersbord
• Populator resultaat: Aantal figuurtjes bij elkaar
• Vee resultaat: plaatje van varken, schaap (ik weet ff niet meer welke dieren allemaal in het systeem zitten....)
• Opvanglocaties: symbool van rode kruis of zoiets in gebouw? wellicht meerdere van dit soort symbolen: aparte kleuren voor wel/ niet geschikt voor gehandicapten en aparte grootte voor de grootte van de opvanglocatie; het symbool moet niet te verwarren zijn met ziekenhuis symbool
• Dijkdoorbraak: symbool van kapotte dijk? of van waterdruppel?
• Politie
• GGD symbool
• Ziekenhuis symbool
• Brandweer
• Gemeentehuis
• Telecom mast als symbool voor ad hoc communicatiepaal
• paar neutrale symbolen (gewoon vierkantje of rondje met verschillende of zo; voor het geval mensen zelf iets anders verzinnen)