<div dir="ltr">On Fri, Aug 15, 2008 at 4:00 PM, Marcelo Coraça de Freitas <span dir="ltr"><<a href="mailto:mfreitas@ydeasolutions.com.br">mfreitas@ydeasolutions.com.br</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
Hello all!<br>
<br>
Now, for the properties window of the plugin I am considering using GTK. For now there will be no such thing but I am wondering of that will be a good idea or not - maybe using the libraries for the blender interface will be better as we won't have many dependencies. What do you think?</div>
</blockquote><div><br>It'd be great if you could use Blenders interface code to do that. I don't feel too happy about GTK as an added dependency. I'm not sure about how the property window looks like, could you give more info? (Perhaps screenshots of property windows of existing plugins).<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>The biggest issue right now is the Mozilla's header files. I can see two options. Depend on user interaction so he will have mozilla installed or we can add the Gecko SDK (a 8mb folder) into the extern folder. I am in favour of the second one but I am not the one who should decide this. So, what's gonna be?</div>
</blockquote><div><br>For now, lets go with the first way - we can always decide to do it otherwise. Just make sure you have some good defaults (ie. in case of Quicktime SDK, we have lib/windows/QTDevWin as the default path in scons. perhaps lib/windows/Gecko can be a good default for this.<br>
</div></div>On the other points I can't comment yet (too little knowledge), but I must say I'm very happy to see renewed effort in this part of the code.<br><br>/Nathan<br></div>