Some work on the server. The databseObject will be renamed to a DestinationObject soon as they hold the jobs. The post method now creates a timestamp for the objectID of the data to post. The Get method accepts an ObjectID and returns all of the Objects it has recieved since that one. This will be the standard use case for this class. Also added was a general error handler to catch exceptions in the code and return a flask.response. Right now generic try/except clauses were added to the get/post/del methods to catch the error to log a message and  then reraise the exception to trigger the error handler
Fixed up how objectIDs are returned frm the get_objectid_from_json function and cleaned things up a bit. I created separate object for the Jobs and Travelers. There is little difference in implementation, it was mostly for readability in further code
Added initial support for the telenav SOAP service as a provider of TraverlerObject updates for the CAReding module. This functionality is still in its early stages and is under testing. The data provider is triggered by signal and will only update once every five minutes regardless of how many times it is signaled. Also when triggered it will only grab updates that happened after the last update. If no last update time is available (ie it is the first run since the app has started) it will grab all entries since 5am that day.
Added some very basic login functionality that is not complete and not secure, passwords currently stored in plaintext. Used Flask-Login for session mgmt. Made views and forms for logging in, logging out, registering. Finally I added a basic map view that is visible after logging in that is just some basic demo code from the maps API website. pretty cool things happening
Should be contacting the server correctly.
new config parsing for client
should now allow the client to connect to the web service
Logging in now works if the user and password exist in the database, everything is plain test right now as there is no encryption or hash function being used, I'll get to this later. The map screen shows up and the tolbar is in place, it look just like the screenshots we gave to our customers. The only options on the menu bar that work is the Logout option unfortuntely. Also, the map iniitally posts all of the travelers that are passed to it on creation. I created an interval in the javascript of map.html that calls a function named updatePoints. In thi function will update the data continuously. The interval will eventually be defined by the user. Also we need to filter data better. Make sure that we aren't posting two locations for the ame PTN (Phne number) and ensure that our time interval queries are working. Good visible progress
Merge branch 'master' of github.com:ccarlton/WhatWhere
fixed bugs and cleaned up code for jaring
fixed bugs and cleaned up code
Merge branch 'master' of https://github.com/ccarlton/WhatWhere
Some work on getting dynamic updating to work with ajax. Results are looking good, I need to parse the results so we are only showing the latest location for each driver and we only get actual new movements every iteration. Refresh rates have been set very low because the code currently hits the telenav soap TOO much. It is easiest for us to use their getLatestGPSMovement function, but we must call it for every PTN rather than a single call to getGPSs. getGPSs however returns tons of extra unnes.
Merge branch 'master' of github.com:ccarlton/WhatWhere
added the make territory paths and registered the view
made changes for the territory manager view
more rectangle stuff
added a new service to handle app requets
Merge branch 'master' of github.com:ccarlton/WhatWhere
changes to territory manager