Mike 11.23.09

  • Came up with a better way to send trend information to column renderers
  • Added threshold lines for every series to the charts and decided it was too much info at one time
  • Figured out how to draw directly on the charts and added threshold lines which appear when mousing over the data

Phil 11.23.2009

7:30 – 3:30

  • Finished up with the fixes to mvnAssist by adding support of the <classifier> tag to the local rep scan as well as remote repos
  • Working on making Ingest manager lay out better on smaller screens
  • Went to the S2F Thanksgiving lunch and deployed the new version
  • Tom is making good progress on getting mvnAssist to work with the new project. He’s through the Flex code and starting on the java.

Phil 11.20.2009

7:30 – 6:30

  • Deployed new banner version, so hopefully the domain people can add a “go visibility” redirect
  • Need to make the VISIBILITY2 banner shorter
  • Make the IngestManager panel a little shorter
  • Have the IngestManager use the same stylesheet as Vis2
  • Add color preferences
  • Fixed a bug in mvnAssist – needed to split off <classifier> data (i.e. “en_US”) from the name of the file in the repo

Phil 11.18.2009

8:00 – 4:00

  • Changed Basic and Advanced forms to use VDividedBox and fixed follow on formatting issues
  • Dong is adding a “Run Now” button to auto ingestor
  • Making some more slides for Boeing presentation
  • Helping Aaron with integrating CheckboxRenderer into Appboard
  • Deployed newest version

MvnAssist

  • Make it so “clear text” clears the console for the selected tab
  • Add “Step 1 of 3, 2 of, 3… to Create Project”
  • Keep from importing yourself in the pom navigator? Or at least post an alert with a warning
  • Do not inset multiple identical dependencies with pom navigator
  • Look for the [ERROR] string in the output. There are two cases. The first is where there is an error that does not cause a build failure. These should be stored in a list and sent to the “Problems” plugin. The other is an “[ERROR] BUILD FAILURE”. This should store the lines that follow the error and present them in a dialog.

Phil 11.16.2009

7:30 – 4:00

  • Spent most of the morning at the fort helping John W look at data. He’s becoming quite the power user of VISIBILITY2, using the advanced tab and typing sql. He wants more room for row selectino in the advanced tab
  • Talked to Charlie about putting together a proposal to mimic the enclave at edge – he’s working on it now
  • Putting together Boeing presentation
  • Showed Clift how to use EdgeUtils tree navigation tools

Mike 11.15.09

  • Started working on thresholds for trend widgets
  • Created a smart column renderer which changes color based on current value and thresholds, right now it’s a kind of ugly red, green, yellow thing but once I get everything working I’ll go back and make it take the default color and red shift it or something
  • Added some code to look for reserved column names and pull out thresholds

Phil 11.13.2009

7:30 – 1:30

  • Walked John through producing a report using the tool
  • Integrated my file-based spooler for mvn help:describe
  • Worked with Dong to find out why flexmojo is creating circular references

Phil 11.12.2009

7:30 – 5:00

  • Deployed latest version at the fort and turned off the old VISIBILITY app
  • Make it so “clear text” clears the console for the selected tab
  • Add “Step 1 of 3, 2 of, 3… to Create Project”
  • Keep from importing yourself in the pom navigator? Or at least post an alert with a warning
  • Do not inset multiple identical dependencies with pom navigator
  • Look for the [ERROR] string in the output. There are two cases. The first is where there is an error that does not cause a build failure. These should be stored in a list and sent to the “Problems” plugin. The other is an “[ERROR] BUILD FAILURE”. This should store the lines that follow the error and present them in a dialog.
  • Spent the rest of the day getting the flexbuilder plugin to actually get its help printed to the console window.

Phil 11.10.2009

7:30 -3:30

  • Needed to make a few changes to the details xml, but that was it. Autoingestors are working, proxy is behaving. Will take down VISIBILITY1 on Thursday
  • Fixed a subtle bug in tree view that would have redundant labels if the order of strings provided did not go from simpler to more complex
  • Adding backticks to quote out column headers so that they can be reserved words – done

Phil 11.9.2009

8:00 – 4:30

  • Spent most of the morning rearranging data (well, the names of the data, anyway) for Pat
  • Looked into why roles vanish sometimes. Barring learning something new tomorrow, it’s because when a new role is added, the old roles are deleted, which in turn causes the mapping tables to get deleted as well, since the numbers may change. IN other words, it’s a desired feature
  • Made it so that which tab is the default in the QueryBuilder settable by editing the setupXml file. Mike had a confusing experience, which we should keep from happening…

Mike 11.08.09

  • Was very confused about an error I kept getting when trying to build a basic chart, turns out “Details” is now the default selected tab in the query builder  instead of “Basic”
  • Modified TrendWidgets to run their own queries instead of directly taking data from QueryWidgets
  • Enabled saving / loading of TrendWidgets with all the standard features:
    • Query and trended rows saved
    • Column order and size saved
    • Selected column (for pie chart) saved
    • Current chart / table being view saved