MobileBlazorBindings
Microsoft.Maui.Graphics
DISCONTINUED
Our great sponsors
MobileBlazorBindings | Microsoft.Maui.Graphics | |
---|---|---|
15 | 11 | |
1,183 | 677 | |
0.6% | - | |
2.3 | 0.0 | |
5 months ago | 10 months ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MobileBlazorBindings
-
MAUI going to all in on Blazor Hybrid.
It's difficult to imagine. But if the rumour has any merit, perhaps it simply means that there will be a push to consolidate on some blazor tech using stuff like https://github.com/dotnet/MobileBlazorBindings
-
What are your gripes with XAML?
There's Blazor Mobile Bindings but it's essentially experimental at the moment and isn't exactly active. From playing around with it though, it is pretty neat as you get the Blazor programming model but with native controls.
-
Clippy goes full cross-platform thanks to Avalonia UI framework
The benefit at least with the approach instead of embedding Avalonia inside Maui is you could potentially use non xaml frameworks for ui as long as they support Maui as a target. Stuff like Comet or Blazor mobile bindings would be possible aside from xaml. Especially if they're coming from Blazor web or code based ui frameworks like flutter which makes it appealing.
-
MAUI's potential hindered by inadequate maintainership
This is one reason I'd really love for them to push through on making alternatives to XAML like Blazor mobile bindings.
-
Is .net MAUI appropriate for a bachelor's thesis?
I'd say Blazor mobile bindings is also pretty interesting imo, unlike Hybrid it doesn't use Html and uses MAUI controls directly but still keeps the Blazor programming style and still uses razor to tie in C# and components.
-
Roundup of .NET MAUI. - Week of July 18, 2022
Oleksandr has been contributing to the official experiment project, and singlehandedly updated it to support .NET MAUI. He even now has documentation on his fork.
-
Anyone been trying out .NET MAUI?
I really hope Blazor Mobile Bindings takes off imo. I still care for native controls and if Mobile bindings does become a valid target, then you'll have an alternative to XAML when writing native components but using Razor syntax (which imo is less verbose). It'll be like how React does it (which is still pretty popular) where you have React web and also React Native which uses the platform's native controls underneath. Both aren't exactly the same but since the framework is similar (React, Blazor) it should be easy to swap between the two.
-
.NET MAUI Release Candidate – Ready for cross-platform app development
Yeah I really hope they'll productize Blazor Mobile Bindings (currently experimental), it's essentially using Xaml controls via Razor as the markup format instead and can use C# expressions (so less need for converters).
-
Does MAUI support web somehow?
It means you can use Blazor's syntax to write MAUI apps, as an alternative to XML-like XAML syntax.
You'll be able to use Blazor for native components (sooner or later, not on release). See here https://github.com/dotnet/MobileBlazorBindings for experimental version.
Microsoft.Maui.Graphics
-
Discussion Thread
Microsoft.Maui.Graphics (which relies on Skia anyway but whatever)
-
ImageSharp leaving the .NET Foundation due to licensing change
Yea, they can keep using the old versions, but that locks them out of the new versions and breaks expectations, especially since they were a member of the .NET Foundation. So it's up to them to keep using a version that won't get fixes or new features or accept the new license.
This whole thing just points out how hard all of this is to get right. I understand both sides. But I do at least get the feeling that the ImageSharp team is a bit high strung.
https://github.com/dotnet/Microsoft.Maui.Graphics/issues/47
I think this is probably an intentional move to move away from Microsoft and the .NET Foundation in addition to trying to capitalize on people making a lot of money from the software package.
After having looked at the license, it seems reasonable enough to me aside from the technicalities others have brought up. The vvvv tool follows a similar license of, it's free unless you make money from it.
-
Roundup of .NET MAUI - Week of June 27, 2022
This set of SkiaSharp views can be added to any .NET MAUI application for drawing. This is similar to what you can do with the built-in GraphicsView and Microsoft.Maui.Graphics, but directly to SkiaSharp.
-
Minimalistic fluent api in C# to create complex reactive Avalonia applications
There's Microsoft.Maui.Graphics as well so that the renderer will not rely on native controls just like Avalonia and Flutter (but currently it's experimental). MAUI's flexible enough to enable that scenario, the bigger question is more on motivation from either MS or the community to make it happen.
-
Views in Comet
For colors you have your choice of solid paint, linear and radial gradient paint, and more provided by Microsoft.Maui.Graphics.
-
ASP.NET Core updates in .NET 6 Release Candidate 2 - Native dependencies for Blazor WebAssembly!
This work is a pre-cursor to Blazor WebAssembly support coming in the Microsoft.MAUI.Graphics repo, giving us a single .Net API to draw on all platforms MAUI supports, along with Blazor.
-
Does MAUI support web somehow?
It doesn't support web. The most promising components at the moment to make this happen are: - https://github.com/dotnet/GraphicsControls . First they will need to get this working with normal platforms. - https://github.com/dotnet/Microsoft.Maui.Graphics . A dependency of the above library. Web code exists here but is not yet functional. - Blazor. In order to deploy usable Blazor wasm apps they need to get AOT support working: https://github.com/dotnet/aspnetcore/issues/5466 (Note the blazor you read about that is connected with MAUI is just another style of writing MAUI apps and doesn't allow MAUI apps to run on the web.)
What are some alternatives?
SkiaSharp - SkiaSharp is a cross-platform 2D graphics API for .NET platforms based on Google's Skia Graphics Library. It provides a comprehensive 2D API that can be used across mobile, server and desktop models to render images.
FFImageLoading - Fast & Furious Image Loading - Image loading, caching & transforming library for Xamarin and Windows
Plugin.AudioRecorder - Audio Recorder plugin for Xamarin and Windows
MTAdmob - Admob plugin for Xamarin Android and iOS
GraphicsControls - Experimental Microsoft.Maui.Graphics.Controls - Build drawn controls (Cupertino, Fluent and Material)
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
MagicGradients - Draw breathtaking backgrounds in your Xamarin.Forms application. It's a kind of magic.
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
ImageSharp - :camera: A modern, cross-platform, 2D Graphics library for .NET
xaml-code-experiences - A collection of the experiences I have collected during days of Xamarin and Wpf, while following the MVVM design pattern.
TwokaB - Blazor WebView control for WPF, Android, macOS, iOS. Run Blazor on .NET Core and Mono natively inside a Webview.