The main features of this release focus on Chilkat’s Ai class, enabling interactive AI response streaming directly into embedded desktop application browsers. It supports Azure, custom base URLs for OpenAI-compatible providers, and local providers like Ollama. ✨ New Features Ai Real-Time Streaming AI Responses to Embedded Browsers in Desktop Apps — Stream AI responses […]
Previous Version: Chilkat v11.1.0 Release Notes The main addition in v11.2.0 is the Chilkat.Ai class, and the Chilkat.StringBuilder.MarkdownToHtml method. Ai: The Chilkat AI class provides a unified API for interacting with different AI providers: OpenAI, Google, Claude, xAI, Perplexity, and DeepSeek. It provides functionality for conversation management, multimodal inputs, and streaming mode. Markdown to HTML […]
Starting with the v10.0.0 release (end of September 2024), Chilkat moves to standard semantic versioning. Prior to this release, for various technical reasons, Chilkat was stuck with versions 9.5.0.xx, where only xx changed. For this first leap to semantic versioning, where the major version changes to 10 (from 9), there are no backward incompatible changes. […]
Chilkat provides its own Async functions, separate from C#’s async/await. For each synchronous Chilkat function that may take time due to network communication or other factors, an Async version is also available, returning a Chilkat Task object (distinct from C#’s Task object). Chilkat’s Async functionality exists in all of the programming languages: C++, PHP, Ruby, […]
In the distant past, there were some Chilkat classes that had a few ad-hoc Async methods and properties. For example, the Ftp2 class contained the methods AsyncPutFileStart, AsyncGetFileStart, AsyncAppendFileStart, and properties such as AsyncFinished, AsyncSuccess, and AsyncLog. A number of years ago, these were replaced with a consistent and standard async model that applies to […]
Here is a complete example showing how to write a call to an asynchronous Chilkat method in .NET Core. (Note: This is .NET Core, not .NET Framework.) This example uses the TaskCompleted callback to get notified when the task completes.
I often get this question: “I’m calling the method XYZ and the UI freezes until the method returns.”. For example: “I’m trying to upload a file in FTP. I’m trying the examples of the site but the screen remains locked until the end of the upload. It’s very important that while I’m uploading a […]
Event callbacks in Java (including Android) are supported starting in v9.5.0.52. To receive event callbacks, first create a Java class derived from one of the Chilkat event callback classes. The event callback classes are: CkBaseProgress, CkHttpProgress, CkZipProgress, CkFtp2Progress, CkMailManProgress, CkTarProgress, and CkSFtpProgress. All future Chilkat classes will only use CkBaseProgress. Theses event callback classes will […]
Demonstrates a TaskCompleted event for an asynchronous Chilkat method call. The event callback occurs in the background thread, and therefore any updates to the UI must happen on the UI thread. For this reason, MethodInvoker is used to make updates to a TextBox..
Demonstrates the TaskCompleted event callback using the Chilkat Delphi ActiveX:
This sample C# snippet demonstrates how to use the TaskCompleted event to be notified when an asynchronous method completes. Given that the event callback is in the background thread, any UI updates must occur on the main thread. This example demonstrates how to do it:
Starting in Chilkat v9.5.0.52, asynchronous capability is added across all classes and all programming languages. The new Task and TaskChain classes have been added. To Beta test, send email to support@chilkatsoft.com. Please specify the programming language, operating system, etc. that is needed. The online reference documentation has been updated. Examples will be forthcoming. Version 9.5.0.52 […]
Chilkat v9.3.0 for Cocoa now includes the asynchronous functionality and event callback functionality that has been available in the C++ libs. Asynchronous methods run in a background thread such that the call immediately returns to the application. Events are not fired w/ asynchronous method calls — your app would periodically check to see if the […]
