7:30 – 3:30

• Deployed data
• Working on search in AdvancedQueryWidget. Also did QueryWidget. Took a while to figure out how to set selected in a chart. Turns out you set the selected index of the series.
• Need to add column checkbox to ADG

7:30 – 4:00

• Deployed VIS1 & 2
• Talked to Mike C about putting “Current”, “stale” and “Obsolete” tags in a “Data Freshness” column in his data sources
• Sent a note of To Mike K about making a Pat display
• Talked to Dong about roles
• Caught up with Brian and Clift.
• AdvancedQueryWidget
  • Put new where clauses immediately after “where” – done
  • Add implicit “select”? – still thinking about this
  • Added the ability to set the query in the builder from an AdvancedQueryWidget
  • Getting loading and saving working
  • Need to have “setQueryBuilder” also set the table name. This requires adding table to QueryStringEvent – done

7:30 – 4:00

• No meeting today – put off until next week sometime
• Showed Anne the new stuff – her suggestions:
  • Have an indication in the chart as to what columns is being displayed
  • Populate the QueryBuilder from the loaded chart so that additional queries, based on the current query can be performed
• Back to AdvancedQueryWidget.
  • Got the date grid part working
  • Need to match up data types from the google types->primType->ColumnInfoObject
  • Integrating charts – things are displaying properly.
  • Need to get AdvancedQueryWidget to save and load properly
  • Need to change AdvancedQueryWidget so that the “and” clauses are inserted immediately after the where. See line 119 for details.

8:00 – 4:00

• Prepping for 10:00 meeting
  • There will be some kind of follow up meeting where I bring in a laptop to evaluate responses
  • Add search box for Inez. Done, but not wired to the datagrid/dataprovider highlighting yet
  • Didn’t get to AdvancedQueryWidget at all today. Try again tomorrow
• Stuff for Mike
  • Need a layout that has the query builder open with the appropriate boxes checked
  • Cascade layout should put panes back in their saved xy positions in addition to size
  • Column ordering is not saved (does not load in saved order)
  • Vertical scroll layout should adjust so that QueryBuilder does not obscure

7:30 – 5:30

• Deployed at the fort. Told Kathy W. and John W. that we’d have a better interface in about two weeks. Meeting tomorrow at 10:00
• Helped Dong fix his project
• Added user info to all remote object queries
• Back to advanced query widget
• Got most of the pieces put together. Need to extend QueryWidgetBase to AdvancedQueryWidget, and deal with columns and saving/loading

out sick

8:00 – 4:00

• Clear fluids today! Wheee!
• Deployed at the fort. Combined now ingests in a few seconds. Talked to Mike C about various issues. Tuns out that there was a bug in Mike’s code that generated spurious entries in the xml table.  The upshot is that we’ll wait to see how Anne likes the new data
• Talked to John W. He’s like a not from Brian about our burn rate and how it gets us through to October
• Working on Advanced Queries. Just realized that there is no equivalent for mySQL “discrete”. Goint to have to figure out a workaround. Not only that, but advanced queries can’t be the same as “normal” if this is the case. Hmmmm. Fixed by putting rows in a HashMap with their string values as the key

• Working on QueryInfoObject – finished the java side, mostly done on the flex side
• Started advanced tab in querybuilder – got to the point that A query is sent and the results come back and are visible in the debugger. For Monday, start transitioning over queryWidgets to use the google format and replace the whereClause code
• Talked to Anne for a while about the source for the combined.xml file. She’s going to talk to Mike C.

• Deployed data at the fort
• Started getting classification working. Managed to break the server (the jblocks jar is needed) so we punted for a while
• Lunch for Mike
• Working on getting the google API integrated
• Select Al button in Query builder is broken

• Deployed data at the fort
• There was a problem with the spreadsheet that we had uploaded. Fixed
• Got the google Visualzation data API working
• Walked Ines through how Vis2 works

8:00 – 4:30

• Had a long discussion with Mike about form input and building a more customized query.
• Thinking about making the query like what Lance and I were pondering on TUMMS – a Google-style interface(http://code.google.com/apis/base/docs/2.0/query-lang-spec.html)
  • a blank line would return all values in a table
  • the full or partial name of a column would return the values for the column (i.e. “bar” would return all the values of column “bar”, while “ba*” would return all the values for “bar” and “baz”.
  • the default search term (and the default) is “columns:”, which means return onlyt the values specified. The other option is “row”, which means to return all columns where the specified constraints are met. (“rows: foo[10]” would return all entries where the value for the columns “foo” is 10)
  • Brackets would constrain searches ( ba* [1..10] would return all entries of bar and baz that lie between 1 and 10 inclusive, while animals[kittens, puppies, ponies] would constrain the search to only those animals listed)
  • Searches could be combined so that ba*[1..10], date[1/1/1990..1/1/2000] would return all the values for bar and baz that are between 1 and 10 and were collected within the specified dates
  • The NOT operator “!” can be used to keep something from being returned (“rows: !ba*” will return the contents of the table without “bar” or “baz”, while “columns: !foo[10]” will return all vaues of foo that are not 10)
• Looks like there is a java API that supports this: (http://code.google.com/apis/visualization/documentation/dev/dsl_intro.html). Also, there is a nice video overview here: http://code.google.com/apis/visualization. It’s not quite what’s specified above, but it’s close, and it’s got MySQL support. Going to look more deeply tomorrow.
• Another useful link on same: http://ouseful.wordpress.com/2009/05/18/using-google-spreadsheets-as-a-databace-with-the-google-visualisation-api-query-language/