<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#ffffff" text="#000000">
<small>Hi, Blender Community!<br>
<br>
I'm still wirking under camera tracking integration project and
here's some small progress for this week</small><br>
<blockquote
cite="mid:BANLkTinNBdYR2pm3b8N-M-ijAGc+5Yq6AQ@mail.gmail.com"
type="cite">
<pre>1) what you did this week
</pre>
</blockquote>
<small>- fixed some bugs, small optimizations<br>
- removed all that modalities from clip editor interface. toolbar
is for tools, properties panel is for properties. all avaliable
tools are visible on the screen<br>
- markers are now could be placed with ctrl-click<br>
- added marker preview area<br>
- option to make makrer thin. it's more a development feature, not
sure it'll be useful for artists.<br>
- option to display track path<br>
- "view selection" operator and "lock to selection" option<br>
- backwards tracking</small><br>
<small>- Remove all "modal" things like active tool and mode. They
aren't so useful as I thought when was starting implementation of
UI. Toolbar (T-panel) now contains tools only, no
options/properties there. All properties are moved to properties
panel (N-panel).<br>
- Convert track to location fcurves for object in 3d world. 1
pixel on footage is equal to 1 Blender unit. </small><br>
<blockquote
cite="mid:BANLkTinNBdYR2pm3b8N-M-ijAGc+5Yq6AQ@mail.gmail.com"
type="cite">
<pre>2) what you will do next week
</pre>
</blockquote>
<small>i've got some request like marker's area resizing with LMB
without doing this annoying area selection and some more usability
requests. Still have to investigate Peter's proxying/caching patch
and implement smarter caching which currently could eat all
memory. Also reconstruction could arrive soon from libmv side.
Also we could start implementing real parenting of objects to
tracks. <br>
</small>
<blockquote
cite="mid:BANLkTinNBdYR2pm3b8N-M-ijAGc+5Yq6AQ@mail.gmail.com"
type="cite">
<pre>3) any problems that will require extra attention and the impact on
your proposed schedule
</pre>
</blockquote>
<small>There's still no showstoppers. Maybe sometimes restrictions
of Blender design, but it could be usability problems only which
wouldn't really hurt workflow (like buttons refreshing during
playback and so). </small><br>
<br>
<small>More info here:
<a class="moz-txt-link-freetext" href="http://wiki.blender.org/index.php/User:Nazg-gul/GSoC-2011#Week_4:_13th-19th_June">http://wiki.blender.org/index.php/User:Nazg-gul/GSoC-2011#Week_4:_13th-19th_June</a><br>
<br>
And new screencast is here: <a class="moz-txt-link-freetext" href="http://vimeo.com/25233701">http://vimeo.com/25233701</a></small><br>
<small> </small>
<pre class="moz-signature" cols="72">--
With best regards, Sergey I. Sharybin</pre>
<br>
</body>
</html>