The FT_UInt was already there (and seems like a simple type). If you have some bleed through, in the same function declaration, then having some for freetype basic types seems like less of an issue. It looks like this class could do with some attention though, and I was hoping to improve the font metrics that I was seeing issues with.<div>
<br></div><div>Marcus<br><br><div class="gmail_quote">On Tue, Jul 6, 2010 at 2:01 PM, Michael Halle <span dir="ltr"><<a href="mailto:mhalle@bwh.harvard.edu">mhalle@bwh.harvard.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The previous bleed through was for complex types, though, and it looks like the new ones are for things like "FT_UInt32", which could replaced with standard ones with only hypothetical danger.<br>
<br>
--Mike<div class="im">
<br>
<br>
On 7/6/10 1:55 PM, David Cole wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
If there's pre-existing bleed-through, then there's not really a good<br>
reason to object to this particular patch.<br>
<br>
On Tue, Jul 6, 2010 at 1:51 PM, Marcus D. Hanwell<br></div><div class="im">
<<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a> <mailto:<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>>> wrote:<br>
<br>
Possibly not, but that prototype already has freetype definitions in<br>
its public methods. I think as a bug fix this is reasonable, but<br>
perhaps this class should be overhauled. This is another area where<br>
code review really helps as a part of the process. In the short term<br>
I would rather improve the unicode support, unless you strongly<br>
object to the patch.<br>
<br>
Marcus<br>
<br>
On Tue, Jul 6, 2010 at 1:43 PM, David Cole <<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a><br></div><div class="im">
<mailto:<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>>> wrote:<br>
<br>
Maybe it's just me.... but I don't think we should be using<br>
freetype type definitions as argument types in public VTK methods.<br>
<br>
Does that concern anyone else that we let implementation details<br>
bleed into the API? Or is it just me?<br>
<br>
<br>
Thx,<br>
David C.<br>
<br>
<br>
On Tue, Jul 6, 2010 at 1:25 PM, Marcus D. Hanwell<br></div>
<<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a> <mailto:<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>>><div class="im">
<br>
wrote:<br>
<br>
On Tue, Jul 6, 2010 at 1:13 PM, Marco Nolden<br>
<<a href="mailto:m.nolden@dkfz-heidelberg.de" target="_blank">m.nolden@dkfz-heidelberg.de</a><br></div><div><div></div><div class="h5">
<mailto:<a href="mailto:m.nolden@dkfz-heidelberg.de" target="_blank">m.nolden@dkfz-heidelberg.de</a>>> wrote:<br>
<br>
On 07/06/2010 06:11 PM, Marcus D. Hanwell wrote:<br>
<br>
I would prefer publishing on a public repository,<br>
but am not informed<br>
about pull requests on Github/Gitorious. I would<br>
certainly preserve<br>
authorship information, and recently integrated a<br>
patch from David Feng<br>
with preserved authorship. We also worked with David<br>
Gobbi on the<br>
wrapping branch.<br>
<br>
<br>
I think pull requests in GitHub are just an easy way to<br>
send a link to people with write access, without much<br>
functionality. Gitorious' merge requests are public,<br>
they have a status and the possibility to comment, e.g.<br>
<a href="http://qt.gitorious.org/qt/qt/merge_requests" target="_blank">http://qt.gitorious.org/qt/qt/merge_requests</a><br>
<br>
<br>
Yes - I have been using merge request on gitorious, and<br>
would favor this as a public list we could view, and comment on.<br>
<br>
<br>
<br>
Sorry if I missed this one, the change looks<br>
reasonable and I can take a<br>
look at it. It would be good to see improved unicode<br>
support too. It is<br>
something that the ARB should probably be<br>
discussing, but it would be<br>
great to involve the community as far as is possible.<br>
<br>
Marcus<br>
<br>
Actually I revised it a bit, so the link is here:<br>
<br>
<a href="http://github.com/nolden/VTK/commit/9b76af72e6016fcd4a7b2e1a58edb77eb5549eef" target="_blank">http://github.com/nolden/VTK/commit/9b76af72e6016fcd4a7b2e1a58edb77eb5549eef</a><br>
<br>
and the patch is attached.<br>
<br>
<br>
There were some trailing whitespaces added, I have removed<br>
those and rebased the commit on master HEAD. I will rebuild<br>
and test this out, but at first glance it looks good. I just<br>
added your remote in the end, and fetched from that. I will<br>
see about adding some regression tests for unicode text<br>
rendering.<br>
<br>
One of the benefits of Git is the ease with which patches<br>
can flow, I definitely want us to take maximum advantage of<br>
that. We are still looking at what the best ways to achieve<br>
this are.<br>
<br>
Thanks,<br>
<br>
Marcus<br>
<br>
<br>
On Tue, Jul 6, 2010 at 12:06 PM, Moreland, Kenneth<br>
<<a href="mailto:kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a> <mailto:<a href="mailto:kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a>><br></div></div>
<mailto:<a href="mailto:kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a><div class="im"><br>
<mailto:<a href="mailto:kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a>>>> wrote:<br>
<br>
Is submitting patches to the mailing list now<br>
the officially<br>
sanctioned method of providing contributions (as<br>
opposed to<br>
publishing on a public repository such as Marco<br>
has done)? Will<br>
this change in the near future when we plan to<br>
move to a branchy<br>
workflow (which as I understand it now has plans<br>
for a more open<br>
“staging” repository)?<br>
<br>
Perhaps this would be a good topic for the next ARB.<br>
<br>
-Ken<br>
<br>
<br>
<br>
On 7/6/10 7:38 AM, "Dave Partyka"<br>
<<a href="mailto:dave.partyka@kitware.com" target="_blank">dave.partyka@kitware.com</a><br></div>
<mailto:<a href="mailto:dave.partyka@kitware.com" target="_blank">dave.partyka@kitware.com</a>><div class="im"><br>
<<a href="http://dave.partyka" target="_blank">http://dave.partyka</a>@<a href="http://kitware.com" target="_blank">kitware.com</a><br></div><div class="im">
<<a href="http://kitware.com" target="_blank">http://kitware.com</a>>>> wrote:<br>
<br>
The most visible way is to send a patch to<br>
the vtk list. If you<br>
use the git patch commands you can create<br>
patches that will<br>
preserve the author (Marco in this case) as<br>
git has separate<br>
Author and Committer fields. See this wiki<br>
at the bottom on how<br>
to create a patch.<br>
<br>
<a href="http://vtk.org/Wiki/VTK/Git#Submitting_a_patch" target="_blank">http://vtk.org/Wiki/VTK/Git#Submitting_a_patch</a><br>
<br>
On Tue, Jul 6, 2010 at 9:24 AM,<br>
Jean-Christophe Fillion-Robin<br>
<<a href="mailto:jchris.fillionr@kitware.com" target="_blank">jchris.fillionr@kitware.com</a><br></div>
<mailto:<a href="mailto:jchris.fillionr@kitware.com" target="_blank">jchris.fillionr@kitware.com</a>><div class="im"><br>
<<a href="http://jchris.fillionr" target="_blank">http://jchris.fillionr</a>@<a href="http://kitware.com" target="_blank">kitware.com</a><br></div><div><div></div><div class="h5">
<<a href="http://kitware.com" target="_blank">http://kitware.com</a>>>> wrote:<br>
<br>
Hi Folks,<br>
<br>
Since VTK souce code is available using<br>
Git, the repository<br>
can be forked very easily and people can<br>
contribute quite<br>
easily.<br>
<br>
Being also available on github, Marco<br>
from DKFZ (German<br>
research cancer institute) forked it and<br>
added a patch. As<br>
he mentioned, "Pull request" doesn't<br>
seem to "work". What<br>
could be the best way for him to share<br>
his patch.<br>
<br>
Beside of the following page<br>
<a href="http://www.vtk.org/VTK/project/getinvolved.html" target="_blank">http://www.vtk.org/VTK/project/getinvolved.html</a> ,<br>
Is there any documentation available<br>
regarding the<br>
"contribution" workflow ?<br>
Is the mailing list the preferred way to<br>
share contribution ?<br>
Will the ownership of the original<br>
"patcher" be maintained ?<br>
<br>
I added Marco in CC, feel free to answer<br>
that email and let<br>
him know the best way to share his work.<br>
<br>
Thks<br>
Jc<br>
<br>
<br>
---------- Forwarded message ----------<br>
From: *GitHub* <<a href="mailto:noreply@github.com" target="_blank">noreply@github.com</a><br></div></div><div class="im">
<mailto:<a href="mailto:noreply@github.com" target="_blank">noreply@github.com</a>><br>
<<a href="http://noreply" target="_blank">http://noreply</a>@<a href="http://github.com" target="_blank">github.com</a> <<a href="http://github.com" target="_blank">http://github.com</a>>>><br>
Date: Wed, Jun 30, 2010 at 9:17 AM<br>
Subject: [GitHub] nolden sent you a pull<br>
request from nolden/VTK<br>
To: <a href="mailto:jchris.fillionr@kitware.com" target="_blank">jchris.fillionr@kitware.com</a><br></div><div class="im">
<mailto:<a href="mailto:jchris.fillionr@kitware.com" target="_blank">jchris.fillionr@kitware.com</a>><br>
<<a href="http://jchris.fillionr" target="_blank">http://jchris.fillionr</a>@<a href="http://kitware.com" target="_blank">kitware.com</a><br></div>
<<a href="http://kitware.com" target="_blank">http://kitware.com</a>>><div class="im"><br>
<br>
<br>
<br>
<br>
nolden wants you to pull from nolden/VTK<br>
at 9ba9588<br>
<br>
Body: Hi,<br>
<br>
this is a bugfix for the rendering of<br>
utf8 characters. The<br>
handling of signed / unsigned was<br>
incorrect. As a result<br>
only 7bit characters were rendered,<br>
though in general the<br>
code was ok for 8bit characters.<br>
<br>
cc Steven and JC, since I don't know if<br>
the "KItware" user<br>
reads pull requests.<br>
<br>
View repository:<br>
<a href="http://github.com/nolden/VTK/tree/9ba958806256e38ae4ae4fc424c37f8a7eea2ae9" target="_blank">http://github.com/nolden/VTK/tree/9ba958806256e38ae4ae4fc424c37f8a7eea2ae9</a><br>
<br>
<br>
<br>
<br>
**** Kenneth Moreland<br>
*** Sandia National Laboratories<br>
***********<br>
*** *** *** email: <a href="mailto:kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a><br></div>
<mailto:<a href="mailto:kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a>> <<a href="http://kmorel" target="_blank">http://kmorel</a>@<a href="http://sandia.gov" target="_blank">sandia.gov</a><br>
<<a href="http://sandia.gov" target="_blank">http://sandia.gov</a>>><div class="im"><br>
<br>
** *** ** phone: (505) 844-8919<br>
*** web: <a href="http://www.cs.unm.edu/~kmorel" target="_blank">http://www.cs.unm.edu/~kmorel</a><br>
<br>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br></div>
<<a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a>> <<a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a>><div class="im"><br>
<br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a> <<a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a>><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
</div></blockquote><div><div></div><div class="h5">
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
</div></div></blockquote></div><br></div>