Ok; although I think changing the information the blender renderer uses can be a nice thing (especially if it will be using these functions to begin with) so future enhancements to the blender renderer *could* be done from plugins.
<br><br>I gave some thought to your <b>Push vs. Pull. </b>paragraph. The way I see it, different renderers may need different information segments at different times, so given that this is an API (vs. a data structure pre-populated with all of the data) I think that your conclusion is right; The API should provide the, well, API.
<br><br><div><span class="gmail_quote">On 6/6/07, <b class="gmail_sendername">Aaron Moore</b> <<a href="mailto:two.a.ron@gmail.com">two.a.ron@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Shaul,<br><br>I'm glad you're interested in the project!<br><br>> Also, am reading the wiki (haven't finished) but wanted to ask if this API<br>> will be able to change the information before the render, and if so, will it
<br>> go back to the scene or be part of the rendering only?<br><br>Here's how I see this issue. The exporter, given that it's task is<br>clearly defined, to produce the rendered image data, will not have the<br>
ability to change any of the scene data from the API. The scene data<br>will be available for read-only query. All information will be there<br>to allow many kinds of renderers to access the data they need in the<br>way they need it in order to fulfill their task within blender: to
<br>produce image data.<br><br>However, some things are not implemented in a given renderer, and some<br>things are too complected to provide exact representations of the way<br>blender does them. Material settings are a good example: shader
<br>implementations will not be accessible through the API, merely<br>declarations of the type and input values: type = "phong" spec=".5"<br>hardness="50" In these cases, the exporters are expected to make
<br>local copies of the input data so that they can manipulate them for<br>use in an exporter specific implementation of the type "phong." At<br>least this is how I currently see it.<br><br>Generally speaking, it is a bad idea to make things mutable when they
<br>don't need to be.<br><br>Aaron<br>_______________________________________________<br>Bf-committers mailing list<br><a href="mailto:Bf-committers@blender.org">Bf-committers@blender.org</a><br><a href="http://lists.blender.org/mailman/listinfo/bf-committers">
http://lists.blender.org/mailman/listinfo/bf-committers</a><br></blockquote></div><br>