Gotta install sp2…. Well that was 20 minutes well spent! Wheee.
Working on multiple select = done. Leaving the single select code in place for a while out of, well, superstition and fear, actually.
I’m thinking about adding another chart that has the unique counts for each column – that way it would be possible to easily find out how many people we in a query, even if they had multiple skills. – done
Ingested data at the fort. Talked to John, who tried to find info with Pat yesterday. I said that the display is only as good as the data, but I don’t think it stuck.
Working on “Questions” interface
Modify – done
Add – done
Add as Child – done
Delete – done – turned out to be tricky. You have to use the delete operator.
Have “Set Query Builder” populate the _questionQuery.text field
Add a setTableQuestions(String questions, String tableName) method in DbRemoteObject that a) Creates a table_questions table if there is none, and b) loads the xml as a blob in the table row (note: only one set of questions per table) See the dashboard entry for how to handle xml – done
Add a getTableQuestions(String tableName) method in DbRemoteObject that a) Creates a table_questions table if there is none, and b) either returns the xml if it exists or returns and empty <questions/> xml string. – done
Deployed the new version with Mike’s fixes. Everything seems to be working fine
Talked to Anne about building special-purpose tables from the master table to make it easier to explore the data
Floated the question idea
Realized that we could also have all the available strings in a column listed in the (a?) hierachy view, so some level of drilldown could be available…
Changed all query double quotes to single quotes
Phone call from Anne – Meeting with here and John on Thursday. Might have a version by then.
Started on the question tab, mostly because it’s an easier problem to solve that might give us what we want. Go the part where you can click on a tree component “question” that runs a query.
Need to be able to interactively build the xml
Need to save the xml in a table-specific entry (only one entry per table holding the xml)
Allow users to delete their dashboards (from the save menu)
Start up in ‘Builder’ layout
If nothing is selected, have a popup that says “No items selected for query” (done in adv and basic query widget, querybuilder defaults to select * so I didn’t change that)
Don’t allow components (particularly minimized windows) to go behind the top “VISIBILITY2” UIComponent
Resize events on the builder window should re-trigger the layout (Only occurs when in builder layout)
Deployed the latest attempt at the fort and it seems to be working well. Uploaded new data
Trained up Anne and John on the new features. Based on their suggestions, here’s what needs to be added
Allow users to delete their dashboards
Start up in ‘Builder’ layout
Update tips
Add tips to the IngestManager
If nothing is selected, have a popup that says “No items selected for query”
Provide direct transition from minimize and maximize
Don’t allow components (particularly minimized windows) to go behind the top “VISIBILITY2” UIComponent
Resize events on the builder window should re-trigger the layout
Automatically scroll to the selected item in a search on a datagrid
Add a “Suggestion Box” under Utils that’s like the old bug reporter on TUMMS
Architecture (get aquainted session?) in Fairfax. Ran a little long. Note. If you leave VA at 3:15 on a Friday, it can take ’till 5:00 to get back to Laurel.
