OpenGL ES 2.0 support (including shaders)

[raft]

After all, having more options to choose from can't be a bad thing.

impossible to disagree

A little of topic: Are you planning to get an actual phone?

no concrete plans yet. if i decide to do something for android, i will certainly need one. but the thing is, living in turkey has disadvantages on this thing too. nexus one isnt sold for this reagon at the moment i dont know any other model sold around/for here. my friend has a tattoo and g1, tattoo is sent him by a company and g1 is bought by a friend living in usa.

speaking of the witch, google gives a free android phone (g1 i suppose) to all who has an app in android market with 5000+ downloads. my friend's dictionary app has 900.000+ downloads but he cant get one because he lives in turkey 

[raft]

..i dont know any other model sold around/for here.

i must correct myself here. this is defintely not the case, there are htc and samsung models for example

[zammbi]

Just ordered a Milestone. So I can help with any testing when I get it...

[EgonOlsen]

Cool. Can we force you to write some game or something for it somehow...?

[zammbi]

Sure   
Was not cheap, had to get a special one from Canada to work on my network. So will be looking into creating some apps and putting it on the market.

[K24A3]

Sorry to dig up an old thread but I noticed a few 'WTF' comments in the default jPCT shaders, perhaps this info can help;

Varyings are used for passing data from a vertex shader to a fragment shader. Varyings are (perspective correct) interpolated across the primitive. Varyings are read-only in fragment shader but are read- and writeable in vertex shader (but be careful, reading a varying type before writing to it will return an undefined value). If you want to use varyings you have to declare the same varying in your vertex shader and in your fragment shader.

All uniform, attribute and varying types HAVE to be global. You are not allowed to specify a uniform/attribute/varying type in a function or a void.

Ref: http://nehe.gamedev.net/article/glsl_an_introduction/25007/

[EgonOlsen]

I know that. The WTFs refer to some shader compiler choking on loops and some optimizing away the whole shader is some cases. They have nothing to do with varyings in the first place.