[Soc-2008-dev] Friday Reports!

Nicholas Bishop nicholasbishop at gmail.com
Fri May 30 09:32:11 CEST 2008

Here's my Friday report:

a) Previous week:
Did some prototyping work; I created a throwaway test using a
modification of the subsurf modifier to try out some of the ideas
outlined by Brecht for how the new multires modifier will function
>From that test, I committed a couple of very basic things to my branch
(boilerplate code for the multires modifier and a new customdata layer
for displacements)
b) Next week:
I need to do some more thinking about how sculpt mode will interact
with the new multires displacements, then run that by Brecht.
Displaying multires displacements is pretty easy; editing them is much
trickier, so I want to focus on that issue early on in the design.
c) I think I covered that above (editing of the displacements)
d) On schedule, I think. Doing the prototype probably didn't produce
much useful code, but it was very helpful for seeing where I'm going
and what problems are still unaddressed.


On Fri, May 30, 2008 at 2:45 AM, Chris Want <cwant at ualberta.ca> wrote:
> Hi folks,
> It's Friday, the day in which Friday status reports are
> required. I know this is the first week, so don't worry
> if you don't have much to show as you settle into
> Blender development, but it's still useful for us to
> ensure that you are all still responsive, and to
> try to work through any problems you might have.
> So, when you have a moment today please send
> a mail to this mailing list describing:
> a) What you did in the previous week;
> b) What you plan to do in the following week;
> c) Describe any issues you are having that may
> require extra attention;
> d) Let us know whether you feel that you are on
> schedule, ahead of schedule, or behind schedule. If
> you are behind schedule, please let us know what we
> can do together to get things back on track.
> Also, if you have a chance, please test committing
> to your subversion branches. I also feel compelled
> to offer some advice about open source development:
> commit often! At the very least it will give you
> a backup of your work, but even better it gives you
> an easy point you can roll back to if you find
> your development isn't going well. Another
> advantage is related to peer review: your mentor
> and other interested parties can examine and
> beta test your code and provide useful feedback.
> Best regards,
> Chris
> _______________________________________________
> Soc-2008-dev mailing list
> Soc-2008-dev at blender.org
> http://lists.blender.org/mailman/listinfo/soc-2008-dev

More information about the Soc-2008-dev mailing list