mouse-lock for Mozilla is being implemented by our class (dps909 – open source development, Seneca @ York 2011) and its very interesting that our class will be the one who created this feature. this feature will be useful for online gaming in “full-screen” mode and maybe more. I believe since we are developing it in Firefox 11, that that’s when it would be available to public. that is if all the specs will be correct, the tests will pass, and a review on it would be done.
bug 1376 update
after analysing the code and understanding where things are and what calls what, i have finally made the mouse dragging stop working when moving out of the canvas. however, there is still some little problems that can still be worked on to make it perfect.
build part2
i tried to play with the different options with mozconfig file and made it have only one line of code “echo “# My first mozilla config” and i didnt add any “mk_add_options” commands and surprisingly the built was much faster then having the commands
firefox build
SWEET! i have completed firefox built and it worked the first time on a windows platform .. took a while to read and understand what im doing and downloading a few missing files and programs but in the end it worked! im glad i have a very good laptop with lots of ram (8gb) and quad core to make the build quicker then on other computers. what i learned during this build is that if it says “optional” beside a heading it means you still have to do it 
project 0.2
the past few weeks i was trying to make mouse dragging work. however, it didnt work so well so far. trying to learn javascript and how it works is not as easy as to understand other code that i have done before. things i tried to do so far to make mouse dragging work:
1) i was trying to understand how the code works so i was playing with the lines of code by commenting them and seeing what they were doing.
2) try to see where the mouse is located but realized canvas only knows the mouse handler when its on the canvas.
3) i tried to make on mouse out remember the location of the mouse and when re-entering check if the mouse is clicked or not.
this didnt work or maybe i dont know enough of the code to make this part work. since when i was working on this the handler didnt trigger when i was going back on canvas.
so basically it was thinking the user was letting go og the mouse button when scrolled out.
what i still have to do is still to work this out and maybe i will be able to make this work somehow hopefully soon.
bug #1376
the bug that im working on is #1376. the problem is while pressing the mouse and moving around in the canvas then scrolling out of the canvas and releasing the mouse button and then scrolling back in the canvas, the canvas still thinks the mouse button is pressed. since im not ready to code and executing the code yet since im just getting to know how to use git and the project it self i will make my solution idea in this blog post. the solution im thinking about is that when a mouse is dragged outside of canvas it will assume that the mouse is still pressed but when the mouse will be scrolled over the canvas again there will be a check if mouse is still pressed, if so continue as it is pressed, if not then the mouseDrag should stop working.
getting to know GIT and project details
set up my git account today. it was harder then i thought to set up and to make sense to me. during class watching the professor work on git he made it look really simple. but now im slightly getting the hang of it.
the project i chose was processing.js and the ticket/bug im working on is #1376 which is ”mouseDragged continues after mouse released outside canvas”
back to IRC to get a project
i went back on to IRC and started to talk on the channel processing.js. I asked a little about the project and was linked to a brief description of the project. I was still interested in this project after reading the description and asked what should i do if i wanted to start helping out in this project. “jbuck” helped me out setting up an account on lighthouse and offered to help me if i have any other questions. my experience with IRC was much better this time around. now the only thing that is left to do is to find a bug to work on and try to understand code and the logic of other people who coded that code and try fixing it.
IRC – chatzilla
my experience with IRC wasn’t to bad. getting on connecting to different channels was easy. however, when people talk about the project that you know nothing about and not sure what they are talking about, starting a conversation with them was harder then i thought it would be.
DPS909 – open source
starting open source development course at Seneca @ York
posts about my progress in this course will follow soon
