https://bugs.kde.org/show_bug.cgi?id=362774
--- Comment #7 from Ivan Čukić <ivan.cu...@kde.org> --- > But adding an integer for the order to whatever object represents the activity Not as simple as that. That integer needs to be synchronized across all clients, to be introduced in a backwards-compatible manner to the syncing protocol, and be done so that all possible cases of service supports or doesn't support reordering, client supports or doesn't support reordering work (since the service and the client library are released separately). Then, you need to implement a pretty drag and drop UI for reordering. Then, you need to deal with the model updates - where does a new activity go? (and then deal with all the bug reports related to where you chose for it to appear - like we have for applications in the menu) > elsewhere) starting from 3 or certainly 4 activities, not dozens Reordering is (IMO) useful when you want to find something more quickly. If you have 3 or 4 activities, you can not have problems to find a specific one. p.s. Nothing here is about the pager specifically. It would be 'easy' to make the reordering for one thing, if the order does not need to get propagated to all the other places. And the pager is in the kdeplasma-addons so it can do whatever it wants to - they are less constrained to fit well into the rest of the Plasma workspace, than components that actually ship with Plasma. If this weren't the case, activity pager would not exist in the first place. -- You are receiving this mail because: You are watching all bug changes.
