Announcement

Collapse
No announcement yet.

GTK Scene Kit Merged For GTK4

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GTK Scene Kit Merged For GTK4

    Phoronix: GTK Scene Kit Merged For GTK4

    The GTK+ Scene Graph Kit (GSK) has landed in mainline GTK+ Git as the "spiritual successor to Clutter" and now providing a scene graph for this GNOME toolkit...

    http://www.phoronix.com/scan.php?pag...cene-Kit-Lands

  • #2
    Now get rid of Cairo, gtk!

    Comment


    • #3
      I notice there was a warning that gtk-4 will require a C99 subset - not sure why they don't go the whole hog and require C11 since they're making a clean brake with version 4

      Comment


      • #4
        Originally posted by FireBurn View Post
        I notice there was a warning that gtk-4 will require a C99 subset - not sure why they don't go the whole hog and require C11 since they're making a clean brake with version 4
        They do still have a good 2 years before they are going to releases GTK4 as properly stable but it may also require a bigger rewrite than they have hands for at the moment. Rome wasn't built in a day as the saying goes.

        Comment


        • #5
          Originally posted by tessio View Post
          Now get rid of Cairo, gtk!
          What's wrong with cairo? I think it's a pretty decent drawing library.

          Comment


          • #6
            Maybe should rewrite in C++ instead of C to take advantage of OO?

            Having to do gtk_window_frame_button() is much uglier than Gtk.Window.Framebutton();

            Comment


            • #7
              Originally posted by uid313 View Post
              Maybe should rewrite in C++ instead of C to take advantage of OO?

              Having to do gtk_window_frame_button() is much uglier than Gtk.Window.Framebutton();
              Just rename all functions to GtkWindowFramebutton style :P

              Comment


              • #8
                Originally posted by rastersoft View Post

                Just rename all functions to GtkWindowFramebutton style :P
                Legit.

                Thread closed.

                Comment


                • #9
                  Originally posted by FireBurn View Post
                  I notice there was a warning that gtk-4 will require a C99 subset - not sure why they don't go the whole hog and require C11 since they're making a clean brake with version 4
                  Because we're still trying to support compilation with MSVC, on Windows, and MSVC only supports that subset of C99 (mostly the whole thing, except variable-length arrays).

                  We're also limited by ABI compatibility constraints in GLib for _Bool, so we cannot really use that.

                  Most of the features C11 provides — atomic operations, static assertions — are already provided by GLib, so we don't really care about them.

                  Comment


                  • #10
                    Originally posted by uid313 View Post
                    Maybe should rewrite in C++ instead of C to take advantage of OO?
                    Then we'd have to write a C layer so that language bindings could be written on top of it. We'd also need to rewrite hundreds of thousands of lines of code just to use a worse language that just happens to have some OO syntactic language on top of all the pitfalls of C.

                    Comment

                    Working...
                    X