[Soc-2013-dev] Weekly Report #4 Motion Tracking

[Ton Roosendaal]

Hi Joseph,

Without a single commit in svn I cannot monitor progress.
I heard Keir (mentor) wanted you to put things in review tracker first, but I think that's a waste of your svn space to not use it for daily committing.

I propose you use svn very frequently, and put things in codereview when ready for review.

Your comments about slow compiles I don't get either. You can configure cmake on a slow system in a way it compiles a single C file, and then links it all in seconds. Ask in IRC for help.

Questions about proper UI signals for refreshes you can get answered in IRC too.

-Ton-

--------------------------------------------------------
Ton Roosendaal  -  ton at blender.org   -   www.blender.org
Chairman Blender Foundation - Producer Blender Institute
Entrepotdok 57A  -  1018AD Amsterdam  -  The Netherlands



On 13 Jul, 2013, at 1:42, Joseph Mansfield wrote:

> =This week=
> 
> I started with some testing of my focal length constraint solution. You can see the results from one clip here: http://wiki.blender.org/index.php/User:Sftrabbit/GSoC_2013/Documentation/Constraint_Tests The results show that it's working correctly! Unfortunately, this particular clip doesn't really need the constrain to be solved well, so I'm hoping for some more challenging footage soon, which I will also test.
> 
> The camera focal length field in the UI currently has the ability to view it as both millimeters and pixels, but my constraint minimum and maximum values were always shown as pixels. Since millimeters are generally more useful, I added units there too. After a code review, it seems that it makes more sense just to have the units match with the selection for the focal length, so I've done that instead now.
> 
> Following this change, there were also a few other things to clean up that were brought up in code reviews (it seems to be endless!). The automatic indentation from my editor keeps deciding to screw me over, because I'm working in Python, C, and C++ files and it gets confused. Most changes were just a little refactoring or documentation to make it neater.
> 
> An important step was made this week that should improve my productivity - I got a new laptop! My previous one would take 30 minutes to compile and prevent me from doing anything else while it was doing so. Not fun! I did have to spend some time getting set up with compiling Blender on this new machine, but got there eventually.
> 
> =Next week=
> 
> I've just started writing up a document about something that I find confusing in the current code which I think could be refactored. I'll finish doing that and hopefully discuss it with Keir. Then once I've made the changes based on that, I should hopefully be ready to commit the focal length constraints.
> 
> =Questions=
> 
> I need to figure out how to refresh one panel in the UI when an option in a different panel has changed. I'm pretty sure I can use notifiers for this, but I'll need to do some research (I've not used them yet).
> _______________________________________________
> Soc-2013-dev mailing list
> Soc-2013-dev at blender.org
> http://lists.blender.org/mailman/listinfo/soc-2013-dev