- Queries
- All Stories
- Search
- Advanced Search
All Stories
Mar 17 2018
That can not be done yet without recompiling the software, and this is exactly part of the features we want to provide on the administration tool.
Please rebase to master
Needs rebasing to master
I think this is fine as-is.
Thank you!
About what you said about GCompris allowing teachers to create games for the platform, it's not so straight forward yet.
S before T
Patrick fixes
I guess <> makes sense. I dont't know if there is a standard for this (maybe ask VDG ), but feel free to go ahead with <>
While looking as this: perhaps it make sense to also switch to use "<#>" instead of "[#]", like known e.g. from KWin? Is there any standard for such instance label numbering?
In D11377#227808, @graesslin wrote:Please also add a kconf update script to reassign the shortcuts. Also please add unit tests for the new shortcuts.
In D11305#227826, @graesslin wrote:I'm sorry but this breaks Wayland, auto-hiding panels and much more.
Sorry, I don't use Wayland because many features I use per day basis aren't working. Should have tested on Wayland too, sorry.
So for now I think I would also aim for the workshop format on presentation of innovative tools.
Nice that they agreed.
In D10796#218320, @nicolasfella wrote:I like the color, but I'm not sure about the disabling.
Right now, only the playPause button is disabled, but what about the other buttons?. If we go with this approach, we should disable all buttons instead of removing them. Why should the playPause button be any different?
IMHO we should remove buttons if the functionality is unavailable, disabled buttons might look a bit broken. The only place where it might make sense to disable a button is when either next or previous is unavailable (probably because we are at the beginning/end of a track list) to keep symmetry.
This looks good. I would just recommend some minor changes.
The patch appears to be correct, but I don't know if removing the ui file is a good thing after all. @tcanabrava @laysrodrigues what do you think ?
- rebase
I fixed the problem: the code now only counts the the art as transferring once the remote actually replies with the art.
So far got a few comments about this being a nice idea in general, and one already about something in the code. So far all positive. Now, where are the negative ones, there must be some :)
If not or even then, I hope for some good people for some further detailed review of the code and/or feature in the next days, please :)
In D11017#226787, @albertvaka wrote:The payloads API seems to be broken and is causing problems in the notifications plugin because we send the notification icons with it (see my email in the kdeconnect mailing list). I think we should make sure it works well before making more plugins use it.
The organisers have agreed to let us have a booth, run demonstrations of KDE Edu software and run workshops for teachers, students, etc.
Also do we want this or two options instead:
- no expanding: maximumWidth = preferredWidth, and
- no shrinking: minimumWidth = preferredWidth?
It is not working because the bundle is corrupt. Krita cannot open it.
I cannot push the patch as arc fails with:
Sorry for the delay
I'm sorry but this breaks Wayland, auto-hiding panels and much more. We need a different solution for the problem. E.g. a signal beginSwitchDesktop and endSwitchDesktop or a property isCurrentlySwitchingDesktops. Also this is only an issue for X11 windows and we don't do feature changes for X11 any more.
Just adding a note to the suggestion by Fuchs: we used to have this in the KDE 4 times, it was highly confusing, users didn't understand that the button acts on the current theme. Due to that in the rework we changed and added the config button to the decoration list. IIRC it initially was outside the preview area but was moved in later on.
Hi :)
I'd like to thank you all for the work done on supporting SVG and RTL text. This is really appreciated.
Please don't. This comes up again and again and we already had to revert a commit which did this for the complete code base. The benefit is too low for breaking the commit history. For more information see https://mail.kde.org/pipermail/plasma-devel/2017-June/071237.html