redcap3000 / geoserve Goto Github PK

The groups and type should be drop down menus based on the global types and groups should be based on the available groups

Let each 'service' have a hour of operation per each 'marker'. Other attributes could also potentially be added.

After a server is restarted .. throws an error and new location markers won't appear as downloaded for the first client. Subsequent reloads or client connections don't seem to be at issue. Probably an index/ undefined check needs to be put somewhere...

Perhaps store it in the users.collection, or explore existing instagram oauth modules for meteor. Should do some sort of validation to avoid allowing a different oauth token to insert records for a user who had previously used another one. (this occurs if the user is already logged into instagram.)

Perhaps force user to use instagram to login and not permit them to use any email address?

Create editor for adding marker types, designating the URL for the marker image, and any gmaps specific functionality needed; and to also specify if the 'type' is specific to a single/multiple group (probably create a groups_marker_types)

If you switch markers and attempt to remove a 'service' by pressing X it won't remove the appropriate record. Probably has something to do with my use of the template evt instead of actual values in the DOM. Probably rework the session and get vars to fix this ...

Attempts to make the map set center at startup are proving fruitless. need to figure out a way to set the map center to whatever marker is the top child in nav.

When geolocating (at least when logged in) it won't recenter the map to the latest position.. or added marker.

I've been noticing after a hot codepush if a selected_marker session var exists it will hide the 'available services' pull down menu from the marker editor.

When a locations' recent media feed is being downloaded for the first time it waits for all locations to be downloaded on the backend before displaying back to the screen. It should happen in real time. Might involve somehow using handlebars templates/functions to dynamically build info windows with the modification of the associated arrays (gmapsMarkers,locationMarkers etc.).

When editing a group (by clicking on it) radio boxes no longer populate themselves

Perhaps make a local mini mongo collection that stores a history of a more verbose status updates that includes visualizations of the markers being modified etc.

Create global pull down to filter markers (both public/logged in)... Public filter would be by publically listed groups... when logged in user could switch among

publically listed
my groups - public
my groups - private
my groups - invitational

This wouldn't be hard and makes slightly more sense... but downside is locations wouldn't load as quickly if posts are associated for it for indexing purposes

Location grams should function like the users' feed... but updates should be carried out in the background (server side) so long as at least one person has the info window open.