Starting to combine the panel and the table/recordset. It’s going pretty smoothly. I’m still using the data array, but I’ll move to more form-based data tomorrow or wednesday. Nicely, the height of the panel resizes based on what’s in it. And I should be able to use the same module for the login form.
Starting Funding Request Form. I’m currently thinking that a YUI recordset might be a good way to do this. Got the recordset demo working fine, but the implementation is basic HTML table manipulation. Now, that’s not necessarily a bad thing – it just means that there needs to be a module written to handle that. I’m not sure that it’s a big win over DataTable, which is part of the forms example.
First draft of the cluster analysis tool is done. Need to add user-supplied similarity function, some graphics options (more shiny – less shiny slider?), and change the output to have a csv compatible output
The test server appears to run at 30% the speed of the integration server. I wrote up a small executable that will run a system call in a specified loop and time the result (the default is “cd .” 500 times. It takes 8.64 seconds on my dev workstation 21 seconds on the laptop. Should be interesting to see what the servers do.
Set selected id to the UUID for the THREE object3D.
Adding animation for changes in height, inner radius and outer radius. The callout for the name is getting changed to the original name whenever height or radius is changed.
And here’s how you use textures to exchange gpu calculation: http://stackoverflow.com/questions/22940678/reading-data-from-shader
Integrating wedge size adjustment – animation, tooltips, add and delete, and rippling across all the wedges.
Got size adjustment working, but timing is off? Fixed.
Adding wedges is done.
Rippling is done.
Working on deleting wedges. Done, but there are some artifacts. Select doesn’t work the first time on post-deleted wedges. Auto naming is too naive – we can get multiple “Pie Chart 3”, for example. There needs to be an overall count or id field.