User:Sdowne/summer 2010 worklog june

Tuesday June 1st

• Worked with notmasteryet thorugh irc on new lightweight parser . I merged the current parser work into a working copy of 0.9.3. This would include the word done on 0.9.1, and anything that was staged in 0.9.3 up to that point. I had to do a few tweaks to make everything work, and I had to fix one small bug with array parameters defined inside a function definition, using the [] after the name, instead of the type caused an error.

Wednesday June 2nd

• Fixed an issue with spaces before the int in a for loop --> for( int i;m in the new parser.
• Set the super review process for the new parser.
• I really did spend a lot of time just trying to read, and understand the new parser.
• Went through what is left for 0.9.3 and picked up a couple tickets 611 and 368

Thursday June 3rd

• Did an initial attempt on 611.
• Did and created a test for 368.
• Continued work with notmaster to get the light parser finished by helping to track down trace issues, and issues with brightness2 example in chrome not user getters and setters as fast as ff.

Wednesday June 4th

• Found an issue with opera not working on linux, as version 10.10 does not yet exist for Linux, and only 10.10 has support for string.trim. Had to add string.trim. The fix was easy... getting there was not.
• Coded a fix for the light parser to use static variables inside classes that have yet to be created into an object. This fixes the neighborhood test. The way it was working before was the static variable would not exist until atleast one object was created from the class, but it should allow use of static variables before that.
• and fixed a few of the smaller issues in the light parser's review.

Monday June 7th

• I did review of tickets 400, 706, 392 and 55. These were all in the same branch, so they were tested at once.
• I reviewed anna's xml ticket.
• Reviewed 596.
• Created a demo for tagging people in html5 videos for tomorrow.

Tuesday June 8th

• Worked with Brett and Dave at Mozilla to do requirements gather for the video.js project. This project is going to be quite small when it comes to code, but working on getting the details of the library just right seems to be something I get hung up on. Not that the finer details should not be talked about, I just have a hard time with it. We did get a lot done, and I did get some good direction about the details of the code, I just feel the large picture is too much for me to grasp, and I need to break it down and focus on one issue at a time. Just how I work best, and it's what I bring to the table. Either way, we won't get this right the first time, and will have to work with Brett and the community as it grows.

Wednesday June 9th

• At Mozilla working with Brett. I spent most my time figuring out how we are going to do the basics of this project. We have three things: 1. an xml parser of some sort. 2. Loading external xml files instead of putting them in the video tag. 3. Wrap everything inside a closure. 4. Still making using this easy form the html perspective. Using this should be simple, and it should be a matter of linking to the video.js library, writing an external xml file, and linking to that file in the video tag as some sort of source. The rest should be handled in the library, while still doing the above step I worry about, like closure, parsing, etc.
• I also did some time talking to Brett, getting to know him, and where he's coming from for this project.

Thursday June 10th

Friday June 11th

Monday June 14th

• I had a meeting with Dave and Dan about our javascript video library popcorn.js. It went well and I got a better understanding for what I am responsible, and this allows me to have a greater degree of focus for my work. I work bets this way.

Tuesday June 14th

• I cleaned up my popcorn branch. The problem was I started over again, and had my work on a new tree, but I didn't consider the previous history for the project, so I cleaned it up, pushed it into the old tree, and updated everything.
• I added some new functionality to the popcorn parser. The parser now does what it did before, but it contains properties passed down by parent elements, along with not using a single regular expressions. Instead, I am using the xml dom object tree, and I transverse through that using a library, much easier.