[Bf-committers] Preliminary Design (render api)

Shaul Kedem shaul.kedem at gmail.com
Wed Jun 27 09:45:52 CEST 2007

 I think that making some kind of an abstract API will be a good
thing, check out a very good API at
http://www.ta-lib.org/d_api/d_api.html#Output%20Size (section 3.3) and
the header at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ta-lib/ta-lib/c/include/ta_abstract.h?rev=HEAD&content-type=text/vnd.viewcvs-markup
(doesn't work right now).

This way additional objects in the future will enter the same format
as previous objects, this can be good if you want to show all of the
objects using some UI, filter them "on name bases" and so on.

On the other hand, there is the object hierarchy right now within
blender, so this may be enough,


On 6/27/07, Aaron Moore <two.a.ron at gmail.com> wrote:
> Campbell,
> I believe you're right, I shall change it so something like
> void *get_objects_by_type( int type_bitflag, void *from )
> replaces
> void *get_geometry_by_type( GEOMETRY_TYPE type, void *from )
> void *get_lights( void *from )
> void *get_geometry( void *from )
> However, I'd like to keep the option of getting these object _from_ a
> specific source. I think this would allow a good deal of flexibility,
> for example, you could perform queries that return a dataset, but then
> you could perform further queries on that dataset alone. This allows
> the user to narrow their dataset by queries until they have exactly
> what they want.
> Aaron
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list