<div dir="ltr"><div><div><div><div><div><div><div>Hi all,<br><br></div>== Week 11 ==<br></div>Not much progress to report, as this was quite a busy week at uni - the annual departmental postgraduate students conference was on in second half of that week, and I needed to give a presentation there.<br>
<br></div>== Week 12 ==<br></div>I managed to fit in a bit of work on bits and pieces of depsgraph work, but a heavy writing+coding workload for uni work took up almost all my time that week again. Also, started discussing overall design with Sergey.<br>
<br></div>== Week 13 - This Week ==<br></div>Starting a few days ago, I now finally have time to seriously work on Depsgraph stuff again (at least until the end of GSoC period, and then some ;)<br></div><div><div><div><div>
<div><div><br></div><div>I started by taking stock of the tasks which still need to be done in order to start integrating the new Depsgraph module with the main Blender codebase. In particular, I've divided the work into several categories:<br>
</div><div>1) Before Integration Todos - Minimal Depsgraph Functionality/Core Code in Place. To keep things manageable, this means that some of the more problematic areas in Blender will be left alone for now (see Part 3) so that we can concentrate on ensuring that the core parts are put in place and holding well.<br>
</div><div>2) Integration Todos - Things like resolving compiler errors/typos, adapting evaluation functions (i.e. those called via object_handle_update(), but also the ModifierTypeInfo->updateDepsgraph() callbacks), replacing existing evaluation system entrypoints with our new system<br>
</div><div>3) Post Integration Todos - These are things we won't get around to before the end of GSoC. Coding final solutions for the issues in this category (e.g. proxies, instancing, metaballs) will have to wait a bit - there are various bits and pieces we can put together in the new system to eventually resolve these issues, but dealing with each one is itself quite a challenge.<br>
<br></div><div>Accomplishments so far:<br></div><div>- 1/3rd of the before integration todos complete. Of the remaining parts, most should be quick to blast through, while one or two will require a bit more work. Namely, fleshing out the details of evaluation contexts and feeding nodes to the scheduler - will be discussed with Sergey some more in coming days.<br>
</div><div>- I'm currently in the process of cleaning up compiler errors in the code (2.5/5 source files done atm), and collecting a list of stubs for evaluation callbacks which need to be implemented. <br><br></div>
<div>
== Next Week ==<br></div><div>I'll try to get things as close as possible to a basic "running" state (albeit, only with a very limited "safe" feature set), which we can start to seriously flesh-out post GSoC.<br>
<br><br></div><div>Regards,<br>Joshua<br></div></div></div></div></div></div></div>