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.

8:00 – 2:00,  3:00 – 5:00SR

• The weather word for today is “ick”.
• Backups
• No word back from Tim E.
• Add “only show if conflict” as a line choice in Reqonciler.
• Timesheet crap.
• Email chain with Brad about how to move off of fgmdev.
• Lunch at 2:00.
• It looks like the POST configuration can be set up in datasource-io, since there is an ioConfig attribute (http://yuilibrary.com/yui/docs/api/files/datasource_js_datasource-io.js.html#l56). Going to set up the servlet to listen to POST as well and see what happens when I send data. This is the io-base example that seems to be appropriate: http://yuilibrary.com/yui/docs/io/
• Wow. That worked! Need to sent the argements over correctly, but the response is already coming back ok.

8:00 – 4:30 SR

• Backups
• Deploy new FA, RA, RQ
• Truststore issue *is* fixed!
• Pinged Tim E. To get renewal process restarted.
• Javascript
  • Allow changing of arguments to servlet
    • Pretty straightforward. When setting up: myDatasource = Y.DataSource.Get({source: ‘http://target&&#8221;});
    • When using: myDataSource. sendRequest{request:”any&arguments&here”, callback:myCallback});
  • Comment everything! First pass is done. Need to walk through with Dong to see what’s not clear.
  • Commit codebase. Done
  • Starting an example that uses the DataSource.IO capability, which appears to be more powerful and more secure. Good example here: http://stlsmiths.github.io/blunderalong/dt_json_dsio.html
    • Got that working, but it’s still based on GET, which means the argument still will need to be mangled. How do you do POST?
  • Might have to use io-base to use POST?
    • http://yuilibrary.com/forum/viewtopic.php?p=29652
    • http://yuilibrary.com/yui/docs/io/#the-configuration-object