8:00 – 3:30 VISIBILITY

• Working on mobile Flex  tutorial
• Brought Mike up to speed on the credentials issue.
• Displaying a Google map on an iPhone is more complex than you would think.
  • Or not? (http://cookbooks.adobe.com/post_Display_Map_in_iPhone_App-18959.html)
• Tour de Flex on iPhone!
• Got icons and splash screens working
• Just got a Google Maps key for fgmdev.com: ABQIAAAAdkcfcB4jtnPTDXu5jXoWURT49yoAjtLw-aX5iZ148rGTLLpumxTUDsWa-68C21ivHw9UTcIejRKXAw
  • Here’s the basic google tutorial: http://code.google.com/apis/maps/documentation/flash/tutorial-flex.html#DeclaringMaps
  • Here’s something from Adobe that explicitly addresses mobile: http://76.74.170.157/post_Google_Maps___Flex_Mobile-19132.html
• Finishing up e-Quip
  • Trying to figure out what to do with the signed forms
• Nothing new on site. Tried to get a hold of Jeff, but he was out.

8:00 – 4:00 VISIBILITY

• Finishing homework
• Trying a tutorial: http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex.html
  • Coming along well, but there is a problem in the tutorial code. When you go from using the HTTPService to using the <dao:EmployeeDAO id = “srv”/> declaration, you need to change the click response to the search button. I did this by creating a private method that took the ArrayCollection result and set the ‘data’ object equal to it. More tomorrow.
• Meeting with all the players in the problem server space. It looks like our SSL proxy server never existed, so instead we’re going to have to write some code that takes care of p12 credentials. Wrote up a note to Bill D. that explained this and CC’s to Brian.

8:00 – 11:00 VISIBILITY

• Checked in my changes
• Deployed the new version of VisibilityScriptingServer to fgmdev.
• Fixed (avoided, actually) a bug(?) setting(?) that had the mySql on fgmdev rejecting the hugedata table create command:
  • Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs
  • Lowered the number of columns from 300 to 150, and the problem went away. Dong did find that he could create the table outside of visibility_dev2. Neither of us is sure why that is, and have decided that it’s not worth pursuing.

8:00 – 5:30 VISIBILITY

• Working on the MySql packet issue: http://dev.mysql.com/doc/refman/5.5/en/packet-too-large.html
• This is where you put the option files for windows version of mySql: http://dev.mysql.com/doc/refman/5.0/en/option-files.html
  • It appears that for windows, the file is here: /Windows/my.ini
  • This didn’t work as I was starting and stopping mySql through the xammp control panel
• That didn’t work, possibly becayse of xampp? Added –max_allowed_packet=16M to the mysql_start.bat file
  • Didn’t work either
• Tried adding argument to /xampp/mysql – nope
• Ran the mysql_start.bat file from the command line. That worked, so there’s something that xampp is doing in the control panel.
• New error: 4484 [main] ERROR com.fgm.ScriptEngineServer.PublishSupportObject  – Data truncation: Data too long for column ‘content’ at row 1
  • Changing to table_publish.content to longblob fixed that. (alter table table_publish modify content longblob;)
  • Changed code to create content as a LONGBLOB
• Back to setting xampp service arguments. Trying /xampp/mysql/bin/my.ini And to be thourough, I’m going to bounce the box.
  • And that worked just fine. Whee!
  • Need to install changes on site and test. Done and working
  • Need to change code and settings on fgmdev. Done but not tested

8:00 – 4:00 VISIBILITY

• Working on VSS. I’m assuming that the problem has to do with the putting of large result xml in the database.
  • Added a PublishTest class. If run standalone, it will create a table (visibility_dev2.huge_table) of varchars, ints and floats that defaults to 300 columns by 1000 rows
  • got the error we saw yesterday: 13227 [main] ERROR com.fgm.ScriptEngineServer.PublishSupportObject  – Packet for query is too large (13226095 > 1048576). You can change this value on the server by setting the max_allowed_packet’ variable.
    • The above causes the sf.publishXml(“/hugetable.xml”, xmlStr); to fail, at the INSERT command in PublishSupportObject.publish()
    • XML is valid if written to a file.
    • Looks like the first thing to try is to set the packet size to 16,777,216 and see if that works

7:00 – 4:00 VISIBILITY

• Demo day. Need to deploy VSS and try to get some reports running
  • Got VSS running, though it choked generating data for the ingestor (Possibly not even getting so far as putting the data in a table). This could be due to the size of the table, or something having to do with the way the data was formatted – there were xml errors according to the browsers we used to view the data. Going to try making some large data sets tomorrow and then doing pulls against them to see what happens.
  • The demo went surprisingly well. The audience was eager to get their hands on the product and to extend it. We could be looking at a lot of work. We’ll see how the funding goes…

7:30 – 6:00 VISIBILITY

• Talked to Dong about what I saw on Friday. The problem as I saw it didn’t seem to appear, but there may be something tied up with the way the adjusted budget is retrieved?
• Updated VisibilityScriptingServer. Some weird problems with Tomcat that fixed themselves.
• Apple Store support at 5:00!
• Out at lunch to do parent financial stuff

FP

• Tom’s shipment from Sparkfun came in.
• Need to call Stewart about patent status 240 864 2420 – done. He’ll send a writeup of costs and the latest provisional
• New speakers appear to work really well

8:00 – 4:30 VISIBILITY

• Tried downloading xcode again. No luck. Took a screenshot of the app store and logs, and sent that along with the all the system logs that seem to pertain. Not impressed with Apple right now.
• Pinged Greg about getting BIAB footage. He thinks he can have it in on DropBox Monday. That’s a big file though… We’ll see?
• Spent. The. Entire. Morning. On the phone with Apple support.
• Deploying Dong’s fixes.
• Saw some odd behavior with how percentages were being calculated. It looked like the calculation was 100% – percentage, but I’m not quite sure. Will pull up a spreadsheet and check the numbers on Monday.

8:00 – VISIBILITY

• Gave Dong the screenshot printout with the notes from yesterday
• Going to try making an apple cert
  • Generated a cert request using the keychain  – and it has arrived!
  • Looks like you need xcode to get the device ID, and that’s not installing.