As I wrote, the purpose of a WM toolkit would be somehow different than a Desktop toolkit. And, yes, it’s feasible since some do it! The problem is that you have to go through the whole owner-drawn way, which nobody would do. Unless you’re a specialist such as Phil.

to add transparency support is what I would have sugested as well, but primary I’m glad to see Date/Time related controls on your roadmap (that’s what we need urgent), as well as calendar functionality. Perhaps this would prevent me from rewriting my own, in VB6 developed calender for dotNet (what I don’t know when to do). Maybe we can provide some input on needed functionality when you start planning or implementing, I think we have some good Ideas.

Although WPF impesses with it’s graphical possibilities I can not imagine when it woud be necessary for us to have controls on this basis …

I think you’re very wise to take a slower approach to WPF. Not because it’s lacking, but because WPF things will have set in by then, matured.

My suggestion for Krypton in the future is not new components — a progress bar and scrollbars would be nice, but not required.

No, my suggestion as a long-time Krypton user and purchaser is this: give the whole toolkit support for animation: transparency, movement, control size, color transitions.

@Serge. I am at first a Windows Mobile developper with the .NET CF. I would be very happy to see Krypton on it, but it doubt it is technically feasible or at least as nice as it is on the desktop. Moreover, the code will require a lot of PInvoke that could still slow down the app, but that would be definitively an interesting idea. For customizing listviews, take a look on the Alex Yakhnin blog, there are quite a few really interesting samples to extend its basic functionnality, but it is always limited by the wrapping around the native control. Resco has great components, and also OpenNETCF (for a low price). There is another thing, we still do not know how things will change with WM7.

@All : I am happy you will still support the Winforms. The next addtions to the toolkit are really welcomed (Progressbar, scollbars,…)
For WPF, I must admit I do not know how it is, if it’s great or not.

A suggestion: Windows Mobile!

One can’t seriously think of writing a real Windows Mobile app without relying on a toolkit. The needs are fairly specific. Such as a customizable ListView.

The problem is that the Windows CE (underlying WM) designers cut into the native messages that allow to easily customize the look of a listview without going the full owner drawn way. And since WM apps designers have to deal with small screen estate, intuitivity of the UI is a must. Hence the need for self speaking lists and stuff… which we don’t have.

You don’t imagine how frustrating it is to see properties and methods disappear from .NET MSDN docs whenever you select the ‘Compact Framework’ doc filter :-(

On the other hand, there’s desktop stuff we don’t need. Such as fancy buttons: A smart WM app uses only the 2 so-called Soft Keys, which are a combination of buttons and menu placed at the bottom of the screen.

The interesting news for you is that there are amazingly few actors on this fast growing market. The toolkit I used is fairly good (fairly. not more) but the support actually sucks.

You certainly have a role to play and money to make in there.

Regards,