Aspose.PDF for C++ is a native C++ library that enables the developers to add PDF handling capabilities to their C++ applications. Aspose.PDF for C++ API can be used to build C++ applications which are capable of reading, writing, rendering, printing, and converting PDF documents (PDF, PDF/A). You can also work with attachments, images, security, signatures, text, and tables. Aspose.PDF for C++ allows you to extract text from all pages of a PDF document, set privileges on a PDF file, work with bookmarks and annotations. It also gives you vast control over customizing the PDF display properties, fonts, zoom fact, and content formatting. Text search feature is also available. You can convert PDF documents to the DOC, DOCX, and SVG formats by simply calling the designated C++ methods. Aspose.PDF for C++ performs equally well at the client-end and server-side. It can be used in the development environment that supports C++ but explicitly supports MS Visual Studio 2015 or later. Aspose.PDF for C++ can be installed manually by downloading its ZIP package or it (Aspose.PDF.CPP) can be added via NuGet Package Manager. Support for Qt framework is also available.
Join SMART COSMOS Are you ready to become part of creating something really big? With SMART COSMOS you can connect a universe of everyday things to the digital world. In fact, SMART COSMOS is the only platform that is purely focused on providing a fast track for both enterprises and developers to Monetize the IoT. SMART COSMOS is an ecosystem. It consists of a robust partner network where hardware manufacturers, system integrators, software developers and enterprises come together to create the IoT. It is comprised of both SaaS and PaaS offerings that help you EMBED, ENRICH, EFFECT, and EXPLORE IoT driven data. SMART COSMOS also includes an education portal, SMART COSMOS Lessons, and a vibrant developer community at our Partner Development Portal. Developers who complete the full Extension Developer learning path, passing all exams, earn the right and privileges of being a SMART COSMOS Certified Enginee. DOCUMENTATION - SMART COSMOS Profiles in the Partner Development Portal - http://partner.smart-cosmos.com - SMART COSMOS API Documentation - https://api.smartcosmos.net - SMART COSMOS Lessons - http://lessons.smart-cosmos.com
Aspose.PDF for C++ is a native C++ library that enables the developers to add PDF handling capabilities to their C++ applications. Aspose.PDF for C++ API can be used to build C++ applications which are capable of reading, writing, rendering, printing, and converting PDF documents (PDF, PDF/A). You can also work with attachments, images, security, signatures, text, and tables. Aspose.PDF for C++ allows you to extract text from all pages of a PDF document, set privileges on a PDF file, work with bookmarks and annotations. It also gives you vast control over customizing the PDF display properties, fonts, zoom fact, and content formatting. Text search feature is also available. You can convert PDF documents to the DOC, DOCX, and SVG formats by simply calling the designated C++ methods. Aspose.PDF for C++ performs equally well at the client-end and server-side. It can be used in the development environment that supports C++ but explicitly supports MS Visual Studio 2015 or later. Aspose.PDF for C++ can be installed manually by downloading its ZIP package or it (Aspose.PDF.CPP) can be added via NuGet Package Manager. Support for Qt framework is also available.
Memurai is a Redis-7.0-compatible cache and data store for Windows. It’s designed to provide the reliability and performance demanded by enterprise Windows environments. Just like Redis, Memurai uses an in-memory data set to achieve great performance at scale, and Memurai supports all the Redis features that you know and love, such as persistence, replication, transactions, LUA scripting, high-availability, pub/sub, cluster, modules, streams, and LRU eviction. In fact, it supports all of the Redis API 7.0 eviction policies.
Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.SitemapXml namespace contains Http Handlers which intercept the request before it hits Sitecore. Robots.TXT Handler: Returns a basic document that automatically applies to all search engine agents. The stock configuration has disallows for /sitecore urls to prevent the login page from being indexed. Additional default or site specific rules can be added through the supplied configuration file. See instructions within the config file. Assuming a given Site's robots.txt does not deny the root of a site, the robots.txt file will include a link to the site's sitemap.xml file. Sitemap.XML Handler: Returns an on-the-fly document (there are cache options available) for each configured Site in your installation. The document is created by having one or more "crawlers" inspect the Content Tree generating the necessary Item facts and URLs required to produce the Sitemap. You can specify a set of default crawlers for your installation, as well as override the crawler list on a site-by-site basis. There are also provisions for excluding sites from returning a sitemap.xml document if it is not appropriate. Default Functionality: The system will function on a basic level "out of the box". There is a default Content Tree crawler that will start at the root of the current Site and include Items that have presentation details. The crawlers operate in the extranet\anonymous role and thus security can be used to "hide" Items or branches from the crawler. Crawler output has extensive support for "validating" whether an Item should be included in the sitemap or not. Facts available through the API include: - Does the Item have presentation? - Does the Item have explicit rules to prevent Search Indexing? - Does the Item represent a "Page"? It is up to the developer to supply meaningful decisions behind these facts, but answering "no" to any of them will result in the Item not being included. This library outputs substantial amounts of troubleshooting warnings to the Sitecore log file. If you're having trouble, search for Constellation.Foundation.SitemapXml in your log file. Multi-Language Support: For every "site" definition element in your Sitecore configs, add a "supportedLanguages" attribute that is a comma-delimited list of all languages available on your site (example: supportedLanguages="en-US,fr-FR,pt-PT") Doing this will force the sitemap.xml file to include "alternate" links for each language the site supports. Installation Warning: Your web.config must have a system.webServer/handlers section, and that section must have at least one handler in it (an "add" element) in order to install this package successfully. If you're using the default Sitecore web.config this won't be an issue. The handlers provided in this package must be inserted at the top of the stack of handlers.
Azure AI Language extraction backend for AgentMemory for .NET. Entity recognition uses Azure NER; fact, preference, and relationship extraction are heuristic (Azure Text Analytics has no dedicated API for these).
Generates visualizations of Jinaga facts and types. For use wihtin .NET Interactive Notebooks. Data management for web and mobile applications. Connect your client to a replicator to replace your hand-written API and database. Jinaga supports occasionally connected clients with local storage in SQLite.
SOCI was initially developed in the environment where Oracle was the main database technology in use. As a wrapper for the native OCI API (Oracle Call Interface), the name 'Simple Oracle Call Interface' was quite obvious - until the 2.0 release, when the internal architecture was largely redesigned to allow the use of backends that support other database servers. We have kept the same name to indicate that Oracle is the main supported technology in the sense that the library includes only those features that were naturally implemented in Oracle. With the 2.1 release of the library, two new backends were added (MySQL and SQLite3) and we decided to drop the original full name so that new users looking for a library supporting any of these simpler libraries are not discouraged by seeing 'Oracle' somewhere in the name. The other possible interpretation was 'Syntax Oriented Call Interface', which stresses the fact that SOCI was built to support the most natural and easy interface for the user that is similar to the Embedded SQL concept (see below). But on the other hand, SOCI also provides other features (like object-relational mapping) and as a whole it is not just 'emulator' of the Embedded SQL. With all these considerations in mind, SOCI is just 'SOCI - The C++ Database Access Library'.
MSI Install Manager is an API that allows you to install an MSI within a .NET application. You can create a WPF install experience and drive the execution of the MSI within. (In fact you can use command line, Winforms, or any other .NET capable client )
Random Facts is a fun facts API that delivers a random fact on every request without requiring any query parameters. Drop bite-sized trivia into apps, chat widgets, and daily notification feeds.
Easily control all aspects of sending and retrieving information from the MailFacts API.
Horoscope fetches daily horoscope readings and sign details for any of the twelve zodiac signs. Pass a sign name to receive today's forecast text; paid tiers add birthdate lookups, mood, lucky numbers, sign compatibility, and sign facts like the ruling planet, opposite sign, brightest star and days until the sign's season.
Chuck Norris Jokes delivers a random Chuck Norris joke on every request without requiring any query parameters. Each call returns plain joke text ready to display in bots, command-line interfaces, or entertainment feeds.
Generates visualizations of Jinaga facts and types. For use wihtin .NET Interactive Notebooks. Data management for web and mobile applications. Connect your client to a replicator to replace your hand-written API and database. Jinaga supports occasionally connected clients with local storage in SQLite.
.Net Standard 2.0 client for cat-facts API. It supports C# 8.0. Made using RestSharp.
Fill in the Blanks Generator creates completion puzzles from idioms, proverbs, quotes, science facts, and geography trivia.
OpenTokVideoView, a .NET MAUI view that renders an OpenTok publisher's camera preview or a subscriber's remote video, over the cross-platform OpenTok.Net API. Handles the part every OpenTok MAUI app otherwise writes twice: OpenTok hands its render view out of the SDK rather than taking one in, so the view has to be attached into a container after the fact. Call UseOpenTok() in MauiProgram.
RuleWright execution engine: expression-tree rule compiler, dynamic-fact interpreter fallback, thread-safe compiled delegate cache, and the RuleWrightBuilder/RuleWrightEngine public API.
Ollama-powered fact extractor and memory consolidator for BlazorMemory. Run local LLMs like llama3.2 or mistral — no API key required.
Provides a client for the NumbersApi (http://numbersapi.com) created by David Hu and Mack Duan. The NumbersApi returns facts about numbers, dates, and years.
County Data Lookup is a county lookup API that retrieves income, poverty rate, and life expectancy for any US county by state and county name, along with its FIPS code and time zone. Paid plans add age demographics, educational attainment, health indicators, ZIP codes, and cost of living.
Model-driven code generation for .NET: a Roslyn incremental source generator that turns one JSON model (bellerophon.json) into a multi-tenant, in-memory ledger with transactions, constraints, an ASP.NET Core API, write-behind persistence, a change feed, and rules-engine facts. Reference Bellerophon.Runtime alongside it, and Bellerophon.SqlServer or Bellerophon.Rules for those features.
Nutrition returns the nutrition facts for a generic whole food by name - calories and the core macronutrients per 100 grams straight from the USDA food composition database - plus, on paid plans, a full micronutrient panel and derived nutrition intelligence like calories per gram and the protein, fat and carbohydrate share of calories.