The following example is based on TextDecoder, a JS-based decoder. For more information, see the Prerendering section. InvokeAsync unwraps the Promise and returns the value awaited by the Promise.įor Blazor apps with prerendering enabled, calling into JS isn't possible during prerendering. A JS Promise is returned for InvokeAsync methods. NET type that best maps to the JSON type returned. The TValue return type must also be JSON serializable.TimeSpan represents a time limit for a JS operation.The cancellation token ( CancellationToken) propagates a notification that operations should be canceled.Pass any number of JSON-serializable arguments in Object to a JS function.There's no need to register the function before it's called. To call, the identifier is someScope.someFunction. The function identifier ( String) is relative to the global scope ( window).NET, inject the IJSRuntime abstraction and call one of the following methods:įor the preceding. IJSRuntime is registered by the Blazor framework. NET methods from JavaScript functions in ASP.NET Core Blazor. They can be accessed via KMKernel ( the "kmkernel" construct ).For information on how to call. KMFolderDir's contents are managed by KMFolderMgr's. A special case of a KMFolderDir is KMFolderRootDir it represents the toplevel KMFolderDir in KMail's folder hierarchy. It inherits KMFolderNode and KMFolderNodeList which is a QPtrList. KMFolderDir is a directory abstraction which holds KMFolderNode's. Subclasses of KMFolderIndex finally interact directly with physical storage or with storage providers over the network. KMFolderIndex contains some common indexing functionality for physical folders. KMFolder and FolderStorage have many functions with the same names and signatures, but there is no inheritance. KMFolder acts as the runtime representation of a folder with the physical storage part being represented by a member of type FolderStorage. KMFolderNode's often do not have an on-disk representation, they are entities existing only within KMail's design. KMFolderNode is the base class encapsulating common folder properties such as the name and a boolean signifying whether the folder is a folder holding mail directly or a KMFolderDir. The collaboration among KMail folder classes looks as follows : KMFolderNodeĪt the base KMail's folder design starts with KMFolderNode which inherits QObject. KMKernel implements the KMailIface (our DCOP interface) and gives access to all the core KMail functionality.įIXME this has moved to libkpimidentities, right?įiles: identity*, tdemidentity. It's always created before any other class, therefore you are guaranteed that KMKernel::self() (and therefore "kmkernel" construct) won't return 0 (null). The "kmkernel" is a define in kmkernel.h declared as : #define kmkernel KMKernel::self() KMKernel is the central object in KMail. The first thing you'll notice about KMail is the extensive use of kmkernel->xxx() constructs. TODO: reader, composer, messages, accounts. be handy for people not hacking full-time on KMail as well as people that want to trace bugs in parts of KMail which they don't know well. This file is intended to guide the reader's way through the KMail codebase.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |