[Bf-committers] New Transform patch.
joeedh
joeeagar at prodigy.net
Sat Feb 26 03:52:54 CET 2005
Don't forget that I was, how did the meetings notes put it, "Martin's
'sidekick'" at the beginning of this project? I've since dropped out,
but I'm not foreign to the code. I did, after all, port over the
transdata conversion code :)
And I even wrote the first version of the scale function, but it was a
little too messy (I couldn't isolate exactly how the code worked at
first (the old code in editobject.c was way too messy) so while I did
end up with the exact same functionality, it took a *lot* of trial and
error and by that time the function needed to be rewritten. Which is
why theeth rewrote it :) ).
And yes, I know I contributed some fairly bad code back then, but
everyone makes mistakes, and in that case I was basing my solutions off
of the old transform code :)
And I'm not very good at describing things like what my patch does. .
.it makes your objects go along the axis closest to the mouse cursor,
but as your still in middlemouse-click mode. . .you click and drag along
the appropriate axis. . .I don't know. But I at least thing it's useful.
joeedh
Chris Burt wrote:
> Joeedh,
>
> I'm sure your help is greatly appreciated but in this instance I think
> your effort is slightly misplaced. There are already two *very*
> talented coders dedicated to this project, am I'm not so sure that
> submitting patches for this code set (which changes every day) is the
> most productive activity right now. Perhaps once things have been
> stabilized/finalized it would be a better time to take it upon
> yourself to work on it, but my guess is, Martin and Ton aren't
> currently accepting patches for the functionality of the user
> interface at this point.
>
> What may be a bit more helpful would be: document the change you think
> is necessary (certainly include your patch, since you've already made
> the effort, albeit at a bad time) and give the reasons why you think
> this change should be made. Unless I missed something, your post is
> very vague and gives a developer little reason to even review the
> code, never mind put it to use. Especially given that the two people
> working on this project are *very* busy working on some specific (and
> very important) goals.
>
> I'm not trying to bash your efforts, or discourage you from
> participating at all, I just think that perhaps you should consider
> this area of the code "off limits" for a while while the pros take
> care of things there. Right now there is just too much work in
> progress to be submitting patches for features that aren't even
> *close* to finished. It would be as though you started hanging
> pictures on the wall before the plastering is done, if you get what I
> mean :)
>
> So! I hope I'm not overstepping my bounds with this suggestion. You
> obviously want to make productive use of your time in your work on the
> sources, and I'm merely trying to prevent you from expending effort on
> things that don't get the attention they would normally deserve. In
> short: Keep up the hard work, but its probably best to leave the
> transform code alone for awhile :) Thanks!
>
> Regards,
> --Chris
>
> joeedh wrote:
>
>> joeedh wrote:
>>
>>> Hi. Here is a patch that makes it so that constraints in the new
>>> transform are enforced as you're picking them. I find this to make
>>> the new middlemouse constraint picking to be a lot more useable.
>>>
>>> joeedh
>>
>>
>>
>> Oops, made patch off of HE Mesh sourcebase. This new one is from a
>> fresh CVS download.
>>
>> joeedh
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
More information about the Bf-committers
mailing list