Skip to content

Instantly share code, notes, and snippets.

View tcosentino's full-sized avatar

Troy Cosentino tcosentino

View GitHub Profile
@tcosentino
tcosentino / orgList.md
Created January 13, 2014 22:18
Org list documentation

Org List

This document will serve as documentation on how to display the list of org/groups.

Change Log

  • 1/13/14 - Troy Cosentino - created

Open questions

@tcosentino
tcosentino / schedule.md
Last active January 2, 2016 10:49
Functionality of the schedule page

Schdule

This document contains details on how to use the schedule page of giOpsCenter.

The schedule view

Create an appointment

  1. Select an admin or admins from the left that you wish to create an appointment for.
  2. Select an org or orgs from the top to display their tickets, alarms, and tasks.
@tcosentino
tcosentino / notification.md
Created January 5, 2014 02:47
User notification system

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, ??
@tcosentino
tcosentino / page.md
Last active December 26, 2015 03:49

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

last night's meeting

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

Kaseya changes

####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.

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.

###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
  1. in updateAd all of the 'else' have set schoolID when they shouldn't
  • $titleUpdate = "UPDATE deal SET schoolID='$dateEnd' WHERE id=$desired";
  1. On every page you need to check if there is a valid session, and if not don't allow them to see the page
  2. Other than that -- most things look pretty good. I will run it tomorrow, and see if I can brake it anywhere haha.
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%",