Found 53 packages
Maya .Net Dark Scheme for WPF http://around-the-corner.typepad.com/
Aspose.3D for .NET is an on premise class library that enables your .NET applications to create, read, manipulate, convert and save various formats of 3D files (e.g. FBX, IFC, 3MF, USD, PDF, STL, Blender, DAE, DFX, MB, MA, glTF, U3D, etc.), without installing any 3rd party 3D modeling or rendering software. Aspose.3D for .NET API enhances your .NET apps to open files of 3D formats and work with the elements within the 3D scenes; such as; line, mesh, nurbs, curves to more complex elements like animation. You can also work with textures, parametrized geometries, scene graphs, custom properties, skeletons, morph deformers and much more. Aspose.3D for .NET can be used on any operating system (Windows, MacOS, Linux) that can install Mono (.NET 4.0 Framework support) or use .NET Core. It is a single .NET library that you can deploy with any .NET application by simply copying it. You do not have to worry about other services or modules. Aspose.3D for .NET is designed to perform equally well on the server as well as the client-side.
Maya.AnyHttpClient basic http client for simplifying connecting to API.
Maya.Ext is an extension library includes useful utils suitable for all projects.
Maya.BulkGate.Sms is a simple library for sending SMS via BulkGate.
Package Description
A F# library to convert and calculate with MayaTzolk’in dates and gregorian dates.
Package Description
MayanDateTime is a C# library for working with dates in the Maya calendar system.
Package Description
Maya.BulkGate.Sms.Extension.Microsoft.DependencyInjection an extension for Maya.Bulkgate.Sms package using Microsoft DI.
This project allows you to reuse your Visual Studio Unit Tests without modifications in your Mono for Android projects.
An extension for the Umbraco backoffice that adds a new tree to the settings section to display the resolved configuration for the runtime environment.
Imagine you deploy an application with, say, a pipeline for transforming Maya binaries to some specific graphics-engine dependent format and another pipeline for transforming 3dsMax files to the same target format. You have a whole lot of types which have to be differently implemented in both pipelines, even though they stick to the same contracts. And you are using Autofac. So you need a way to easily tell the container: - this is a component to be used in the context of the Maya pipeline - this is a component to be used in the context of the 3dsMax pipeline - this component X should be used by all pipelines - for the Maya pipeline, please override X with Y If this scenario sounds familiar to you, this Autofac.Extra is for you.
NineWaves is a F# library to calculate with the nine Maya waves of Carl Johan Calleman
A library for Mayan/Gregorian calendar conversions
Customized calendar plugin for Xamarin.Forms
Mayan Calendar converts Gregorian dates to the ancient Mayan calendar system. Returns the Long Count, Tzolkin (260-day sacred calendar), and Haab (365-day civil calendar) dates.
Updates existing records where auto number field is missing value Read more: https://mayankp.wordpress.com/2021/12/09/xrmtoolbox-autonumberupdater-new-tool/
Allows to View and Export Internal Dynamics 365 Business Rules Java Scripts! Read more: https://mayankp.wordpress.com/2021/12/24/xrmtoolbox-new-tool-businessrulesscriptviewer/