• @wth@sh.itjust.works
    link
    fedilink
    3010 months ago

    Well… this is pretty crappy.

    I built a Xamarin app (mac/iOS) because I wanted portability to windows. Then I was forced to upgrade to .net 6/7 because of a library I needed, and that meant upgrading to .Net for Mac/.Net for iOS (which is part of MAUI, but not using MAUI UI controls). MAUI is definitely undercooked at the moment.

    What an awful and painful process, but I’m finally there… and they drop the main IDE for development. Damn.

    VSCode doesn’t have a visual UI designer (well… neither does VSMac, but it does prepare a copy of your project and opens XCode for editing the storyboard/images, and copies changes back). So does this mean they will add that to VSCode? Or will we all have to switch to raw edits of XML to create UIs like you have to do with MAUI? Ick.

    Developing GUIs for windows using MS tools is a lesson in frustration, especially when you want to have cross platform capabilities… WPF -> WinForms -> Xamarin -> Xamarin.Forms -> MAUI/.Net for {Mac,iOS}… Not to mention UWP… Each transition is a rewrite. Damn.

      • @wth@sh.itjust.works
        link
        fedilink
        1
        edit-2
        10 months ago

        ROFL.

        True on desktop OSs. I did quite a bit of commercial dev on GTK many years ago, but I always found the look and feel on Mac (esp) and windows quite klunky. I hear that quite a bit of work has been done on native theming, so perhaps my impressions are out of date. Having said that - GTK wasn’t bad to work with. I also did a project in WxWidgets, but again desktop only. It was not too bad for simple apps.

        For the current app - first release target was iOS, then Mac, Android, Windows then Linux. So GTK was out since its not mobile friendly (I have heard you can do something on Android, but iOS is out).

        • TerrorBite :veripawed3:
          link
          fedilink
          110 months ago

          @wth I have worked with GTK3 myself, and once I got used to its quirks, actually found it quite nice to work with. I was writing my code in Python too, which added some extra challenge, but the GObject introspection took a lot of the pain out of interoperating with what’s basically a C library.

          However, I’m aware that GTK has a bit of a reputation. The look and feel is great on Linux desktops that use it natively, but I do remember it looking pretty ugly cross-platform.

        • @Trivial@programming.dev
          link
          fedilink
          110 months ago

          GTK has improved a lot, but native theming isn’t the area. It has very powerful theming but I don’t think a macOS theme exists.

    • @abhibeckert@lemmy.world
      link
      fedilink
      4
      edit-2
      10 months ago

      What an awful and painful process

      Yeah… that’s why almost nobody uses Xamarin. The fast approaching train if you’re invested in Xamarin (for others, the light at the end of the tunnel) is SwiftUI which is the first good SDK designed to create cross platform user interfaces.

      SwiftUI isn’t on Windows yet - but it’s coming.

      • @wth@sh.itjust.works
        link
        fedilink
        810 months ago

        Its hard to make a commercial decision for something that’s coming someday. But I hope it does arrive - I like Swift as a language (OMG - it was such a pleasure after the ugliness that is Objective C).

      • @wth@sh.itjust.works
        link
        fedilink
        210 months ago

        I really like the idea of having a web UI for its portability and richness (esp thanks to CSS being so close to consistent across all platforms). But I have a metric tonne of business logic and ZKE code in C#/.Net running on Mac/iOS. From your prompt, I did just find Electron.Net, so perhaps there is hope.

        And, AFAICT, electron can’t be used for iOS apps on the App Store (am I still wrong about that??)

        Plus (personal bent) I did a ton of JavaScript years ago when truthiness and indeterminate behaviour was rampant back in ES5 days. I’m a purist and found it a little ugly, but incredibly fast. Then I found dart which compiled to JS, and I decided that JS made a better assembly language than a usable language. Sadly dart has remained a minor player. JS has moved on and I see lots of the old ugliness (like iterating through properties, exceptions and a sync) has gone away. ES13 looks pretty good, although I haven’t played with it yet.

          • @wth@sh.itjust.works
            link
            fedilink
            110 months ago

            After I saw your note, I had a quick catchup on that project.

            It looks awesome, with the promise of mobile and desktop, and the ability to make apps that can be uploaded to the AppStore. Plus its Dart which is a pretty well structured language. Its ticking a lot of boxes…

            Then I ran « wc -l » on my support libraries (i.e. not UI code) - 64k LoC that would need to be rewritten in dart. But then I noticed Flutnet. its probably an abomination linking the two… but it could be promising.

            Thanks for the pointer.