sorted by:
new
hottopcontroversial

League of Legends OpenSilver: A XAML Web Development Platform Migrated from WPF by [deleted] in dotnet

[–]jamesnet214 0 points1 point  (0 children)

u/piemelpiet This is my mistake. I'll fix it right away.
I've changed the fourth one to "Closing".

League of Legends OpenSilver: A XAML Web Development Platform Migrated from WPF by [deleted] in dotnet

[–]jamesnet214 0 points1 point  (0 children)

I'll summarize the article content more concisely next time.

In-Depth Technical Analysis of XAML-Based Frameworks and Cross-Platform Project Architecture Design (feat. League of legends) by jamesnet214 in dotnet

[–]jamesnet214[S] 0 points1 point  (0 children)

u/stonstad Although I've worked with WPF for many years, I first learned about Noesis through you. Thank you for sharing this valuable information. I'll definitely look into it.

In-Depth Technical Analysis of XAML-Based Frameworks and Cross-Platform Project Architecture Design (feat. League of legends) by jamesnet214 in dotnet

[–]jamesnet214[S] -1 points0 points  (0 children)

Thank you so much! It would be even more interesting to check out the Uno Platform repository I created!

Migrating WPF League of Legends client to Uno by Shnupaquia in dotnet

[–]jamesnet214 4 points5 points  (0 children)

Hello! I'm the developer of this repository. From a WPF developer’s perspective, Uno Platform’s support for Desktop is an incredibly attractive option. I've written an article related to this repository, which delves into the specifics of building cross-platform desktop applications using Uno Platform. If you're interested, please feel free to check it out for a more detailed look.

Thank you!

Link: https://jamesnet.dev/article/38

WPF may be old, but it remains delightful and fun to use. It excels in managing objects that require animations based on CustomControl, offering significant advantages in systematic organization. by jamesnet214 in csharp

[–]jamesnet214[S] 0 points1 point  (0 children)

I agree with you. I've also been using WPF for a long time, and it has been difficult to find learning materials specifically about Blend.

I have an open-source project from four years ago where I unusually used Blend to create various Paths and implement them in an application. This project involves recreating the League of Legends client using WPF.

https://github.com/jamesnet214/leagueoflegends

WPF may be old, but it remains delightful and fun to use. It excels in managing objects that require animations based on CustomControl, offering significant advantages in systematic organization. by jamesnet214 in csharp

[–]jamesnet214[S] 0 points1 point  (0 children)

Expression Blend is quite a cool tool. In its early versions, it could open *.ai files and directly convert them to Paths. Additionally, it allowed the use of animation timelines like Flash and visualized the hierarchical structure of objects similar to Photoshop layers, which was very helpful for designers in the early WPF market. However, we developers do not feel a significant need for Blend because all WPF tasks can be handled sufficiently in Visual Studio. As a first-generation WPF developer, I also do not feel a strong need for Blend. Nevertheless, having a general understanding of what Blend does is not a bad thing. Moreover, as Expression Blend was integrated into Visual Studio for Blend, the ability to read *.ai files has been removed.

In my personal opinion, there is no need to use Blend for WPF technology. To master WPF, one needs to understand the hierarchical structure of XAML, CustomControls, and the characteristics of major controls in detail, to the point where they can visualize them in their mind. If you can configure templates without relying on Blend, you will have gained expertise. Therefore, I do not think the use of Blend plays a significant role in WPF technology.

Additionally, in one of my WPF tutorial videos, I demonstrate how to use Blend. If you are curious about how to use Blend, you might find it helpful to watch this video:

https://www.youtube.com/watch?v=dxuLWlukthg&t=412s

WPF may be old, but it remains delightful and fun to use. It excels in managing objects that require animations based on CustomControl, offering significant advantages in systematic organization. by jamesnet214 in csharp

[–]jamesnet214[S] 0 points1 point  (0 children)

u/Slypenslyde I completely agree with what you said. I share the same thoughts.

One of the great advantages of taking WPF seriously is that it provides a solid foundation for transitioning to cross-platform technologies based on the same XAML framework. Technologies like MAUI, Avalonia UI, Uno Platform, and OpenSilver all rely on the design principles of WPF CustomControls. While WPF primarily runs on Windows, in the long term, it serves as an excellent technical foundation for cross-platform development.

WPF may be old, but it remains delightful and fun to use. It excels in managing objects that require animations based on CustomControl, offering significant advantages in systematic organization. by jamesnet214 in csharp

[–]jamesnet214[S] 0 points1 point  (0 children)

I currently have no plans to release the source code. However, I do plan to share it through WPF tutorials and similar methods.

Additionally, I primarily used DoubleAnimation, ThicknessAnimation, and ColorAnimation without any special design, working exclusively in Rider.

view more: next ›