On Sun, Dec 12, 2010 at 8:54 AM, Phil Endecott < spam_from_goo...@chezphil.org> wrote:
> Don't overcomplicate it. 99% of reqirements are satisfied by "and > greater than", i.e. "I need >= 4 user clip planes and >= 3 texture > units". Don't let the theoretical possibility that someone might want > to say "I need exactly 2 user clip planes and anisotropic filtering OR > less than 6 user clip planes and non-power-of-two mipmaps" stop you > from implementing the basic functionality. > That's my point. I believe the number one pain point that has been raised is texture formats, so this is a solution for that which can be provided very quickly because it can re-use all of the existing infrastructure for features and shared libraries. Doing something more will delay any solution for textures. Anyway, I can't discuss this much more. I work on the platform, and this is totally unrelated to the platform -- filtering like this is not at the platform level (the platform doesn't even know what these things are), it is part of Market, and that is outside my area of expertise. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
