With results from well over a 100 replies the conclusions should accurately reflect the requirements from all the users of the Krypton Toolkit.
Are you using the Krypton Toolkit?
_7% No and never will
42% No and maybe will
11% Yes in internal app
34% Yes in prototype app
_6% Yes in commercial app
The low percentage for the use in commercial applications is not very surprising. Many companies will not use a third party component if they do not have the source code, especially from a small outfit like ours. Plus, although the toolkit is handy it is certainly not a replacement for any paid for product currently on the market.
If you add up the percentages for use of the Toolkit in any scenario then you have 51% and that is very encouraging for a first release of a simple library. As the Toolkit is improved and additional commercial extensions created I would expect that to improve.
Suggested focus for next release?
53% Add new control
13% Add new features
21% Improve docs and samples
14% Create predefined palettes
I was pleasantly surprised to see that only 13% of respondents requested extra features be added to the existing set of controls. Instead the clear indication is that developers would like new controls adding in order to broaden the range. This would indicate that the level of functionality and customization for the controls is already about right.
The second conclusion is that the collaterals need improving as shown by the 21% wanting improved samples and help documentation. This is entirely to be expected as the help documentation is almost empty and only a single sample application is provided.
Would you like the option of buying the source code?
23% No
34% Yes
43% Don't Care
I entered the set of results into a spreadsheet and it became clear that those replies that were not using the library answered that they did not care about the supply of source code. Those that responded by saying they were using the code tended to be biased towards wanting the code. Hardly surprising I can hear you say!
At the moment I cannot sell the source code because I need to get to Australia before I can create a company and then have a legal entity to sell the code through. But once a companyt is setup there is enough demand to make it worthwhile making it available.
What control would you like added?
This question generated a wide range of replies from the humble ProgressBar to a full feature docking windows system. But there were two answers that were far more popular than any others, a grid control and a calendar/scheduler control.
The popular demand for a grid is to be expected but will not happen as part of the Toolkit because it is intended as a small and free library that compliments the other commercial extensions in the future. I did not realize that a calendar/scheduler was such a popular control for use in applications and I will give it serious thought for a future commercial extension.
Conclusions
The results lead to the following list of tasks for the next development cycle of the Krypton Toolkit.
1) Fix all bugs
2) Add one or two new controls
3) Improve documentation in the help file
4) Create some extra samples
5) Add another predefined palette
The biggest emphasis has to be on steps 2, 3 and 4 as highlighted from the results of the survey.
