Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Gtk] NuGet packages #90

Closed
lytico opened this issue Apr 12, 2024 · 11 comments
Closed

[Gtk] NuGet packages #90

lytico opened this issue Apr 12, 2024 · 11 comments

Comments

@lytico
Copy link
Collaborator

lytico commented Apr 12, 2024

Discussion: Should where be NuGet packages at this early stage of implementation?

@lytico
Copy link
Collaborator Author

lytico commented Apr 12, 2024

@jsuarezruiz wrote: maybe we can start creating some NuGet packages from this point? #66 (comment)

@lytico wrote: not sure about that, it's really not production ready at all #66 (comment)

@mhrastegari wrote: Why not a pre-release package? :") #66 (comment)

@lytico
Copy link
Collaborator Author

lytico commented Apr 12, 2024

pros:

Gtk Applications in Maui's "Dialect"
Motivation to join Maui Gtk implementation

cons:
Only basic controls are working at the moment
Some of the basic Controls have errors

@mhrastegari
Copy link

Yes! I mean if only BlazorWebView and native navigation works it's totally worth it!

@kztao
Copy link

kztao commented Apr 23, 2024

i completely agree

@steveriemannx
Copy link

Yes!

@taha-ghadirian
Copy link

Yes! I mean if only BlazorWebView and native navigation works it's totally worth it!

That is exactly what we need to kick-start a new MAUI Blazor project on Linux!
Publishing a pre-release would be greatly appreciated.

@jsuarezruiz
Copy link
Owner

My point of view here would be:

  • Create a Nightly feed.
  • Add the status to the Wiki and documentation with a link a table with the implementation (every control), etc. and clearly indicate that it is a pre-release. Both in documentation and with versioning.

The reasons would be:

  • Allow devs to create apps on Linux. Only with Label, Entry and Button you can create various types of Apps. With Blazor Hybrid open many possibilities. I think that in the current state, although very far from something stable, it can allow the creation of certain types of apps.
  • Having devs using it increases the possibilities of increasing the community: having more feedback or who knows, even more devs cooperating with PRs etc.

The disadvantage, it may cause a negative feeling/feedback due to lack of implementations. Could happen, it's a risk, I would say that the solution would be a good Wiki and correctly share the message.

Feedback?

@ysmoradi
Copy link

ysmoradi commented Jun 7, 2024

@jsuarezruiz Thanks for your efforts

In bitplatform we helps developers to write the codes only once and have as much as outputs as possible, and as you can see, the Linux support is missing
image

I know there is a fair expectation about quality of a nightly feed provided nupkg

I've the same hope about blazor hybrid and Linux, especially if we become able to test them directly in windows thanks to wslg and Visual Studio.

@knocte
Copy link

knocte commented Jun 8, 2024

Feedback?

If by "nightly feed" you mean that each commit to the master branch (or main-linux branch) generates a nuget package that can be consumed by anyone interested, I fully support this idea. We have this approach in FSharpLint: each commit generates a prerelease nuget package. When we feel it is ready for a (non prerelease) nuget package, then we create a git tag and a nuget package with the version of the git tag gets pushed to nuget.org.

Making both nighly feed (prerelease nuget packages) and normal packages live in nuget.org also helps visibility and makes it very easy to consume without the need to subscribe to different nuget sources.

If you want to go ahead with this approach, my team can take care of it (with your guidance) and we will propose a PR.

@jsuarezruiz
Copy link
Owner

Feedback?

If by "nightly feed" you mean that each commit to the master branch (or main-linux branch) generates a nuget package that can be consumed by anyone interested, I fully support this idea. We have this approach in FSharpLint: each commit generates a prerelease nuget package. When we feel it is ready for a (non prerelease) nuget package, then we create a git tag and a nuget package with the version of the git tag gets pushed to nuget.org.

Making both nighly feed (prerelease nuget packages) and normal packages live in nuget.org also helps visibility and makes it very easy to consume without the need to subscribe to different nuget sources.

If you want to go ahead with this approach, my team can take care of it (with your guidance) and we will propose a PR.

After reviewing the feedback on this thread, I think we can agree on having a nightly feed to allow easy usage of what's currently available and to help with the visibility of the project. @knocte open an issue, and we'll discuss how to handle it in that thread.

@mhrastegari
Copy link

Hey @jsuarezruiz
Is it possible to debug it directly in Windows with WSLG and Visual Studio?

Because .NET MAUI development on Linux with VSCode is not as good as developing on Windows with Visual Studio which has a lot of tools and feature for .NET development! plus VS WSL works like a charm!

WSLG:
Run Linux GUI apps with WSL | Microsoft Learn

WSL:
Get started using VS Code with WSL | Microsoft Learn
Debug .NET apps in Linux using WSL - Visual Studio (Windows) | Microsoft Learn

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants