- User Since
- Sep 14 2018, 11:24 AM (53 w, 2 d)
Sat, Sep 14
Regarding 1b: maybe tabs on the top would look better than buttons? Something like this: (terrible mock, forgive me)
Thu, Sep 12
Tue, Sep 10
Mon, Sep 9
Thu, Aug 29
Sun, Aug 25
Sat, Aug 24
Aug 14 2019
I'm currently on vacation. Please make any change you consider necessary.
Jul 30 2019
Please keep in mind that changing a name is terrible on a promo point of view, as people might generally recognize a name as a good project. Also, renaming might not end well: just look at kde -> plasma.
Jul 27 2019
Jul 26 2019
I don't like the current behaviour of the "Get plasma here." button; especially for people without too much knowledge about the linux world, being redirected to a list with 40 different distributions and almost no way to distinguish between them is not ideal. I think the webpage should try to redirect the user to KDE Neon, unless the user specifically wants for a list of compatible distributions. Furthermore, I would also add the option to see a page with a list of computers with plasma by default ("Buy a computer with plasma").
Jul 25 2019
Jul 21 2019
Jul 19 2019
Jul 15 2019
I would think we only need two different sidebar appearances for this: The one used in System Settings when there are many entries and D20908: RFC: Redesign QML applet configuration windows when there are few.
Jun 25 2019
Here's my view on how coordination should be done, especially when talking about inconsistiencies about the user interface:
Jun 23 2019
Should T10243, which is about redoing many Breeze icons, be a subtask of this as well?
Jun 22 2019
DWD is also very controversial and difficult to implement. Either way, this task is moving in a good direction, becoming more visually appealing for both sides, and way more feasable in the short term.
I also agree to use a subdle 90% opacity on the tools area as I stated before, but I'd prefer it to be applied either on all windows or only the active one. When applied only to inactive windows, it would be waay less noticeable and appealing.
Jun 21 2019
I think the two inputs are similiar enough to achieve a pretty good consistency as a whole, with only few exceptions. Right-click is only one possible gesture for touch screen/pad input, so let me approach this in a more holistic way, using an example of possible gestures (mix of Windows', iPadOS, and own):
Jun 20 2019
Currently, Kvantum is able to use different colors for toolbars based on their location, so that is feasable. I think it should get the tools area color only when it's put on the top, and leavingi everything else, including statusbar, with the normal lighter gray. When the toolbar is on the sides or on the bottom, it should be part of the window, and not of the tools area.
I agree that a two-finger tap is not optimal in many cases, what I was thinking of was rather using both a two finger tap and press and hold in both the touchscreen and the touchpad, thus providing consistence between them.
Jun 17 2019
What do you think of: (opaque on the left, transparent on the right)
I strongly agree with the idea of consistency between touchpad and touchscreen when possible. An example of that can also be a click with two fingers, which could open the context menu in both input methods.
That came off sounding kind of harsh, sorry.
Last week I had to install Windows (bad experience overall), and I took that as a chance to consider their choises on this matter. One thing that I noticed is that Windows is using its fluent (/transparent window) effect in many applications, and it's used as a way to help the user understand which one is the active window. When the window is no longer active, the window become opaque. I found it quite interesting to use:
Jun 14 2019
vvave, index, nota and buho all have a major "feature" that sets them apart from the other mentioned apps. They are targeted towards a mobile platform. Especially for Dolphin vs Index this makes perfect sense because IMHO trying to adapt Dolphin to work good on mobile would not be wise.
Jun 13 2019
Jun 11 2019
Jun 6 2019
Jun 2 2019
I tried to guess a couple of mocks of the style; here's dolphin:
May 2 2019
Given the time, four members is perfect to me.
Some VDG members expressed the expressed the will to partecipate. Since whoever proposes a wallpaper should not also be a judge, it was proposed to create a jury from the VDG that will not partecipate in the contest. If they are avaiable some jury member who were proposed are Andy and @ngraham. Also, @flipwise and @GB_2 also said they would be avaiable to be member of it.
Mar 30 2019
Mar 18 2019
Thank you so much for the detailed answer. I was able to do [1,2,4,5].
Unfortunately, I do not understand how to add margin in elements in . I tried to use anchor-based margin, but I see that in some files anchor is not used at all, and where it is used, the margin won't affect the appareance at all. I'm sorry to disturb you again, but may I ask you what the correct approach would be here?
Mar 9 2019
The dock has a real margin, meaning that interactions (/mouse clicks and hovers) made between the panel and the screen border are not be managed by latte, and an auto-hide panel will disappear if mouse is there. Approaching the edge with the mouse will show the autohidden dock anyway. Example:
Feb 28 2019
I personally feel like the most intuitive way is to create a KCM just for Layout, and then make the Look and Feel able to override those setting. In this way if you only want to change the layout you will change it in the Layout KCM, but Look and Feel would still be able to change the layout. If I recall correctly, that should be the same relationship between Look and Feel and Plasma Theme.
Feb 15 2019
Feb 13 2019
It seems like it landed. Please tell me if I screwed up anything.
Feb 12 2019
I do not have a developer account. I requested one some days ago with no answer yet.
Feb 4 2019
- fixed whitespace, sorry
- Made windows show even without export-pdf flag
Jan 31 2019
- Made window show on pdf print and removed trailing spaces
Jan 30 2019
- Removed connection between job and exiting; added todo
I have some doubts:
- Moved QString pdfFileName to KoApplicationPrivate
This solution is Qt <5.12 friendly
- Adding pdf filename as propriety of KoApplication
What have I Done:
- Added slots in KoApplication to handle pdf and print.
Jan 29 2019
- Removed unnecessary newlines
- Made slotFilePrint depend on signal loadCompleted to avoid it running before remote file being complete
Jan 26 2019
I'm not sure on how to do that, do you have any tip?
openDocumentInternal is called by openDocument, which is called in KoApplication just before checking the arguments. When it sees the print argument, it calls slotFilePrint. openDocumentInternal downloads the document in async. Should it be made not async, or is there another way to make it wait until the other process ends? Also, "slotLoadCanceled" is already implemented, or were you talking about something else?
Jan 23 2019
I tried differents files (locale and remote, opening and printing), and everything works okay. Other applications work normally, but calligrasheets still crashes when trying to print a remote (odt) file - but I can see the file is downloaded correctly, so it looks like a different problem (calligrasheets manages printing?).
About removing features from slotLoadCompleted, it is important to notice that it is only called by openDocumentInternal itself, so that should not be a problem.
I've seen that openDoumentInternal is called every time a remote document is used as input. I'm not sure if it's also used in different scenarios.
- Moving the if from slotLoadCompleted to openDocumentInternal.