Announcement

Collapse
No announcement yet.

Mir Works On Screencasting, Parallelized Page Flipping

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

  • #16
    Originally posted by TheSoulz View Post
    it is my understanding that either MIR or unity 8 is the compositor, like built in...
    Compiz compositor was build into it

    Comment


    • #17
      Originally posted by Attentäter View Post
      i fix that for you

      they used code from Wayland and Compiz even the SDL Mir code is using Wayland paths
      You don't know much about anything, do you?

      Wayland is a protocol, you can't use code from Wayland as Wayland isn't code!
      Compiz is a X.org specific software with a very high use of X.org specific APIs
      using Compiz without X.org is inpossible. Also Mir have nothing to do with how
      windows look and behave wich is the only thing Compiz cares about.

      Comment


      • #18
        Originally posted by Attentäter View Post
        Compiz compositor was build into it
        No. Compiz is written in C++ 98. Unity8 is written in C++ 11 and QML.
        Compiz only cares about X.org. Unity 8 only cares about QT.

        Comment


        • #19
          Originally posted by Pajn View Post
          You don't know much about anything, do you?

          Wayland is a protocol, you can't use code from Wayland as Wayland isn't code!
          Compiz is a X.org specific software with a very high use of X.org specific APIs
          using Compiz without X.org is inpossible. Also Mir have nothing to do with how
          windows look and behave wich is the only thing Compiz cares about.
          Mir and Unity8 are being build one a Mir the Server talks to b Unity8 the DE who cares

          no duplicated code here

          Originally posted by Awesomeness View Post
          The fact right now is that code is duplicated.
          Just compare https://hg.libsdl.org/SDL/file/52f86...L_waylanddyn.c against https://hg.libsdl.org/SDL/file/52f86...r/SDL_mirdyn.c
          Occasionally here is a line of code missing, there was a line of code added and in the end the Mir back-end has 20 lines of code less in this file than the Wayland back-end but the rest is pretty much a search "WAYLAND" and replace with "MIR". Even the comments are the same:

          Code:
          #if DEBUG_DYNAMIC_WAYLAND
              if (fn != NULL)
                  SDL_Log("WAYLAND: Found '%s' in %s (%p)\n", fnname, waylandlibs[i].libname, fn);
              else
                  SDL_Log("WAYLAND: Symbol '%s' NOT FOUND!\n", fnname);
          #endif
          
              if (fn == NULL)
                  *pHasModule = 0;  /* kill this module. */
          
              return fn;
          }
          
          #endif /* SDL_VIDEO_DRIVER_WAYLAND_DYNAMIC */
          
          /* Define all the function pointers and wrappers... */
          #define SDL_WAYLAND_MODULE(modname) int SDL_WAYLAND_HAVE_##modname = 0;
          #define SDL_WAYLAND_SYM(rc,fn,params) SDL_DYNWAYLANDFN_##fn WAYLAND_##fn = NULL;
          #define SDL_WAYLAND_INTERFACE(iface) const struct wl_interface *WAYLAND_##iface = NULL;
          #include "SDL_waylandsym.h"
          #undef SDL_WAYLAND_MODULE
          #undef SDL_WAYLAND_SYM
          #undef SDL_WAYLAND_INTERFACE
          Code:
          #if DEBUG_DYNAMIC_MIR
              if (fn != NULL)
                  SDL_Log("MIR: Found '%s' in %s (%p)\n", fnname, mirlibs[i].libname, fn);
              else
                  SDL_Log("MIR: Symbol '%s' NOT FOUND!\n", fnname);
          #endif
          
              if (fn == NULL)
                  *pHasModule = 0;  /* kill this module. */
          
              return fn;
          }
          
          #endif /* SDL_VIDEO_DRIVER_MIR_DYNAMIC */
          
          /* Define all the function pointers and wrappers... */
          #define SDL_MIR_MODULE(modname) int SDL_MIR_HAVE_##modname = 0;
          #define SDL_MIR_SYM(rc,fn,params) SDL_DYNMIRFN_##fn MIR_##fn = NULL;
          #include "SDL_mirsym.h"
          #undef SDL_MIR_MODULE
          #undef SDL_MIR_SYM
          Even the file names just had a search&replace done: https://hg.libsdl.org/SDL/file/52f86.../video/wayland https://hg.libsdl.org/SDL/file/52f86.../src/video/mir

          Comment


          • #20
            Projects have coding standards. If you submit a patch that doesn't look
            like the rest of the code then you won't get your code merged. If you look
            at the X11 dyn it looks exactly the same aswell
            Code:
            #if DEBUG_DYNAMIC_X11
                if (fn != NULL)
                    printf("X11: Found '%s' in %s (%p)\n", fnname, x11libs[i].libname, fn);
                else
                    printf("X11: Symbol '%s' NOT FOUND!\n", fnname);
            #endif
            
                if (fn == NULL)
                    *pHasModule = 0;  /* kill this module. */
                return fn;
            }
            
            #endif /* SDL_VIDEO_DRIVER_X11_DYNAMIC */
            
            /* Define all the function pointers and wrappers... */
            #define SDL_X11_MODULE(modname)
            #define SDL_X11_SYM(rc,fn,params,args,ret) SDL_DYNX11FN_##fn X11_##fn = NULL;
            #include "SDL_x11sym.h"
            #undef SDL_X11_MODULE
            #undef SDL_X11_SYM

            Comment


            • #21
              Originally posted by Pajn View Post
              Projects have coding standards. If you submit a patch that doesn't look
              like the rest of the code then you won't get your code merged. If you look
              at the X11 dyn it looks exactly the same aswell
              Code:
              #if DEBUG_DYNAMIC_X11
                  if (fn != NULL)
                      printf("X11: Found '%s' in %s (%p)\n", fnname, x11libs[i].libname, fn);
                  else
                      printf("X11: Symbol '%s' NOT FOUND!\n", fnname);
              #endif
              
                  if (fn == NULL)
                      *pHasModule = 0;  /* kill this module. */
                  return fn;
              }
              
              #endif /* SDL_VIDEO_DRIVER_X11_DYNAMIC */
              
              /* Define all the function pointers and wrappers... */
              #define SDL_X11_MODULE(modname)
              #define SDL_X11_SYM(rc,fn,params,args,ret) SDL_DYNX11FN_##fn X11_##fn = NULL;
              #include "SDL_x11sym.h"
              #undef SDL_X11_MODULE
              #undef SDL_X11_SYM
              Wayland used DRM from Xorg....

              Comment


              • #22
                Originally posted by Attentäter View Post
                Wayland used DRM from Xorg....
                And? The code you posted have nothing to do with that, it just checks
                if Wayland/Mir/Xorg is avalible for compiling or not.

                Comment


                • #23
                  Originally posted by Pajn View Post
                  And? The code you posted have nothing to do with that, it just checks
                  if Wayland/Mir/Xorg is avalible for compiling or not.
                  Sorry for stepping on your Religion and Mark your God but they do share code i looked over the SDL code files said to say there is no point in Mir ill keep using Xorg and i have better things to do like coding later noob

                  Comment


                  • #24
                    anyway...
                    I've decided to test XMIR on ubuntu 14.04 and i have to say WAY BETTER!
                    visual glitches are gone ( at least with this hardware ) and performance is alot better
                    i wonder now that SDL had mir support does that mean i can run XMIR and when i launch a game it uses MIR stuff instead of X?
                    and would nvidia lasted beta drivers work with XMIR since it has EGL support? i'm unable to test this since im not close to my desktop with an nvidia card.
                    Last edited by TheSoulz; 02-14-2014, 09:01 PM.

                    Comment


                    • #25
                      Originally posted by Attentäter View Post
                      Sorry for stepping on your Religion and Mark your God but they do share code i looked over the SDL code files said to say there is no point in Mir ill keep using Xorg and i have better things to do like coding later noob
                      Bye.

                      .

                      Comment


                      • #26
                        Originally posted by Attentäter View Post
                        Sorry for stepping on your Religion and Mark your God but they do share code i looked over the SDL code files said to say there is no point in Mir ill keep using Xorg and i have better things to do like coding later noob
                        if you wanna learn more about mir Follow this link:
                        https://wiki.ubuntu.com/Mir/Spec?action=show

                        shows how the compositor works

                        Comment


                        • #27
                          Basically wayland is vaporware that needs to be implemented by each desktop environment while Mir when finished will be a display server which is ready to use without having to go to all the trouble of writing an entire protocol implementation from scratch.

                          Comment


                          • #28
                            Originally posted by TheOne View Post
                            Basically wayland is vaporware that needs to be implemented by each desktop environment while Mir when finished will be a display server which is ready to use without having to go to all the trouble of writing an entire protocol implementation from scratch.
                            The facts say that Wayland is that kind of vaporware that is implemented in several projects, from desktop to the in-vehicle infotainment (and in the phone world, looks to Jolla, it's a real phone, not prototype) while Mir is still implemented only in the Canonical workgroup and nobody cares to adopt it.

                            Comment


                            • #29
                              Originally posted by valeriodean View Post
                              The facts say that Wayland is that kind of vaporware that is implemented in several projects, from desktop to the in-vehicle infotainment (and in the phone world, looks to Jolla, it's a real phone, not prototype) while Mir is still implemented only in the Canonical workgroup and nobody cares to adopt it.
                              We will see...

                              Comment


                              • #30
                                Originally posted by valeriodean View Post
                                The facts say that Wayland is that kind of vaporware that is implemented in several projects, from desktop to the in-vehicle infotainment (and in the phone world, looks to Jolla, it's a real phone, not prototype) while Mir is still implemented only in the Canonical workgroup and nobody cares to adopt it.
                                What matters is the financial backing behind project. People may not like Mir or Canonical but if they keep pushing it with financial support for years, it will eliminate the need for Wayland. If Wayland does something better, with enough effort Mir can adopt that and become better in the end. It's just a matter of manpower and industrial co-operation. For example if Mir supports closed source drivers better, companies will like it more and at least on ARM all GPU work is closed so it's clear Wayland has trouble on ARM and Mir doesn't.

                                Comment

                                Working...
                                X