Free, unsolicited advice to CCL management from someone with some knowledge in this area:
Take a serious look at a platform-portable development environment such as
wxPython. wxPython is a cross-platform toolkit. This means that the same program will run on multiple platforms without modification. Currently supported platforms are 32-bit Microsoft Windows, most Unix or unix-like systems, and Macintosh OS X.
As suggested by the name, wxPython uses the Python programming language, which is easy to learn, easy on the eyes, kind of a "swiss-army knife" of programming languages because you can do so many different kinds of things with it and an amazing toolkit for the amount of functionality you get absolutely free, from this open source platform. I haven't learned CCL enough yet to do a mental functional decomposition of the architecture but at first blush I'd say that you probably have most of what you need in the wxPython toolkit and most certainly can add what is needed from the vast pool of open source add on tools available.
I was curious about how long it would take an experienced programmer to get productive on Python. He had never done any MS Windows development and had never heard of the Python programming language. He was able to get a working proof of concept application running in about three weeks. This included getting remote RPC procedures written in Python running on a Linux server to communicate with a Python/wxPython/TCL/TK client running on Windows XP. The client application ran flawlessly on Windows, Linux and Mac from the same single source code. Did he have questions and issues? Yes, quite a few. But unlike development in the proprietary world, he had a whole community of helpful peers to quickly and accurately get unstuck.
Obviously, porting CCL to wxPython would take longer than three weeks, but you may find that it would take a lot less effort than you think, and give you access to many more customers for no additional development effort. But most importantly, you will gain much more control over your development destiny and will no longer be vulnerable to having your product roadmap be sent over the cliff because some proprietary component vendor (1) went out of business (2) got sold to a competitor or (3) needed a new revenue stream, so they ended the life of your current product, to get you to buy the next one.
I am no longer involved in development of software products for sale, but I know that if I were, I'd be using tools like wxPython for many reasons.
Regards,
Lee