8:00 – 5:00 SR

• DB Backups
• Deployed new FA and RA
• Added a column to the master table
• Added labs to FRa
• Angular
  • Worked on http interaction. It turns out that Angular likes to post in JSON format, but most servers (PHP, Java) use URI encoding. Spent a few hours going around and around with that. There are also no directives around <br>, and ng-model doesn’t seem to work with <div>. Nonetheless, I’m interacting with the database through a web page, so yay.

8:00 – 4:30 SR

• DB Backups
• Updated FA, RA and project_portfolio_enh on the integration machine to see what’s going on with FMPs. They are in the DB, but not showing. It seems to be related to an event problem in the display.
• Meeting with Ronda at 4:00.
• More Angular!

8:00 – 4:00 SR

• Got an email from Geena – she’s unable to save a mitigation plan. “To elaborate, looks like the malfunction occurs when ‘copy from previous month’ is selected, unable to save. I selected ‘copy from previous month’ and modified the data yet unable to save”
• DB Backups.
• Get for class, this too.
• Working through chapter 3 of AngularJS Up and Running, which introduces unit testing. I was having trouble getting karma to run – getting the error
  • ERROR [karma]: { [Error: listen EACCES] code: ‘EACCES’, errno: ‘EACCES’, syscall: ‘listen’ }
• Poking around led to this post, which suggested changing the port in the karma.conf.js file to 8001 from 8080. This works just fine, though I’m not sure why port 8080 is choking. I have Tomcat installed on 8080, but even with Tomcat off, I get the same error. Odd.
• On to forms and validation. Very nicely done.

8:30 – 5:00 SR

• DB Backups
• Resubmitted test server for web approval since it didn’t show up on the list
• added banners to the FR site
• Angular. Getting started on testing.

8:00 – 10:00, SR

• DB Backups

Aaaand that’s it. Bad day at the vet.

8:00 – 6:00 SR

• Deployed FA and RA
• Servers are working fine today.
• Changed the slideshow queries to accommodate the new month.
• Made sure that the key mapping hack works in all browsers.
• Back to Angular

8:00 – 8:00SR

• DB Backups
• More Angular. Going to try to connect to the server and get Funding Request data.
• Nope, got distracted. It turns out that the browser DOM keyboard model is not ASCII. If you listen for keyboard events (as some of the charting apps do), then it’s impossible to determine what key has been clicked by just looking at the event.charCode in the keypress event. So instead, my first Angular app is going to be a webapp that allows you to enter in a set of keyboard characters and have the javascript determine what the keycode maps to. This varies by browser and edition. Did someone not tell early web developers that there was this thing called an ASCII table? Here’s the angular directive