WhatIf... GC09E01 - GirCore Mutter

[czirok]

WhatIf... GC09E01 - GirCore Mutter

Source

Gnome Shell

Introduction

This is just a proof of concept. A demonstration of how brilliant the GirCore you created is. Sincere thanks on behalf of the .NET community that loves Linux and develops on Linux.

This is still a concept, but in its current state, using the .NET and NuGet ecosystem, it could even enable a full .NET-based GNOME Shell implementation. The only limit is imagination, as it makes possible highly unique, pluggable, and themeable Linux desktop experiences unlike anything seen before in the history of Linux.

GirCore Mutter

To give a concrete example, here is a pure C# WM, effectively a minimal Mutter-style sample, implemented in just a few lines of C#:

language	files	code	comment	blank	total
C#	2	76	1	18	95
XML	2	51	5	9	65
Shell Script	1	6	1	2	9

GirCoreMutter_small.mp4

Source: GirCore Mutter

And 18 NuGets

ATK-1.0

Source: ATK-1.0

Generator extensions:

• InterfaceMethodsCollidingWithInterfaceMethodsFixer : Fixer<GirModel.Class>
• GLibPointerArray : FieldConverter

Mtk-18

Source: Mtk-18

Generator extensions:

• OpaqueTypedRecordArray : FieldConverter
• OpaqueUntypedRecordArray : FieldConverter

EGL-1.5 and Cogl-18

Source: EGL-1.5 and Cogl-18

This was the first time I encountered that gir files do not reflect real dependencies. In Cogl-18.gir, EGL is required instead of GL. This was an important lesson, as it showed that gir files are not always accurate.

The EGL-1.5.gir file did not exist, so it had to be created. This was another important lesson: sometimes gir files need to be created. EGL-1.5 README.md

After that, GL had to be replaced with EGL in Cogl-18.gir, and missing types had to be defined. Cogl-18 README.md

Clutter-18

Source: Clutter-18

Generator extensions:

• UnionFramework : Generator<GirModel.Union>
• UnionMethods : Generator<GirModel.Union>
• Union : ToManagedParameterConverter
• Union : InstanceParameterConverter
• Union : ToNativeParameterConverter
• Union : ReturnTypeConverter - ReturnType
• Union : ReturnTypeConverter - ReturnTypeToManagedExpression
• UnionFramework
• UnionMethods

P11Kit-0.26, Gck-2, Gcr-4

The situation here was similar to Cogl-18: a missing P11Kit-0.26.gir file. This also had to be created, and Gck-2.gir and Gcr-4.gir had to be made compatible. A shell script was used to generate and modify the P11Kit-0.26.gir file. P11Kit-0.26 generation

Generator extensions:

• PropertyCollidingWithInheritedMembersFixer : Fixer<GirModel.Class>
• ArrayLengthConversion

Description of the generator extensions: CLongUnsignedCLong.md

GModule-2.0

Source: GModule-2.0

GioUnix-2.0

Source: GioUnix-2.0

Gvc-1.0

Source: Gvc-1.0

GDesktopEnums-3.0

Source: GDesktopEnums-3.0

xfixes-4.0, xlib-2.0

Source: xfixes-4.0, xlib-2.0

Meta-18

Source: Meta-18

Here, the Meta-18.gir file needed to be modified. README.md

NM-1.0

Source: NM-1.0

Generator extensions:

Here, the EscapeString needed to be extended with a KnownNumericPrefixes dictionary, where 80211 is replaced with IEEE80211. I intentionally deviated from the escape behavior because this felt more logical, and it can be extended as needed. NumericDictionary.md

    private static readonly Dictionary<string, string> KnownNumericPrefixes = new()
    {
        { "80211", "IEEE80211" }
    };

Polkit-1.0, PolkitAgent-1.0

Source: Polkit-1.0, PolkitAgent-1.0

Here, the Polkit-1.0.gir file needed to be modified. README.md

St-18

Source: St-18

The St-18.gir file was incomplete, so it had to be extended with a Cogl-18.gir include. README.md

Shell-18

Source: Shell-18

Closing thoughts on generation

During the generation process, I came to the conclusion that in many cases it is more practical to modify gir files than to write generator extensions. This highlighted that gir files are not always accurate. In some cases, they are inconsistent and depend on non-existent gir files to such an extent that creating and modifying those files is simpler than extending the generator.

I would like to thank you once again for this amazing GirCore, and for the fantastic experience of using it. This project is a true gem for the Linux and .NET community, and I am looking forward to seeing what amazing things developers will create with it.

Keep it up!

[badcel]

Thank you. Your demo is pretty impressive 👍.

Gir files are system dependent. You can't mix and match them. I wonder if you take all gir files from one distro like fedora if things would match together better.

Someday the generator will be available as a nuget itself. Then you can generate any binding for any gir file you give it.

I hope that over time the integration will get as deep as there is little to no trace of interop between C# and C with GObject.

[czirok]

WhatIf... GC09E02 - GirCore Bar

World's first: GirCoreSession, GirCoreShell, and GirCoreLauncher - the GNOME session and shell completely reimagined, in pure C#.

Not a fork, not a port, not JavaScript. A new layer on GNOME fundamentals: the same Mutter, the same Wayland, but the shell is now written in C#. And alongside it, the GirCore Bar - a clean, lightning-fast application launcher.

GirCoreBar_Small.mp4

AOT sizes:

• 6,797,000 bytes - GirCoreSession
• 6,647,192 bytes - GirCoreShell

GirCore Modifications

• Native return value handling in the generator was improved: Fundamental types now use explicit Handle management instead of always falling back to DangerousGetHandle().
  • src/Generation/Generator/Renderer/Internal/Callback/CallbackCommonHandlerRenderUtils.cs
  • src/Generation/Generator/Renderer/Internal/ReturnTypeToNativeExpression/Converter/Class.cs
• Multiple src/Libs/*/Public/Module.cs files have been updated uniformly. Modules now support a custom DllImportResolver configuration, and initialization has changed accordingly.

Meta-18 Modifications

New Meta-18 files have been introduced around WaylandClient, expanding Wayland client functionality for the GirCore Shell and Session modules.

• src/Libs/Meta-18/Internal/WaylandClient.PrivateMethods.cs
• src/Libs/Meta-18/Public/WaylandClient.PrivateMethods.cs
• src/Libs/Meta-18/Public/WaylandClientCaps.cs

GC09E02 Summary

GirCoreSession

gnome-session reimagined. Not a port, not an emulation - a completely new session leader written in C# that speaks the same systemd targets and DBus protocols as the original.

GirCoreShell

gnome-shell rewritten. Runs on Mutter, serves as a Wayland display server, and implements the same DBus interfaces - but without JavaScript, in pure C#, AOT-compiled.

GirCoreLauncher

The result. A minimalist, lightning-fast application launcher built on the two modules above, proving that .NET has a place in the heart of the Linux desktop.

nugets-gnome50.zip
WhatifGC09E02.log

[czirok]

Hello @badcel

7 gir files -> 7 NuGet packages, and Linux only.

These gir files are already included in the SDK, but compiling them requires extending the Generator in a few places. I marked the required modifications for each gir file.

Please review them, and if everything looks fine, I will submit all of them one by one as separate PRs.

If you think the Generator source should be modified somewhere, let’s discuss it and I will make the necessary changes.

Atk-1.0.gir

Source: ATK-1.0

Generator extensions:

• InterfaceMethodsCollidingWithInterfaceMethodsFixer : Fixer<GirModel.Class>
• GLibPointerArray : FieldConverter

Manual files:

• Internal/DocumentIfaceData.cs
• Internal/EditableTextIfaceData.cs
• Internal/ImplementorHandle.cs
• Internal/ObjectClassData.cs
• Internal/TextIfaceData.cs
• Public/NoOpObject.InterfaceMethods.cs
• Public/TextHelper.Methods.cs

GModule-2.0.gir

Source: GModule-2.0

Manual files:

• Internal/ModuleHandle.cs

GioUnix-2.0.gir

No modifications needed.

GDesktopEnums-3.0.gir

No modifications needed.

xfixes-4.0.gir

No modifications needed.

xlib-2.0.gir

No modifications needed.

Polkit-1.0.gir

Currently, a gir patch is required for compilation, which is described here:

• Polkit-1.0.gir patch

[badcel]

Please just open separate PRs.

Start by prioritizing them in the order which is most important for you. So don't open like 10 PRs but 1 as a start.

Then we can see if I think your most important changes belong into GirCore. Then you can continue opening more PRs if you think they are helpful for you until we reach a point you have nothing more open on your list.

It's just easier for me this way. Thank you.