12:00 – 4:00

• Spent the morning at UMBC for PhD activities. Had the department heads reinforce that if I couldn’t get additional hours it would be “virtually impossible” to get a degree. Thanks a bunch, WCC/Novetta for reneging on our agreement.
• Working on integrating tooltips into graphics. Tricky because the only way to get the mouse position is by having a mousemove event listener and you don’t want one for every shape. Adding a “checkMousePos()” method to the PhysicsShape class that uses a sampled mouse pos from the containing class.
• Stuff to test

8:00 – 9:30, 12:30 – 5:00 SR

• Backups
• Deployed new FA and RA
• Going to try to add a profiling wrapper around queries that can be triggered to see what’s taking so long. See here for details.
• JavaScript
  • Adding events – done, though they are not YUI Events. Just added Y.fire and Y.on in the containing HTML
  • Adding tooltips – this is turning out to be hard. Shape nodes don’t seem to support tooltips, and many of the mouse events seem to be misbehaving. So I’m going to use my shape/div trick to build tooltips. I think opacity can be triggered using transitions, but if not, I can do something based on distance.
  • Adding arguments and defaults for size, color and line thickness – done

8:00 – 4:00 SR

• Backups
• Bugs/Comments
  • RA
    • Add ‘View FMP’ button next to ‘View Invoices’
    • Reported FACTS obligated is showing zeros.
  • FA
    • Non admins need to see the panel that clicking on a requisition line brings up, but they should not be able to edit.
    • Clicking on a line in the top panel of the ‘Financial View’ sould bring up the RA ‘Financial Data Entry’ panel
• JavaScript
  • philfeldman.com is now available through the firewall. And the MSD display is working
  • Add names (show/hide attribute) and tooltips (overlay)  next
    • Labels are working. In YUI you have to handle text as a <div>, since there is no support for text in YUI.Graphic class.
  • Size and color (normal, selected, hover?)  attributes, and initial arguments. Also could have default values this way.
  • Fire a “clicked” event for integration with application.

  DARPA releases open source code. However, some links seem to be broken.

8:00 – 4:00 SR

• Backups
• Deployed new FA
• more paperwork
• Talked to Chris about getting a new SA and finding out who our Security guy is.
• Status report.
• JavaScript
  • Got lines working. Since there does not seem to be a way to adjust the order of the nodes, I have to add the shape that represents the connecting lines before adding the shapes. THis means two passes in the initialization first the constructor loop, and then a loop where addShape() is called. Clunky, but it works. And here’s the result so far.

8:00 – 4:00 SR

• Backups
• More server paperwork
• Asked Dimitri to get some written justification for my change in compensation.
• Starting on a mass-spring-damper network display
  • Got shapes drawn and clickable.
  • Got early physics running.
  • Today’s work: http://philfeldman.com/TransformDrawingTest.html

8:00 – 4:00 SR

• Backups
• Deployed FA, RA, and RQ, with a new FA.jar and some new sql.
• Finally got isVisible working, but I’m not happy myNode.getAttribute(‘hidden’) should work, but doesn’t. myNode._node.hidden does. Totally undocumented yuck.
• Moving the developed code to CSSRemoteDataModule.
• Working on putting a Base module in a Panel.
• That was quicker. The root node that the panel connects to seems only to provide its size. Color seems to get lost, and you need a 50 pixel offset from the top for the title bar.
• 

8:00 – SR

• Backups
• Javascript
  • Still working out how CSS and YUI work together
  • Ok, figured it out. The css name must match the .js name which must be contained in a folder with the same name as well. See the picture below. Note that in the HTML code that the two “electron” modules are referenced with appropriate names and paths based on this pattern. Note that this is for the default (sam) skin, and might be adjustable with custom skin names/location
  • 
  • Tried to add charts to the new <div> elements but got a “TypeError: I is undefined combo” error when creating the chart. Posted to the forums.

7:30 – 11:30 SR

• Snow coming, so it’ll probably be short hours today.
• Backups
• Javascript – well, I moved the entire development environment to the laptop, but got hung up with Tomcat on my work computer not being seen by my home machine. And I need two screens. Grr. Picking it up tomorrow.

8:00 – 4:00 SR

• Backups
• Submitted paperwork (xacta) for new security plan.
• Javascript
  • Created a YUI Base module. Still trying to figure out what I did though.
  • This looks helpful: A Recipe for a YUI 3 Application
  • Adding attributes
  • Building Reusable Widgets with YUI 3
  • Gotr three instances of a module cross fading in kind of a clunky way. I think it’s time to add the data back in and see what breaks.

8:00 – 5:00 SR

• Backups
• Deploy
• Javascript
  • Created a module based on the YUIConf examples and was able to create a module that I could new(). Next will be to use Base.create to get at the lifecycle management. Then add the chart and table pieces back in.

8:00 – 4:00 SR

• Backups
• Went through the server registration process with Tim E.
• New swfs for everything
• We still have the clear problem with Reqonciler
• It’s possible to loose a floating panel if it’s dragged beyond a certain point.
• Change Complete/Due/Overdue to look at Planned, Obligated and PM Actuals only
• JavaScript
  • Turning code into a YUI module. Set up the module and created <div> nodes to attach things to and styled them.

8:00 – 4:00 SR

• Backups
• Tried to ping Tim E. Got ahold of him later. Will call around 8:30 tomorrow to walk through the paperwork.
• Server paperwork with Bill V.
• increased storage in MySQL, but we’re still having slow page loads on RA
• JavaScript
  • Break the ChartWithRemoteData3.html into files. Done, and took a detour into typescript. It’s just not documented well enough with respect to YUI (and it’s not at v1.0 either) to use without a struggle.
  • Tomorrow we’ll try to turn this into a proper YUI module
    • Need to create some additional <div>s for the components to attach too
    • Change the css so that it’s more generic.