gtk ongoing

[lytico]

merging main-linux with

1. a recent maui.main (dotnet@1106987)
2. plus Moves Microsoft.Maui.Graphics.Gtk into the Maui repo dotnet/maui#9522

State

Controls.Samples.Gtk is running

all the rest is WIP

How to get net6-gtk workload:

clone https://github.com/GtkSharp/GtkSharp branch Develop

dotnet tool restore
dotnet cake --BuildTarget=InstallWorkload 

Controls.Samples.Gtk screenshot:

[lytico]

State

Controls.Samples.Gtk is compiling
Controls.Maps is compiling
BlazorWebView is compiling

[lytico]

State

Controls.Samples.Gtk running

[jsuarezruiz]

State

Controls.Samples.Gtk running

Ready to review/merge?

[lytico]

i've little time at the moment ...

[iMonZ]

i've little time at the moment ...

Hey @lytico and @jsuarezruiz and everybody else, thank you so much for your work!
My only question is what is missing before this can be merged?

Thanks

[knocte]

Ready to review/merge?

How can this be tested? If there were clear instructions I'd be down to help :)

[lytico]

@knocte check it out, & run src/Controls/samples/Controls.Sample.Gtk

next step would be: try get src/Controls/samples/Controls.Sample to COMPILE
it wouldn't RUN, cause there are missing controls, but it would be helpful to have a compiling Controls.Sample to continue

[trungnt2910]

it wouldn't RUN, cause there are missing controls

I can see that MAUI is a really quicky-evolving platform, so for every version of MAUI added, numerous new controls are added too.

The platform specific portions of controls seem to follow a very specific convention, would a stub generator program (something that guesses the functions needed to be implemented, and then write placeholders that simply throw NotImplementedException()) be a useful tool for the porting effort?

[lytico]

@trungnt2910 this is the strategy i use.

1. make it COMPILE
   the projects compile without errors

2. make it RUN
   the project runs without exceptions; this includes "dummy" implementations showing "nothing" but an empty placeholder == stub

3. make it VISIBLE
   the controls/views show up something useful, but maybe not all features are implemented

4. make it feature complete
   :-) will it ever be?

5. optimize it
   sometimes after 3), sometimes after 4). have an implementation that is fast and memory optimized

[trungnt2910]

@lytico

1. make it COMPILE
   the projects compile without errors

My point is the rapid evolution of MAUI means that controls and other features are added, making this step harder and harder after rebasing (for example, while some parts of this branch may compile, rebasing it to the main branch for .NET 8 might not work, especially after half a year).

Therefore, this project would benefit from a stub generator. The simplest method is to throw a NotImplementedException everywhere, but we can customize the stubgen to generate more specific implementations for certain situations in step 2).

I would gladly build and provide an initial implementation of the stubgen for the project if you and other maintainers don't have much time, but I'm asking if using a stub generator is preferred, or if you or the other maintainers have better solutions for handling missing controls/functions.

[YoshiRulz]

I wasn't able to test the sample app on Manjaro, as installing the GTK# workload fails.

An error occurred when executing task 'InstallWorkload'.
Error: One or more errors occurred. (Access to the path '/usr/share/dotnet/sdk-manifests/6.0.400/GtkSharp.NET.Sdk.Gtk/temp' is denied.)

Everything under /usr/share/dotnet is owned by root. Creating the dir as root broke things.

---

I'm also available to work on Source Generators if that's desired.

---

My point is the rapid evolution of MAUI means that controls and other features are added, making this step harder and harder after rebasing

Microsoft could easily check for build errors in CI. But from their attitude towards Linux on the main repo so far, I'm guessing they're not going to.

[trungnt2910]

@YoshiRulz

as installing the GTK# workload fails.

Have you tried installing it as root? This workload (and probably official workloads from Microsoft) requires root access to be installed on UNIX-like machines.

I'm also available to work on Source Generators if that's desired.

What I was talking about are stub generators, those that can semi-automatically insert

#if GTK
    throw new NotImplementedException("Code path unimplemented on GTK");
#endif

and things like that, and not those Roslyn plugins that Microsoft calls "Source Generators".

Microsoft could easily check for build errors in CI

Yes, they could easily check for build errors in the CI (if writing and updating CI scripts for a separate platform is considered easy).

But what about fixing the errors? Microsoft doesn't want to spend money on a small market like GTK on Linux, and while waiting for two busy GTK experts to inspect what's wrong Microsoft would rather remove the whole Linux CI.

Also if someone really, really needs MAUI on GTK and willing to hire someone I'm happy to take on this issue as a part-time job.

[lytico]

Controls.Sample is compiling now (but not working)

Ready to review/merge