Update on Feature Requests

I am continuing to aggregate the requests and have the updated and abbreviated list below (removed items with less than 1 or 2 requests). A couple of comments based on some of the requests:

I am tracking 3D even though ScottGu announced Silverlight 3 will support 3D. For Silverlight 3, we are introducing the ability to treat 2D objects as if they are in 3D space. You can view this support as being able to draw content (XAML) onto a postcard and then position that postcard in 3D space (this is also called perspective transformations or non-affine transformations). What I am tracking for “3D” is the ability to do full 3D – which is the ability to have full 3D objects/models (e.g. a 3D box vs. a postcard) and rotate/shade/light that object.

I have not included an item for bitmap effects as we have announced plans to support a pixel shader model in Silverlight 3 and Silverlight will include a few stock shader effects.

There are some things we are continually focused on and one is performance. For performance, we are scenario focused – meaning we pick the most important scenarios and then optimize those end to end. For general performance requests, including requests for hardware acceleration, it would be helpful to understand what scenarios you feel do not meet performance expectations.

There are numerous requests for mouse wheel and there was a comment that suggested the reason we do not support this is due to a security concern. To clarify, the reason we do not support this in Silverlight 2 is that mouse wheel events are not exposed to Silverlight in all browsers (see this post for more details). We continue to look for a consistent way to work around this issue.