Hi,
Here I am listing two project ideas for GSOC.
Your opinion about which to select , modification idea about the scope of
these projects will be very much helpful.
If you find some ideas that are not feasible or sth important relating to
these topics that are not listed here please tell about th
> *Idea 1 : Improvement of Game Engine Python API*
>
> 1.providing syntaxes similar to these -
>
> a. *scene.meshes["meshName"]*
>
> b. *meshI.material.textures["myTexVar"] = loadedTexture *
>
> this is for *KX_MeshProxy* class.Like textures the options for setting
> these properties
>
Message: 2
Date: Fri, 26 Mar 2010 21:10:57 -0700
From: Mitchell Stokes
Subject: Re: [Bf-committers] my GSOC project idea
To: bf-blender developers
Message-ID:
<9e1569591003262110j697ff1d7v3bc1798b85315...@mail.gmail.com>
Content-Type: text/plain; c
Here is the patch: http://www.pasteall.org/11985/diff
It's pretty messy as I didn't get around to finishing it. I was
planning to support DXT1, DXT3 and DXT5, which handles the most
popular ones. If I recall correctly, adding more formats wouldn't have
been too difficult. None the less, I know thi
Just to complement.
I gave Shuvro the idea of working with DDS without really understand how
much work that would take.
So if If that's not much work to a GSOC I would endorse the idea of having
other small tasks to be completed on top of that.
I never participated on a GSOC though so I'm not sure
Hi Shuvro, I'd hesitant to recommend API projects from developers who
have not had to use similar API's before.
So rather then work on a project to improve the API you could choose a
project that has this as a component.
To accomplish this you would end up having to extend the API's but
with real
