I've added your description in the task description (and fixed a bit the text), it will be easier this way.

Yes, the example I gave for chess 2players was just one example from a quick guess. But like I said in my next comment, it was surely done for a reason anyway.

Connecting devices screen allows to :

• List all the tablets reachable from the control panel (shows a list with all users or grouped by groups)
• Target a specific group
• Send targeted groups a connection request
• Display each group user connection status (shows a list with all users or grouped by groups)
• Disconnect a user
• Disconnect a group

Main screen allows to access:

• Dashboard screen
• Connecting devices screen
• Following results screen
• Managing pupils screen
• Manages sequences screen
• Managing workboard screen

An option to hide the titles of these screens in the menu allows to gain some place once the user knows the meaning of each icon.

For chess, I'm not sure if it was to not click by mistake when you play with someone else.
The undo/redo only removes/replays the last hit for the current game.
If we restart, we clear the history and everything from the previous game.

All good points.

... also to complete my comment about chess 2player mode, as the reload button is specifically made to appear only at the end of the game, it confirms that it was intended to work this way for some reasons.

In T13633#240330, @echarruau wrote:

String freeze:
As we are in string freeze I would simply propose for the time being to get rid of the second level (too redondant), but I would open a ticket to improve solar system this way.

In T13633#240234, @jjazeix wrote:

Bouncing is due to the fact that we add/remove the "Hint" for some questions. It is clearly not the best, maybe we can have some exception for the bouncing (only have it on some cases)

I would prefer to not add a restart button when it's not really necessary for using an activity.
Also, as a general rule, we should avoid having more than 4 buttons in the bar as much as possible as it makes the bar (and so the buttons) smaller on smartphone with vertical screen, especially if we have the levels buttons.

As a prototype I made kglobalaccel use dbus activation (https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#dbus) if the desktop file specifies it is dbus activatable instead of manually parsing Exec fields. Also a patch for spectacle to see how it would work.
https://invent.kde.org/frameworks/kglobalaccel/commit/78baef0af7ec56db115f9e2c726a714a8684761b
https://invent.kde.org/graphics/spectacle/commit/a43c16d395ef5c0f0373ccfa555db783052b6797

Can we add @tcanabrava to the list of potential candidates for the Advisory Board?

Meeting Minutes
17 September 2020

Hi,
Level1 (with image):
We have twice the questions because some pupils have a visual memory and can, from the image proposed, remember where the planet is located in the planets row.
From this location, pupils that have understood that furthur you are from the sun longer is a year, colder it is, the one that have in mind that except for mars the size of the planets follows a regular increase and decrease size can deduct some of the answers from the facts known about earth (365 days, -30 to 50 degrees, 24 hours etc...).
I would say that the image level is the deduction level.
Image 2 (without image):
Here pupils test what they memorised.

In T13631#240328, @alex wrote:

dolphin plugins that solely target developers

That also has mountiso and dropbox plugins, these are not just for developers

dolphin plugins that solely target developers

In T13631#240302, @ngraham wrote:

I don't try to nanny our users into accepting all those extra dependencies.

You're a Gentoo packager, right? My concern here is for users who want things to just work out of the box, not users of distros geared towards technical experts. That's a different problem space. :)

By far not everyone of our users is an expert, and I don't see the numbers to back this up as a huge problem yet. There sure has been the odd forum thread about missing stuff, but through our KDE Wiki it is common knowledge that users are supposed to use the plasma-meta package and that settles it real quick. Is it really beginners who randomly install the minimal plasma-desktop package (if they do, why?) rather than following the distro's Wiki, or is it the tinkerer who doesn't own up to hunting for features manually after going the minimal route? How many distros get it actually wrong, can it be improved by adding RUNTIME infos to cmake? Where are those bug reports you see coming from? Those are the questions before establishing this as a problem we need to fix by lumping repositories together. And that would change it for something like Arch where binary packages are not often being split, but not for others like Debian where the amount of binary packages may not even change except where they pull their sources from.

Hmm. Nextcloud Text is working fine here and at many other instances on the internet. There might be a configuration issue here. Could you create an issue here? https://github.com/nextcloud/text/issues
Thanks.

But I could still just copy the relevant lines into kcmshell directly instead of linking.

Any update here? Can this hack be dropped now?

Rebased to current master and merge request created:
https://invent.kde.org/plasma/kwin/-/merge_requests/267

• More const QString.

I assume so. I might be wrong. :)
I'm looking how other app that uses kconfigxt and toolbars behave.

I agree with moving the runners, but it is also planned to introduce some new APIs so that the Kate/Konsole profiles runners can be replaced and are provided within the Kate/Konsole apps themselves. For the remaining runners it makes totally sense.

In T10650#240171, @cubix wrote:

Alright. Are we supposed to refresh it then everytime? Or if the count of messages decreases - a workaround maybe?

I don't try to nanny our users into accepting all those extra dependencies.

From me also a -1, mostly because of the dependency tree. Stuff like ffmpeg and Samba have a *huge* dependency tree.

In D23883#530551, @davidedmundson wrote:

It only exists as a hack around some Qt5.9(?) bug to allow plasma stuff to be in wayland without needing us to force an environment variable.
Personally I want to kill it, but AFAIK SuSE still uses it. Worst case we can just copy the 5 lines into kcmshell.

Sounds great. Thanks :)

Is text under icons your personal setting? Will I see text alongside icons then?

In T13631#240269, @ngraham wrote:

I have seen many bug reports and user frustrations whose root cause was not having these packages installed--whether due to bad distro defaults or not knowing about them when using Arch or Debian. We can bug distros to have better defaults and write better documentation and such, but merging their functionality into other repos eliminates the whole class of bug altogether. That's a win IMO.

I can't set text alongside icons or text below icons, the app will get that from plasma settings by default. this just tells the toolbar what icons to load by default, all the other configuration are defaulted to kde global settings.

+1 to a toolbar. My suggestion would be to have text alongside icons, as we rarely (=pretty much never) use text under icons and would thus be more consistent and free more vertical space. If the button's don't fit in the toolbar, some buttons could also work without their labels, such as copy and paste or s.lit viev, since their icons are extremely recognizable already. Also please consider using some separators and/or fill width spacers

Nice! Here would be my initial recommendations:

Also, this makes konsole easier to use for people with reduced mobility (hitting key combinations is harder than a mouse click) and for new users.

And fixed in commit e66601933b9dd1c132bcf0efcd71dedeb864eac4 :-)

stuff in *-extras is not core functionality but provides additional features that one may or may not want to use

Thanks for that explanation. I will test that activity to double check that behavior after a version with your fix is released.

Fixed in commit 29e6b0a986a659104851d73e296a54ddcfab7289

In T13635#240258, @tysonwilliams wrote:

Ah, yes, yes! Thanks. I am submitting too many bug reports!! ;)

OK, I'll add that yes.

Distros can fail to pre-install them in their Plasma packaging, leading to users missing content and having a sub-optimal user experience

Sure, distros make mistakes too, but that kind of mistake is easy to address downstream

Users of DIY distros like Arch or Debian can fail to install them and wind up missing content and having a sub-optimal user experience

That's the price you needs to pay for using such a distro. You need to think about what to install. Following the logic of why some people prefer this kind of distro one can argue that some people do not install these extra packages on purpose.

Reduces the clarity of the software's status: Is this stuff core functionality or not? On the one hand, it's hosted on KDE infrastructure and tracked on KDE's Bugzilla. But on the other hand, it's possible to not install it

How is merging it clarifying anything? Right now the status is pretty clear IMO: stuff in *-extras is not core functionality but provides additional features that one may or may not want to use

On the flip side, I see no major advantages to having stuff split into these extra repos.

For a framework like KIO I made my point above. A similar point can be made for Plasma too. Plasma is used as a base for various embedded products (Plasma Mobile, Mycroft, Plasma Bigscreen, kiosk deployments. I've also seen kwin used as a standalone window manager in commercial products). For these kinds of projects it is beneficial to be able to deploy a core-only version of our product since stuff like installation size does matter.

Ah, yes, yes! Thanks. I am submitting too many bug reports!! ;)

Isn't it land safe instead of solar system?

I am unsure that the intended behavior is suppose to be for these left and right buttons in this activity.
There doesn't seem to be a maximum "level" number for this activity. Instead, there seems to be a fixed number of questions (for the selected solar system object) and clicking left or right selects one of the questions uniformly at random. In particular, it is possible to be looking at some question Q, click right, and be presented with question Q again.

In T13631#240230, @ngraham wrote:

I remember hearing about a proposal to move ApplicationLauncherJob into KService to bypass just that issue.

That's T13590.

Alternatively, do you see a better place to merge kio-etras?

No, but I don't see a pressing need to merge it anywhere either

Thank you for fixing it! :)

It's fixed: https://invent.kde.org/education/gcompris/-/commit/e2a4dfde847dbf587f86bc0ae45c223857a090c4

In T13633#240236, @tysonwilliams wrote:

Nothing is printed to the console because of step 4. What happens when you do step 4?

Ok, I just managed to reproduce. Configuration file needs to be empty!

Nothing is printed to the console because of step 4. What happens when you do step 4?

Are there logs in the console? I'm trying to reproduce but can't for now

Bouncing is due to the fact that we add/remove the "Hint" for some questions. It is clearly not the best, maybe we can have some exception for the bouncing (only have it on some cases)

Thank you

In T13631#240200, @nicolasfella wrote:

-1 on merging kio-extras into kio. For frameworks we need to keep an eye on the dependency tree and kio-extras has quite a number of additional dependencies (phonon, samba, libssh, mtp, kdsoap etc) and the features that kio-extras provides are usually. I don't want my app to depend on all of that just to be able to use ApplicationLauncherJob et al

I'll take a look :)

Also, sometimes clicking left or right causes the buttons to "bounce up" from a single point below the bottom of the screen like then do after step 2. And sometimes they don't. I don't understand why this behavior differs. I expected that the only time the buttons would do this bouncing move is after step 2 and never after clicking the left or right buttons.

Yep, that is right. I am just recommending better formatting of numbers. No effect on the string freeze.

increases work for KDE's release team and distro packagers to have more packages to tar, package, update, manage, etc

-1 on merging kio-extras into kio. For frameworks we need to keep an eye on the dependency tree and kio-extras has quite a number of additional dependencies (phonon, samba, libssh, mtp, kdsoap etc) and the features that kio-extras provides are usually. I don't want my app to depend on all of that just to be able to use ApplicationLauncherJob et al

Thanks for the useful feedback!

LGTM

We have since moved to GitLab. Would you mind re-opening this as a merge request at https://invent.kde.org/plasma/kwin/-/merge_requests/? Thanks!

Alright. Are we supposed to refresh it then everytime? Or if the count of messages decreases - a workaround maybe?