On Mon, May 12, 2014 at 9:28 AM, Alexis López Zubieta <azubi...@estudiantes.uci.cu> wrote: > Hello: > I keep using the Sokoloff's branch, I have ported some components > successfully but those that relies on Xlib are stalled. While I was > trying to fix the taskbar also realize that both Xlib and Xcb can work > together. I didn't like the idea of use two libraries that do the same > thing, but if you think it's not mandatory we can move on.
This is the design choice made by xcb developers, keeping it backward compatible so porting can be done gradually. If we have more people working on it, phasing out xlib and use xcb only. If we don't have people who can work on it, we use mixed xcb + xlib. I think this approach is reasonable. Many programs are still using xlib so it won't die soon. > About liblxqt, I agreed with you, we must finish it's port to Qt5 before > once it became a bit stable we keep working on the panel and the other > components. I'd recommend the following workflow. 1. Let's fix our main liblxqt repo first. (there are still some header renaming problems) 2. Once liblxqt fully works with Qt5, let's port your code to use it instead of the unfinished branch left by sokoloff. 3. Just disable plugins which do not compile in Qt5 at the moment. 4. We can enable the plugins by one after they're fixed. 5. Leave kwindowsystem and wait for KDE developers to improve it more. Let's fix our mixing xlib+xcb code first. 6. Merge the qt5 changes to the master branch. 7. Start porting to kwindowsystem after we have a Qt5 version that works with X11. > I'm interested in helping you with this but right now I'm a bit busy > with my thesis work, i have to send the report tomorrow and on thursday > I have to present it to the judges :-(. So i will have a little time to > code. That's ok. I'm busy too. People all have their real lives. Otherwise we should have the first LXQt release long time ago if we're full time developers. > But in the meanwhile we can work on design, gather some requirements and > agreed on the API. Afther this week i will have some free time to code :D. That will be great. > About the kwinsystem support, i have to say that i was overwhelmed, what > a shame. I thought that it will be easy but i was to far away from > truth. The thing that most shock me was the leak of documentation, may > be I'm a bad googler but I only found it's API description. So nothing > have been done in this area. Glad to hear that nothing has been done yet. This will actually make the initial porting to Qt5 easier. We can do it again after lxqt-panel is ported to Qt5. I believe that we can make it work with least effort by mixing xcb and xlib temporarily. > So, do we start by liblxqt? Definitely. > Best wishes and happy mothers day > > Alexis López Zubieta > Nova Light Development Team > University of Informatics Sciences, Cuba ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
