Page 2 of 7 FirstFirst 1234 ... LastLast
Results 11 to 20 of 67

Thread: Mir Works On Screencasting, Parallelized Page Flipping

  1. #11
    Join Date
    Dec 2013
    Posts
    84

    Default

    Quote Originally Posted by intellivision View Post
    Mir doesn't use Compiz because it's not compatible with the specific Xorg hooks that Compiz relies on.
    Compiz will never be used in a post X world.
    how do you think they build the compositor?

  2. #12
    Join Date
    Oct 2013
    Posts
    409

    Default

    Quote Originally Posted by marciocr View Post
    The cases are totally different.

    The "Mir haters" must understand that Wayland isn't a display server. No DE will adopt Wayland as his display server. The DEs teams will build a display server that will implement Wayland protocol.
    that only speaks in favour of wayland. getting rid of one layer and getting more with the roots gives one more power. sadly, as far as DE go, as much as i don't like to admit it, but with recent atrocities in gnome usability and KDE not being ready for wayland prime... ubuntu with unity holds advantage. still, there is 0 chance for me to opt for Mir or Unity though.

    as much as i'm hyped about wayland, i also get downright sad when i think i'll be reverting to 90s era where my desktop looked like museum of various looking toolkits. right now selection is really bad. most gtk apps were completely destroyed by gnome HIG down to being complete crap (gedit, epiphany...) and last months all i'm doing is searching for sane replacements in order to be ready for wayland

  3. #13
    Join Date
    Sep 2012
    Posts
    280

    Default

    Quote Originally Posted by Attentäter View Post
    nope Mir is using Compiz
    No
    Quote Originally Posted by Attentäter View Post
    and it shares code with Wayland
    No
    Quote Originally Posted by Attentäter View Post
    Unity8 was
    No
    Quote Originally Posted by Attentäter View Post
    how do you think they build the compositor?
    By paying developers to write code, what do you think?

  4. #14
    Join Date
    Feb 2014
    Posts
    113

    Default

    Quote Originally Posted by Attentäter View Post
    how do you think they build the compositor?
    it is my understanding that either MIR or unity 8 is the compositor, like built in...

  5. #15
    Join Date
    Dec 2013
    Posts
    84

    Default

    Quote Originally Posted by Pajn View Post
    yes

    yes

    yes

    By ripping out Compiz's compositor, what do you think?
    i fix that for you

    they used code from Wayland and Compiz even the SDL Mir code is using Wayland paths

  6. #16
    Join Date
    Dec 2013
    Posts
    84

    Default

    Quote 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

  7. #17
    Join Date
    Sep 2012
    Posts
    280

    Default

    Quote 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.

  8. #18
    Join Date
    Sep 2012
    Posts
    280

    Default

    Quote 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.

  9. #19
    Join Date
    Dec 2013
    Posts
    84

    Default

    Quote 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

    Quote 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

  10. #20
    Join Date
    Sep 2012
    Posts
    280

    Default

    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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •