This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Just curious how compatible your tools are will Silverlight 3.0. Thanks Will |
|
|
At the moment none of our products are available for Silverlight. We are working on some new Silverlight products, and we hope soon to get working on a version of LightSpeed for Silverlight. If there's a specific tool or product you're interested in, let us know and we'll see if we can bump it up the priority list! |
|
|
Having the property grid in both Silverlight and WPF would be a tremendous need for my application. Do you have any thoughts as to a time frame for such an effort?
|
|
|
We get a lot of requests for this, and we're keen to do it, but there are a couple of things that make this less than plain sailing. The first is that Silverlight doesn't contain some of the bits that the WPF version of the grid is built on. So we would need to recreate those bits. Fortunately, that has now happened to some extent as part of another project (plus some of the stuff that has arrived in Silverlight 3). So that is probably no longer an issue. The second is that Silverlight supports only the low-level reflection APIs. The WPF property grid makes extensive use of System.ComponentModel design-time extensibility via TypeDescriptor, PropertyDescriptor, etc. and these classes do not exist or are placeholders in Silverlight. So we would need either to build our own equivalents or to limit the grid to "true" properties (plus custom nodes and key-value dictionaries). We'd be interested to hear feedback on how important it is for you to be able to customise metadata so we can decide which of these approaches is appropriate. In terms of timeframe, we're at this stage reluctant to make a commitment. We will likely do some prototyping and proof of concept over the next month or two, but until we've done that investigation we can't even say for certain whether we'll be able to build the thing at all. Sorry this is a bit vague... |
|
|
I am being a bit selfish here and may be one of only a few, but I would like to have you build your own interfaces\objects to read from so that we could customize the grid with the same code between WPF and Silverlight in the long run. I know this is a LOT to ask and don't expect it, but it would be nice.
|
|