Re: [E-devel] Intent to freeze
On 06/27/2015 01:14 AM, Carsten Haitzler wrote: > On Fri, 26 Jun 2015 16:11:45 -0400 Mike Blumenkrantz > said: > >> With a few minor exceptions in Wayland, all target features for the E20 >> release have been met. As such, I am planning to commence an >> everything-but-wayland feature freeze on Friday, 3 July 2015. >> >> If anyone has things that they want to push in or implement before the >> freeze begins, I'm open to moving back the date as necessary--within >> reason. I will not, however, be very receptive to adding new features once >> the release cycle freeze has begun. > > actually - devilhorns. > > you need to pipe in here - what is the wayland state, and what would there be > left to drop in after july 3 and what timetable? > As far as what is left: DnD needs a bit of testing/tweaking yet as there are some little buggers floating in there (I'll be hacking on that come Monday). We have pending patches to support wl_text_input and wl_input_method (https://phab.enlightenment.org/D2275) however we cannot "securely" push those until we have a working VKbd implementation to go with them. I pinged shiin to see if he could also hack up a vkbd to go with. While not a Top priority, support for wl_scaler and wl_viewport would be remaining things to drop in after July 3. We have pending patches for that also (https://phab.enlightenment.org/D2485) however those need some refactoring. > i am saying this from the perspective that we get a fair number of "does e run > wayland yet" kind of questions and the answer is always nebulous. i think we > want a clear state of play for an e20 release. > While I have not tested it yet, Mike has updated/refactored my initial XWayland branch and pushed that upstream already which means we should have working XWayland support now. I've not tested it yet myself however he did manage to get Firefox running with it (which is good news) :) E/Elm apps are running good in E-Wl. Gtk apps also (tho Some gtk apps have popup menu placement issues according to Phab reports). I don't suspect that those are Major issues and likely will take little time to fix. QT apps on the other hand are a whole different can of worms. Apparenly, QT5 has not been updated yet to support xdg_shell version 5 which means, while the apps do run, they have quite a few issues. I spoke with RzR about it and he plans to update QT5 to support xdg_shell version 5 which should address issues there. There are a few pending buggers listed on Phab which I/we will be addressing in the coming weeks tho I don't think any of them are Major problems (in terms of functionality). It is likely that I may be forgetting something in this list, so if you can think of something I may have missed, please ask. Cheers, dh -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Intent to freeze
Hey, Cool, let's get this baby out of the door! A lot of exciting stuff going on. Just two comments: 1. It's a bit of a short notice, would be great to have a longer one. I'd recommend looking at how it's done in the EFL where everything is known months in advance. 2. What is the timeline for the release? Given that Wayland is still being actively developed and not frozen, and that e20 is not going to be released before efl 1.15, e will be in feature freeze for a long time. Feels a bit excessive. -- Tom. On Fri, Jun 26, 2015 at 9:11 PM, Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > With a few minor exceptions in Wayland, all target features for the E20 > release have been met. As such, I am planning to commence an > everything-but-wayland feature freeze on Friday, 3 July 2015. > > If anyone has things that they want to push in or implement before the > freeze begins, I'm open to moving back the date as necessary--within > reason. I will not, however, be very receptive to adding new features once > the release cycle freeze has begun. > > -- > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] [EGIT] [core/enlightenment] master 48/51: add hooking for WL_SURFACE_ID atom on XWayland windows and composite them
On Sat, 27 Jun 2015 14:11:29 +0900 Carsten Haitzler (The Rasterman) wrote: > On Fri, 26 Jun 2015 16:19:17 -0400 Mike Blumenkrantz > said: > > > Thankfully, it seems you didn't end up pushing your revert back upstream > > and the issue is now resolved. > > ummm... oh crap. you're right. oops. i didn't push. > > > It would be great if we could step back from this "instant revert" culture > > that has been created since the move to git. Just because it can be done > > doesn't mean that it should; it's a very reasonable thing to do a local > > revert (like this) and then raise an issue about the commit in question. > > This preserves repository history and makes it significantly easier to > > bisect things when there are fewer "revert XYZ" -> "revert 'revert XYZ'" > > chains needing to be followed. > > 1. i pinged you on irc. you did not respond. so you were not around to > discuss, and an email would thus not elicit a response in a timely fashion > either. I appreciate your attempts to contact me prior to reverting. > > 2. the point of reverting is to ensure OTHER PEOPLE are not sitting here > bitching all day about their desktop being broken so badly that it's actually > unusable. you expect each and every person to work out their own personal > private reverts? it has been a point of pride that our cvs/svn/git has > remained relatively usable at all times. this bug made e unusable. i made a > call because it was SO BAD that it had to be reverted and people OTHER than > me WILL be affected as well as it is the default pointer focus mode. the > longer it stays broken in git, the more people are affected. > > i think you need to get some perspective on this. this is not a revert > because of a typo or some small irritation in behavior. repository-history > comes a distant second place to having code not break so badly that it's > unusable. this is a QA, support and stability matter. > > i think that YOUR attitude on this is questionable. it has an undercurrent of > arrogance. yes - i am calling you out on this. if your response is "please > don't revert and discuss" and you expect all the people who update from master > to suffer while they wait for you to finish sleeping or whatever (which is > perfectly normal, so nothing wrong with that), as opposed to "oh oops. sorry. > that was bad. thanks for that. fixed it now", then that tells me that you > prioritize the beauty of commit logs over the pain of users and developers, > and that is arrogance. you matter more than they, and when someone else > spends the effort to fix things you would prefer people suffer than hurt the > "beauty" of logs with a revert. please think about this carefully. > > this isn't an instant revert culture here - i have NOT reverted your keysym > commit because it isn't hurting anyone at the moment, for example. i make a > call that when something is bad enough it has to be fixed whatever way > possible ASAP. i made that call here. You have your perspective and that's fine; you're looking at this as a couple of incidents related only to me, and I'm seeing it as a microcosm of the developer ecosystem as a whole. In my view, the workflow since moving to git has changed from "someone introduced a bug, maybe I can help out by fixing it" to "someone introduced a bug, better revert every possible commit". It's a fundamental shift from being collaborative to being combative in our usage of SCM, and I know I'm not the only one who has noticed this. Simply checking over the commit logs will show a staggering increase in the number and frequency of reverts in every repository over the past couple years. At no point have I ever said (except as a joke) that my code is always flawless. I have no issues with criticism or reverts, except when it subverts or replaces actual cooperation between developers, which, in my opinion, is what has happened to us. > > > On Fri, Jun 26, 2015 at 3:34 AM, Carsten Haitzler > > wrote: > > > > > On Thu, 25 Jun 2015 17:30:43 -0700 Mike Blumenkrantz < > > > zm...@osg.samsung.com> > > > said: > > > > > > sorry - i had to revert this due to a pretty bad behavior bug this commit > > > introduced. see my commit log in the revert. i pinged you on irc (zmike) > > > but no > > > response, so i've had to do this to at least keep e working until this can > > > come > > > back without this break. :] > > > > > > > discomfitor pushed a commit to branch master. > > > > > > > > > > > http://git.enlightenment.org/core/enlightenment.git/commit/?id=2b38147c43270815ef71726d8700703968429d90 > > > > > > > > commit 2b38147c43270815ef71726d8700703968429d90 > > > > Author: Mike Blumenkrantz > > > > Date: Thu Jun 25 19:55:37 2015 -0400 > > > > > > > > add hooking for WL_SURFACE_ID atom on XWayland windows and composite > > > them > > > > > > > > in order to maximize the amount of reused code the following details > > > the > > > > current process for xwayland compositing: > > > > > > > > * get map request fr
Re: [E-devel] Intent to freeze
On Sat, 27 Jun 2015 15:45:38 +0100 Tom Hacohen wrote: > Hey, > > Cool, let's get this baby out of the door! A lot of exciting stuff going on. > > Just two comments: > 1. It's a bit of a short notice, would be great to have a longer one. I'd > recommend looking at how it's done in the EFL where everything is known > months in advance. I can appreciate that it may be short notice, but consider that Enlightenment has been in full-on development mode for 9+ months. If anyone truly had any critical features to merge (which I am not already aware of), they've had ample time to come forward during this period. Furthermore, while I may be reluctant to merge new things after the freeze, it is by no means impossible to do so. If someone comes up with something novel and interesting which has little chance of creating large bugs for me to fix, it's probable that I'll accept it. > 2. What is the timeline for the release? Given that Wayland is still being > actively developed and not frozen, and that e20 is not going to be released > before efl 1.15, e will be in feature freeze for a long time. Feels a bit > excessive. In my estimation, >= 1 month of feature freeze (1.15 is scheduled for 3 August 2015) prior to release after a 9 month development cycle is actually a very short freeze. While I would like to provide a concrete release-by schedule, Enlightenment development is a bit different from EFL, and I am strongly opposed to setting such a deadline given the extremely limited manpower actively working on Enlightenment. Ideally, E20 will release prior to EFL 1.16, but this is nothing more than my responding to questions of "When will E17 be released?" with "Soon". > > -- > Tom. > > On Fri, Jun 26, 2015 at 9:11 PM, Mike Blumenkrantz < > michael.blumenkra...@gmail.com> wrote: > > > With a few minor exceptions in Wayland, all target features for the E20 > > release have been met. As such, I am planning to commence an > > everything-but-wayland feature freeze on Friday, 3 July 2015. > > > > If anyone has things that they want to push in or implement before the > > freeze begins, I'm open to moving back the date as necessary--within > > reason. I will not, however, be very receptive to adding new features once > > the release cycle freeze has begun. > > > > -- > > Monitor 25 network devices or servers for free with OpManager! > > OpManager is web-based network management software that monitors > > network devices and physical & virtual servers, alerts via email & sms > > for fault. Monitor 25 devices for free with no restriction. Download now > > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > -- > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Intent to freeze
On Sat, 27 Jun 2015 15:45:38 +0100 Tom Hacohen said: > Hey, > > Cool, let's get this baby out of the door! A lot of exciting stuff going on. > > Just two comments: > 1. It's a bit of a short notice, would be great to have a longer one. I'd > recommend looking at how it's done in the EFL where everything is known > months in advance. > 2. What is the timeline for the release? Given that Wayland is still being > actively developed and not frozen, and that e20 is not going to be released > before efl 1.15, e will be in feature freeze for a long time. Feels a bit > excessive. i actually would dearly love to see far more rapid releases of e. break down work into smaller blobs and when each blob is done - release. likely not more often than every 2-4 months as that will probably churn too much for users and distributions (imho), but definitely group work into chunks that fit into a 2-4 month window then get it out. repeat relatively rapidly. > -- > Tom. > > On Fri, Jun 26, 2015 at 9:11 PM, Mike Blumenkrantz < > michael.blumenkra...@gmail.com> wrote: > > > With a few minor exceptions in Wayland, all target features for the E20 > > release have been met. As such, I am planning to commence an > > everything-but-wayland feature freeze on Friday, 3 July 2015. > > > > If anyone has things that they want to push in or implement before the > > freeze begins, I'm open to moving back the date as necessary--within > > reason. I will not, however, be very receptive to adding new features once > > the release cycle freeze has begun. > > > > -- > > Monitor 25 network devices or servers for free with OpManager! > > OpManager is web-based network management software that monitors > > network devices and physical & virtual servers, alerts via email & sms > > for fault. Monitor 25 devices for free with no restriction. Download now > > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > -- > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] [EGIT] [core/enlightenment] master 48/51: add hooking for WL_SURFACE_ID atom on XWayland windows and composite them
On Sat, 27 Jun 2015 12:01:16 -0400 Michael Blumenkrantz said: > On Sat, 27 Jun 2015 14:11:29 +0900 > Carsten Haitzler (The Rasterman) wrote: > > > On Fri, 26 Jun 2015 16:19:17 -0400 Mike Blumenkrantz > > said: > > > > > Thankfully, it seems you didn't end up pushing your revert back upstream > > > and the issue is now resolved. > > > > ummm... oh crap. you're right. oops. i didn't push. > > > > > It would be great if we could step back from this "instant revert" culture > > > that has been created since the move to git. Just because it can be done > > > doesn't mean that it should; it's a very reasonable thing to do a local > > > revert (like this) and then raise an issue about the commit in question. > > > This preserves repository history and makes it significantly easier to > > > bisect things when there are fewer "revert XYZ" -> "revert 'revert XYZ'" > > > chains needing to be followed. > > > > 1. i pinged you on irc. you did not respond. so you were not around to > > discuss, and an email would thus not elicit a response in a timely fashion > > either. > > I appreciate your attempts to contact me prior to reverting. > > > > > 2. the point of reverting is to ensure OTHER PEOPLE are not sitting here > > bitching all day about their desktop being broken so badly that it's > > actually unusable. you expect each and every person to work out their own > > personal private reverts? it has been a point of pride that our cvs/svn/git > > has remained relatively usable at all times. this bug made e unusable. i > > made a call because it was SO BAD that it had to be reverted and people > > OTHER than me WILL be affected as well as it is the default pointer focus > > mode. the longer it stays broken in git, the more people are affected. > > > > i think you need to get some perspective on this. this is not a revert > > because of a typo or some small irritation in behavior. repository-history > > comes a distant second place to having code not break so badly that it's > > unusable. this is a QA, support and stability matter. > > > > i think that YOUR attitude on this is questionable. it has an undercurrent > > of arrogance. yes - i am calling you out on this. if your response is > > "please don't revert and discuss" and you expect all the people who update > > from master to suffer while they wait for you to finish sleeping or > > whatever (which is perfectly normal, so nothing wrong with that), as > > opposed to "oh oops. sorry. that was bad. thanks for that. fixed it now", > > then that tells me that you prioritize the beauty of commit logs over the > > pain of users and developers, and that is arrogance. you matter more than > > they, and when someone else spends the effort to fix things you would > > prefer people suffer than hurt the "beauty" of logs with a revert. please > > think about this carefully. > > > > this isn't an instant revert culture here - i have NOT reverted your keysym > > commit because it isn't hurting anyone at the moment, for example. i make a > > call that when something is bad enough it has to be fixed whatever way > > possible ASAP. i made that call here. > > You have your perspective and that's fine; you're looking at this as a > couple of incidents related only to me, and I'm seeing it as a microcosm of > the developer ecosystem as a whole. > > In my view, the workflow since moving to git has changed from "someone > introduced a bug, maybe I can help out by fixing it" to "someone introduced a > bug, better revert every possible commit". It's a fundamental shift from being > collaborative to being combative in our usage of SCM, and I know I'm not the > only one who has noticed this. Simply checking over the commit logs will show > a staggering increase in the number and frequency of reverts in every > repository over the past couple years. > > At no point have I ever said (except as a joke) that my code is always > flawless. I have no issues with criticism or reverts, except when it subverts > or replaces actual cooperation between developers, which, in my opinion, is > what has happened to us. in this case this doesn't imho. i tried to contact (co-operate) but due to no response within that hour or whatever a fix wasn't likely to be timely. i actually bisected the commit and read the diff. i read all of the diff and nothing jumped out at me as the cause so i could do a quick fix. i had to make a call. let it sit broken for possibly another 2-12 or so hours, or revert it with sufficient information as to why it needs a revert. i believe the log and email contained easily sufficient information. in my book that is communication. a log by itself would not be. the email is the explicit heads-up. i would have preferred that it be fixed without a revert, but i was literally sitting there with a broken system and beginning to swear every second word just trying to function as normal. sure... i can roll back myself to before the commit but i realized that what i was exper
Re: [E-devel] Intent to freeze
On Sat, 27 Jun 2015 09:05:02 -0400 Christopher Michael said: > On 06/27/2015 01:14 AM, Carsten Haitzler wrote: > > On Fri, 26 Jun 2015 16:11:45 -0400 Mike Blumenkrantz > > said: > > > >> With a few minor exceptions in Wayland, all target features for the E20 > >> release have been met. As such, I am planning to commence an > >> everything-but-wayland feature freeze on Friday, 3 July 2015. > >> > >> If anyone has things that they want to push in or implement before the > >> freeze begins, I'm open to moving back the date as necessary--within > >> reason. I will not, however, be very receptive to adding new features once > >> the release cycle freeze has begun. > > > > actually - devilhorns. > > > > you need to pipe in here - what is the wayland state, and what would there > > be left to drop in after july 3 and what timetable? > > > > As far as what is left: DnD needs a bit of testing/tweaking yet as there > are some little buggers floating in there (I'll be hacking on that come > Monday). We have pending patches to support wl_text_input and > wl_input_method (https://phab.enlightenment.org/D2275) however we cannot > "securely" push those until we have a working VKbd implementation to go > with them. I pinged shiin to see if he could also hack up a vkbd to go with. > > While not a Top priority, support for wl_scaler and wl_viewport would be > remaining things to drop in after July 3. We have pending patches for > that also (https://phab.enlightenment.org/D2485) however those need some > refactoring. > > > i am saying this from the perspective that we get a fair number of "does e > > run wayland yet" kind of questions and the answer is always nebulous. i > > think we want a clear state of play for an e20 release. > > > > While I have not tested it yet, Mike has updated/refactored my initial > XWayland branch and pushed that upstream already which means we should > have working XWayland support now. I've not tested it yet myself however > he did manage to get Firefox running with it (which is good news) :) > > E/Elm apps are running good in E-Wl. Gtk apps also (tho Some gtk apps > have popup menu placement issues according to Phab reports). I don't > suspect that those are Major issues and likely will take little time to fix. > > QT apps on the other hand are a whole different can of worms. Apparenly, > QT5 has not been updated yet to support xdg_shell version 5 which means, > while the apps do run, they have quite a few issues. I spoke with RzR > about it and he plans to update QT5 to support xdg_shell version 5 which > should address issues there. > > There are a few pending buggers listed on Phab which I/we will be > addressing in the coming weeks tho I don't think any of them are Major > problems (in terms of functionality). > > It is likely that I may be forgetting something in this list, so if you > can think of something I may have missed, please ask. the question reading between the lines from users is: "can i now use E20 to switch to wayland?" :) i've talked with you about this - i know that i personally can't. my 2 main desktop systems have new nvidia rigs and literally have zero nouveau support. i know i'm not the only one and for many nouveau is still iffy. i am sure we could get more people working on wayland if we could run "e in a window" in x11 - ie wl-x11. like weston does. with a but of imagination it'd be possible to get full acceleration for egl working too. from a pr point of view, for many people they'd like to "see how e wayland is going" without having to drop out of x11 to do it. this'd help answer a lot of questions people have. :) it'd also mean a LOT more helping getting wayland moving along. btw - how goes session recovering with uuid's etc. ... stefan? -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Intent to freeze
Hi, On Sat, 27 Jun 2015 09:05:02 -0400 Christopher Michael wrote: > On 06/27/2015 01:14 AM, Carsten Haitzler wrote: > > On Fri, 26 Jun 2015 16:11:45 -0400 Mike Blumenkrantz > > said: > > > >> With a few minor exceptions in Wayland, all target features for > >> the E20 release have been met. As such, I am planning to commence > >> an everything-but-wayland feature freeze on Friday, 3 July 2015. > >> > >> If anyone has things that they want to push in or implement before > >> the freeze begins, I'm open to moving back the date as > >> necessary--within reason. I will not, however, be very receptive > >> to adding new features once the release cycle freeze has begun. > > > > actually - devilhorns. > > > > you need to pipe in here - what is the wayland state, and what > > would there be left to drop in after july 3 and what timetable? > > > > As far as what is left: DnD needs a bit of testing/tweaking yet as > there are some little buggers floating in there (I'll be hacking on > that come Monday). We have pending patches to support wl_text_input > and wl_input_method (https://phab.enlightenment.org/D2275) however we > cannot "securely" push those until we have a working VKbd > implementation to go with them. I pinged shiin to see if he could > also hack up a vkbd to go with. Which issues do you encounter on DnD? Thiep and I can help on this. > > While not a Top priority, support for wl_scaler and wl_viewport would > be remaining things to drop in after July 3. We have pending patches > for that also (https://phab.enlightenment.org/D2485) however those > need some refactoring. > > > i am saying this from the perspective that we get a fair number of > > "does e run wayland yet" kind of questions and the answer is always > > nebulous. i think we want a clear state of play for an e20 release. > > > > While I have not tested it yet, Mike has updated/refactored my > initial XWayland branch and pushed that upstream already which means > we should have working XWayland support now. I've not tested it yet > myself however he did manage to get Firefox running with it (which is > good news) :) > > E/Elm apps are running good in E-Wl. Gtk apps also (tho Some gtk apps > have popup menu placement issues according to Phab reports). I don't > suspect that those are Major issues and likely will take little time > to fix. > > QT apps on the other hand are a whole different can of worms. > Apparenly, QT5 has not been updated yet to support xdg_shell version > 5 which means, while the apps do run, they have quite a few issues. I > spoke with RzR about it and he plans to update QT5 to support > xdg_shell version 5 which should address issues there. > > There are a few pending buggers listed on Phab which I/we will be > addressing in the coming weeks tho I don't think any of them are > Major problems (in terms of functionality). > > It is likely that I may be forgetting something in this list, so if > you can think of something I may have missed, please ask. > > Cheers, > dh > > > -- > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & > sms for fault. Monitor 25 devices for free with no restriction. > Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
