Revised Project Plan

Project Name

C3DL test suite

Project Description

Create and implement an automated test suite which compares C3DL still frame render demos and a still frame pictures. Additional innovation will be required for the implementation of moving C3DL demos.

Project Leaders

Andor Salga
Catherine Leung

Project Contributors

Andor Salga
Catherine Leung
Carlin Desautels
Peter Leaning

Project Details

The project will require the initial step of porting Processing.js automated test suite created by David Humphrey. That will produce a framework for which the C3DL demos can be added. The framework will need to be tailored for the project needs, such as: moving demos need to be integrated, replacing Processing.js still frame demos with C3DL ones.

Project Plan

Goals for each release:

•  0.1: 
• Port Davids code 
• Integrate a C3DL demo
• Archive with git and github.com
• Integrate github with C3DL dev team
•  0.2: 
• Integrate all still C3DL still demos
• Streamline automation to developers needs
• Attempt method of including moving demos
•  0.3:
• Fully integrate existing moving C3DL demos
• Attempt personal demo.

Project News

C3DL lighthouse

•  http://c3dl.lighthouseapp.com/dashboard

Processing.js Repo

•  http://github.com/annasob/processing-js

Initial Project Plan

What is your chosen project?

If your reading this and haven't looked at my last post, my project is available here. All I can offer is a brief description of the project, I know it will require me to piece together an automated test auite to compare Mozilla's webGL implementation development with other possible implementations to ensure Mozilla's development doesn't slow. It will also involve some webGL demo creation. Unfortunately that's all I know for now. However a call next week with David's contact Vlad from Moznets #gfx channel.

What will your process be for doing this work?

As per the course requirements I will be doing three project releases, you can also keep track of my progress on my personal wiki. Important dates:

• 15% – 0.1 Release (Due Oct 22)
• 15% – 0.2 Release (Due Nov 16)
• 25% – 0.3 Release (Due Dec 7)

From my understanding the first release goal is to put out an automation tool. Refine it by the second release in addition to putting out a webGL demo. At the third release get an openGL control of a similar demo and comparison tools within the automation.

Plan for 0.1, 0.2, and 0.3 releases

For each release I will need expanding knowledge of HTML5 and it's canvas object in addition to Javascript for the suite and webGL for the demos. I'm not entirely sure what I'm doing or even how to do it. Dave simply pointed me in the direction focused on webGL research for now. He also suggested getting a web page up that uses webGL, even if its very basic.

Who do you need to know and who will you work with?

I'll have three main contacts my teacher David Humphrey, another knowledgeable professor Catherine Leung, lastly Vlad from #moznet. Other then these specific people I'll have access to #seneca and #gfx on irc. So far my conversations have been solely with Dave, with some supplemental lurking on IRC.

Collaboration and contribution? 

Other then these specific people I'll have access to #seneca and #gfx on irc. So far my conversations have been solely with David Humphrey. A phone call with Vlad will happen next week to help flesh out the project and deadlines. My project can help out any my colleagues playing any sort of video or animation using the canvas tag in HTML5. By utilizing my projects functions they should see serious performance gains. On the other hand it would be beneficial for me to get a hold of code used for similar systems so that I can adapt and learn from it.

What barriers stand in your way? 

I'm worried about simply juggling my projects this semester, but I guess baby steps in this new world will help me succeed. Possible risks include shear scope overwhelming me, so I would have to figure out a way to scale it down or scale is back into something more manageable. In order to lessen my risks I need to ask for advice from Dave and simply listen to his sugeestions in addition and applying it to Vlads vision for the project.

Nailing down an OSD project

After a fair bit of procrastination, and finishing other project proposals. The time came around to choose an DPS901/OSD600 project. After briefly going through the list of projects found here. I decided that having a paltry 12 projects to choose from wasn't quite enough.

After speaking to my teacher Dave on IRC I expressed my interest in WebGL, without hesitation David was hitting up his contacts and threw a brand new project to: create a webGL performance test suite. Now that sounds a little daunting. However with the #moznet community and David's guidance, I can't wait soak up these readings and get started.

Here is a list of reading sources thus far:
WebGL Wiki 
Learning WebGL Blog
Mozilla Dev Central WebGL
WebGL Mainpage

I haven't gone through every source in great detail yet. If anyone has more reading suggestions, comment!

Chrome experiments: A Bug's Life

Phase 2 of our: Firefox Performance Testing Lab

After narrowing down all the fun Chrome experiments which use the latest open standards including: HTML5, Canvas, SVG and more! Into significant test cases. That is where most of my class mates would experience our first taste of becoming a contributor to the open source community.

As you can see in my lab link students collaborated together and compiled our results in one place. From there we were on our own. However Not at all because D.Humphrey was available every step of the way to show us how a bug is filed or even if a bug a bug, along side all of the open source community at our finger tips.

My first bug available here. I filed a bug concerning the JavaScript engine when running this chrome experiment.
Steps to recreate:

1. Click launch experiment
2. Drag mouse across experiment window to give you something to bounce against
3. Turn up ball drop rate 15x

Interestingly within minutes of posting the bug and sending to Humph on irc he replied telling me the javascript for the experiment was out of date. So I downloaded the experiment and swapped out the JS with this one provided.

The end result? Minefield performed beautifully and all was well in the world. However I'm still watching the bug for updates to see how I can contribute.