8:00 – 5:00 SR

• Filled out contact info for Steve
• The stricter trust chain did not work. I had Ronda go back to the looser one.
• Fixed attraction/repulsion/linkScalar it’s 1.0, 10.0, 10.0 for defaults
• Ran into a weirdness with <input type=”range> and browsers. Chrome is fine. FF and Chrome have differing default widths and margin/padding. Had to add the following to get all ranges to work similarly:

  .forceRange{
      position: absolute;
      width: 120px;
      right: 10px;
      margin: 0px;
      padding: 5px;
      z-index: 2;
  }

• Back to figuring out the AlchemyNews API. Blew up the limit again, being careful. I think that the news API, aside from behaving poorly (things like ‘&q.enriched.url.concepts.concept.relevance=0.9’ don’t work). Think I’m going to add more user interaction and less machine learning. Store it all for later page ranking?

8:00 – 2:30 SR

• Updated the truancy report.
• Adding multi-connections to network construction
• Woohoo!
• Then
  • NewsAPI or database.

8:00 – 2:00 SR

• The production server is behaving again!
• Wrote up some thoughts on TypeScript interfaces and fat arrow notation.
• Working out more subtle network linkages. An item is current (selected?) has potentially several other items that will connect to it. Selecting should also bring up the search results associated with that item (create an itemlist of nearest neighbors). Maybe the item should be created before the results of the query come back. That might make things more modal.

8:00 – 4:30 SR

• The production server isn’t visible through the browser, though the test server is. It first I thought it was pre-populated keychains, but when the servers are set up identically, the production server still doesn’t cooperate. Ronda’s putting in a ticket.
• Helped Ronda generate a PKI request for the new dev server, she’s going to try to make it work on the other two.
• Looking at Dong’s code, I cannot figure out why he needs fat arrow. His:

  public promiseCaller():void{
     this.promise = this.service.getQueries();
     this.promise.then(this.processData, this.errorData);
  }
  
  public processData = (data:any):void => {
     console.log("got data");
  };
  
  public errorData = (data:any):void => {
     alert("error getting data");
  };

• And mine

  private goodUserQuery (response:any) {console.log("got data");}
  private goodUserQuery (response:any) {alert("error getting data");}
  public promiseCaller():void{
      this.queryService.submit(qstr, this.goodUserQuery, this.errorResponse);
  }

• Which calls (in the service):

  public submit(query:string, goodResponse:any, errorResponse:any):any {
     return this.httpService(query).then(goodResponse, errorResponse);
  }

• And it looks like Google won’t let me use their images as textures. Working at downloading on the server side and storing in a local directory, using PHP. That works just fine! And to keep from downloading the same pix all the time, added a check as well. PHP has pretty much everything you’d ever want to do stuff on the web. But no typing. Must check out Hack one of these days.
• Adding connections. Finally! Simple conditions are working and up.

8:00 – 4:00SR

• Prime day. May poke at that a bit. Disappointing.
• Call Porsche for oil change and chin cover repair – nope. Tomorrow?
• Get network connections working – Almost!
• Add news API integration – nope

8:00 – 4:00 SR

1. Sent Steve F. some background on Visibility and equipment requests
2. Continue working on integrating dynamic data provider into charts. First pass is done, but kind of crappy. I think there needs to be a recursive way of adding the data. Something like an tree object that recurses through itself to create the data provider which is then rendered. Ponder it over the weekend.
3. Need to make a self-contained example of the flexbox/ng-repeat interaction.
4. Redid my tuition reimbursement because Novetta changed it after I submitted it before.
5. Uploaded the current app and it still works!

8:00 – 4:30 SR

• Re-ordered my dev machine
• Had a good discussion with Lenny about future directions for the project and how to effectively use my time while we wait for someone to come on board.
• Working on figuring out how to put an absolute div in a dynamic page. Ok, here’s how I got it to work.
• This is the style

  <style>
      .wrapperPanel {
          display: flex;
          justify-content: center;
          background-color: lightgray;
          margin-bottom: 10px;
          margin-top: 10px;
          width: 98vw;
          height: 30vh;
      }
  
      .mainWindow {
          position: relative;
          width: 100%;
          height: 100%;
          background: linear-gradient(darkblue, black);
      }
  
      .glDiv {
          position: absolute;
          width: 100%;
          height: 100%;
      }
  </style>

• and this is the HTML

  <div class="wrapperPanel">
      <div class="mainWindow">
          <ng-network-webgl class="glDiv" config-obj="glc.configObj"></ng-network-webgl>
      </div>
  </div>

• The mainWindow css is needed so that the div with the ‘glDiv’ css has something to reference to. Otherwise the overlays won’t work.
• Lunch thoughts
  • Confirm/Dispute
  • URL chain (or, just chain)
• Handoff meeting from Brad to Steve tomorrow at 2:00 or later.
• Added webgl network canvas using inheritance for the controller. Aside from forgetting the stylesheet, everything worked as hoped for!

8:00 – 4:00

• Told Lenny about Dong’s resignation.
• More dynamic chart data.
• Set the meta information about the kind of data into each item so that the directive knows what to draw.
• In the main app, set it so that the data was returned in one object and meta information about the query was returned in the other
• Connect the data provider to the initial pull
• Add additional defined strings for query types to support different flavors of queries (DRILL_DOWN, etc)
• Add defined strings for response type (NEW, REPLACE, APPEND, UPDATE, etc) UPDATE should keep current data and only add new.
• Need to be able to add and delete (lines? lighting?) between nodes without adjusting the behavior of the nodes. It’s be nice to be able to do this as part of the mouseover
  • AddRelation(target) – creates an entry in a hashmap
  • DeleteRelation(target) – deletes the entry
  • CustomMouseoverBehavior(c:WglComponentBase){} – add to CanvasBase