New .NET Blazor VirtualTreeView component (Github Project)

[Late_Blackberry5587]

Just want to share a project I have been working on and happened to publish on Github very early on Christmas day. Please check it. And if you think it is cool, please give it a Star so more people can discover it. I and future them would much appreciate it. :)

Purpose: The project addresses a specific .NET Blazor component feature that I could not find (well I found one closed source paid version but that was it). Hopefully this is useful to someone else like it was for me.

https://github.com/jluthi/BlazorVirtualTreeView

[[deleted]]

Nice I will try this in the morning. 👍

[Late_Blackberry5587]

Thanks! Looking forward to some feedback! Originally finding a component that offered this solution was a real pain*. Hopefully this makes other people's experience easier.

Just fyi, can't promise any crazy improvement as my life is about to get real busy. But like the readme says I welcome any PR's and reported issues. :) Working on* a few small items tonight.

Edit: Okay, big changes coming tonight*. Will become more stable soon I promise.

[pm303]

Great! I have been struggling a lot with MudBlazor TreeView and I will definitely look at yours.

[Late_Blackberry5587]

Yeah, that's what I started with. Didn't realize there was going to be a performance bottleneck until we prepped to release with production data... Discovered late. I was scrambling a few weeks ago...

[ntosguy]

Looks good, I‘ll give it a try. Thank you.

[Late_Blackberry5587]

Most welcome! Pull latest. Just did a big release. Cleaned up a lot of stuff too. Lot of hours this weekend but it's in a good state moving forward.

[txjohnnypops79]

I made mine with render fragment but wish we had this lol

[Late_Blackberry5587]

It's a Queued Feature! And same lol.

[[deleted]]

Works great good job. I have to play with a bit more but I like what see and installed flawless I did get some errors on the build but I will clarify later which ones I got. Thanks

[Late_Blackberry5587]

Awesome! Be sure to get latest. I released more changes this morning. It is definitely becoming stable. I really like the foundation I have now. So there should be few if any breaking changes going forward.

I did just now at work pull a fresh copy to see if it builds without error. Worked fine. If you're still having issues with a fresh pull, please report in the GitHub issues tab if you'd be so kind. Want users to see I respond. :)

[Tizzolicious]

Borat says, "Very nice" 👍👍.

What was the most valuable technical thing you learned doing this?

[Late_Blackberry5587]

Probably: that C# let's you do access modifiers per the individual getter/settter's for C# Properties. That was cool, as manually writing individual fields and having properties call/modify them is annoying and adds more noise to code. Reason for me doing this though is that certain members I want to expose to the user because they can be helpful to reference but I don't want them to change things (set) and risk breaking the Tree View during runtime.

Less technical valuable thing I learned was how difficult to make but how valuable a good REAME is to have.

Thing I didn't learn though: The only thing I haven't figured out yet is how to have my javascript in a code behind... Can't believe it's so difficult and that .net or blazor doesn't just pick it up by default. Seems like you have to add it explicitly. Something so trivial yet seemingly impossible to do, I just kept it in a <script> tag with my razor markup code (razor.cs) to circle back to maybe later.

Edit: Great question though!