Request to update git solution to also include a server side project in addition to a webasm project

[dokmanc]

I am new to Blazor and recently created a "unified" Blazor solution using the latest Visual Studio 2022 template, which includes both a Blazor Server project and a Blazor WASM client project. However, I noticed that the sample project on your GitHub repository is based on an older template and only includes a WASM client project.

I would greatly appreciate it if you could update the GitHub solution to use the latest .NET 8 Blazor template from Visual Studio 2022. It would be particularly helpful to include at least one example that runs on the server side.

Currently, I am interested in using BlazorDataSheet as a server-side component and would like to be able to pull the latest updates from the repository to ensure I am working with the most recent code, even if it hasn’t been published as a NuGet package yet.

In my server-side project, I successfully created a page that utilizes BlazorDataSheet, but I found that keyboard scrolling does not perform as smoothly as it does in the WebAssembly demo. I would like to investigate the cause and potentially enhance BlazorDataSheet (likely just locally, as I am still learning Blazor).

Would you consider updating your GitHub project to include both server-side and WebAssembly projects with project references to your code? This would greatly help me and others by providing a solid starting point for working with both project types.

Thank you for considering this request!

[anmcgrath]

Hi dokmanc, I haven't had any experience with the new unified blazor template but would have expected that server-side interactive render mode should work the same as the blazor server solution that is currently there.

What sort of scrolling issues is there? Have you tried it in a couple of browsers?

I'm happy to try to add examples using the new template - it makes sense as it's the suggested way to use blazor going forward.

[dokmanc]

Hi,
Thanks for the reply and for considering updating the solution in your repo to use the new .NET 8 Blazor (United) Template that includes both a Server and CWASM Client Project along with project references to all of the BlazorDataSheet projects. I look forward to this update and hope that it will help me to focus on using your component rather than setting up the app plumbing.

As for the issue that I was having with scrolling, it was related to keeping the active cell always visible as I use the arrow keys to move the focus to a new cell. When I run your repo WAM project, the scrolling works as expected, the currently active cell is always visible but when I create a simple grid, the default navigation behavior does not seem to keep the active cell so it remains in view. I demo this issue in the following screen capture video: https://app.screencast.com/C06ZYyYaMc5fh?tab=Details&conversation=EALfROnkbgpNHhVXXJ9RU1

[dokmanc]

Do you think the difference in scrolling behavior described above and demonstrated in the video link a difference between the git project that includes the source code for each project and the NuGet package?

[anmcgrath]

Hi @dokmanc yes the nuget package hasn't been updated for a little while so the scrolling behavior might be related to that. If you clone the repo and add your own project/code the scrolling should work as expected? Thanks for the detailed video by the way.

I've got a fairly big update brewing in the view-redo branch which should improve the scrolling behavior again. With that I'll try to migrate the server project to the new blazor hybrid approach.

[dokmanc]

Thanks for the reply. Agreed!
I decided to fork your repo here, https://github.com/dokmanc/BlazorDatasheet. In it, I added some logic to respond to browser resizing, as shown here,
https://app.screencast.com/FaQAkx3X1zgWt?tab=Details&conversation=92it2dTMhCI6BgYN66ky5q
It's probably a little klunky, especially in how I take into consideration how to resize when the left menu pane turns into a hamburger.
The next think I am trying to figure out is how to resize a column all of the columns to fit the data, taking into consideration using a variable font to determine exact sizings.
I love this project and that you are actively working it. Keep up the good work!

[anmcgrath]

@dokmanc v0.5 is out on nuget, it would be interesting to see if that fixes your scrolling issues.