tcosentino

New use cases to test

Map

• The user should be able to see admin and org's represented by pins on the map at their current location. (Anoop needs a way to update admin's locations)
• The user should be able to use the red target button in the admin list to move the map to the location of an admin.
• The user should be able to open an admin or org's vCard by clicking their map pin and then the arrow button.
• When a new admin or org is selected the map should zoom and move to show all selected admins/orgs.
• When a group (in the org list, anything inside of an expand section) is selected its vCard should be displayed.

Controller

tcosentino

string opLicTotalCount = string.Format(@"http://{0}/mandell-mvc/agent/gisrvGetOperatorLicenseCount?license={1}&sessionid={2}",
                    server.GIServerString, version.LicenseKey, "12344321");
string travLicTotalCount = string.Format(@"http://{0}/mandell-mvc/agent/gisrvGetTravelerLicenseCount?license={1}&sessionid={2}",
    server.GIServerString, version.LicenseKey, "12344321");

HttpWebRequest httpWebRequest = (HttpWebRequest)WebRequest.Create(opLicTotalCount);
httpWebRequest.Method = WebRequestMethods.Http.Get;
httpWebRequest.Accept = "application/json";

WebResponse response = httpWebRequest.GetResponse();

tcosentino

// From agentListServer

var statusIcon = "";

switch(Number(oObj.aData["OnlineStatus"])) {
	case 0: if (oObj.aData["rCriticality"] === '0' || oObj.aData["rCriticality"] === '') { statusIcon = "GrayDot.png"; } else { statusIcon = "agentAlarm1.png"; } break;
	case 1: if (oObj.aData["currentUser"] === "") { statusIcon = "GreenDot1.png"; } else { statusIcon = "BlueAgent1.png" } break;
	case 2: if (oObj.aData["currentUser"] === "") { statusIcon = "GreenDot1.png"; } else { statusIcon = "YellowAgent1.png" } break;
	case 198: statusIcon = "suspended.png"; break;
	case 199: statusIcon = "FrongGlobe58.png"; break;

tcosentino

		this.chart = AmCharts.makeChart(this.el, _.extend({
		  type: "pie",
			theme: "none",
		  dataProvider: this.collection.getAmChartData(),
	    valueField: "value",
	    titleField: "label",
	    theme: AmCharts.themes.dark,
	     outlineAlpha: 0,
	    //"radius": "28%",

tcosentino

###Just a few notes about the code you sent:

1. I have heard/read that the 'mysql' family of php functions are being sort of phased out. mysqli is replacing it, as well as other things like PDO. I think it would be good practice/best if you switched it to PDO because thats what we use with the rest of the site.

• PDO lets you make it more object oriented

2. in updateAd all of the 'else' have set schoolID when they shouldn't

• $titleUpdate = "UPDATE deal SET schoolID='$dateEnd' WHERE id=$desired";

3. On every page you need to check if there is a valid session, and if not don't allow them to see the page
4. Other than that -- most things look pretty good. I will run it tomorrow, and see if I can brake it anywhere haha.

tcosentino

The tree layout implements the Reingold-Tilford algorithm for efficient, tidy arrangement of layered nodes. The depth of nodes is computed by distance from the root, leading to a ragged appearance. Cartesian orientations are also supported. Implementation based on work by Jeff Heer and Jason Davies using Buchheim et al.'s linear-time variant of the Reingold-Tilford algorithm. Data shows the Flare class hierarchy, also courtesy Jeff Heer.

tcosentino

####Charts Development

---

#####Session ID It was not clear to me where this is to come from. Grep'ing for it on the source revealed a lot of hard coded versions of it. For the moment, it is hard coded at the top of charts.render.

#####URL Roots (Chart-Server/Chart-Images) There are currently two hard coded url roots. My assumption is these will be handled by some type of configuration file. Has this been defined as yet?

#####CSS: Created charts.scss with two simple classes.

tcosentino

last night's meeting

• introduce Ahmad
  • clean up svn
  • hudson? - automated build process / distribution
  • email him about 10.10.1.28

Kaseya changes

tcosentino

Page function overview

The goal of this document is to describe the common functionality in each page, including how to add/create a new one.

Each page has three files that make it up: a template, view, and model (more of a helper to manage all the models that the page needs).

Note: the model manager should be abstracted but I haven't gotten to it

tcosentino

Features required

• Notifications for one, many, or all users
• Marked as read/unread
• Link or action associated with it.. e.g. clicking 'you are now friends with -----' goes to their page
• Notifications are split into 'types'
  • types will have a template to determine how to display
• Users can choose settings on where to receive them (by type)
• where being in the app, email, ??