KirigamiProject
ActivePublic

Recent Activity

Jul 3 2020

tosta added a comment to T13216: Make Koko a possible successor of Gwenview.

I think the image gallery (or image/video) app must be like Piktures is for Android.

Jul 3 2020, 10:41 AM · Kirigami, Plasma: Mobile, VDG, Goal: Consistency

Jul 1 2020

ngraham added a comment to T13256: Come up with a solution for displaying QQC2 elements in Plasma.

One idea I've been throwing around recently is using the Plasma theme for apps too, by making the QStyle load Plasma theme SVGs. This would eliminate the potential problem of Plasma dialogs having a different appearance from apps, because all of them would be using the same theme in the first place. It would also allow a single theme to apply to the entire system, producing a major consistency win, and these newly-all-encompassing systemwide Plasma themes are share-able via GHNS, which is not currently possible using binary QStyle widgets themes. In so doing, the Breeze QStyle would be essentially transformed into a theme engine. Alternatively I suppose we would fork it into a new one, or write a new one.

Jul 1 2020, 2:14 AM · Kirigami, Plasma, KF6

Jun 13 2020

ngraham added a comment to T13256: Come up with a solution for displaying QQC2 elements in Plasma.

I wouldn't be in favor of making config windows have the plasma style. In other respect they would match the desktop style (e.g. titlebar) so that would just be weird IMO.

Jun 13 2020, 2:10 AM · Kirigami, Plasma, KF6

Jun 11 2020

mart added a comment to T13256: Come up with a solution for displaying QQC2 elements in Plasma.

feasible technical solutions at the moment are

  • QQmlAbstractUrlInterceptor based solution: kinda error prone but easy to do
  • configuration windows in a separate process: quite complicated and error prone, would take a year to do
  • having config windows with the plasma style
Jun 11 2020, 1:12 PM · Kirigami, Plasma, KF6
ngraham added a comment to T13256: Come up with a solution for displaying QQC2 elements in Plasma.

Related to but necessarily a duplicate of T11558: kill plasma components in favour of qqc2-desktop-style. If we do T11558, we won't have to do this, but we can do this without having to do T11558.

Jun 11 2020, 5:39 AM · Kirigami, Plasma, KF6

Jun 9 2020

ngraham updated the task description for T13256: Come up with a solution for displaying QQC2 elements in Plasma.
Jun 9 2020, 5:49 PM · Kirigami, Plasma, KF6
ngraham claimed T13256: Come up with a solution for displaying QQC2 elements in Plasma.
Jun 9 2020, 5:46 PM · Kirigami, Plasma, KF6
ngraham updated the task description for T13256: Come up with a solution for displaying QQC2 elements in Plasma.
Jun 9 2020, 3:37 PM · Kirigami, Plasma, KF6
ngraham renamed T13256: Come up with a solution for displaying QQC2 elements in Plasma from Come up with a solution for QQC2 elements in Plasma to Come up with a solution for displaying QQC2 elements in Plasma.
Jun 9 2020, 3:37 PM · Kirigami, Plasma, KF6
ngraham triaged T13256: Come up with a solution for displaying QQC2 elements in Plasma as Normal priority.
Jun 9 2020, 3:35 PM · Kirigami, Plasma, KF6
ngraham closed D29462: Fix Kirigami.Units.devicePixelRatio=1.3 when it should be 1.0 at 96dpi.
Jun 9 2020, 2:47 PM · Kirigami

Jun 8 2020

davidre added a comment to D29462: Fix Kirigami.Units.devicePixelRatio=1.3 when it should be 1.0 at 96dpi.

Ping

Jun 8 2020, 7:30 AM · Kirigami

Jun 1 2020

cblack abandoned D28643: WIP, RFC: Add ColorInfo class.
Jun 1 2020, 7:29 AM · Kirigami

May 30 2020

twitt added a comment to T13216: Make Koko a possible successor of Gwenview.

@ognarb thanks! It did not work out of the box, but it helped me make it run (I'm on arch linux and had to change the kirigami version to 2.4 and remove the usage of ImageColors to make it run)

May 30 2020, 4:43 PM · Kirigami, Plasma: Mobile, VDG, Goal: Consistency
ognarb added a comment to T13216: Make Koko a possible successor of Gwenview.

@twitt The error you are getting is because you didn't source the prefix.sh with source prefix.sh then it should just work™.

May 30 2020, 2:39 PM · Kirigami, Plasma: Mobile, VDG, Goal: Consistency
twitt added a comment to T13216: Make Koko a possible successor of Gwenview.

Recently I got into the source code of Gwenview. I was missing a crop tool that allows arbitrary rotations. While a rough implementation in Gwenview was quite easy, I never solved all problems to also retain the old behavior, which is why I not yet committed it. However, after getting a deeper look into the codebase of Gwenview, I agree that several things could be refactored or rewritten, although I still like the application itself. If someone could review/help, I would spent some time on polish or adding some new features.
Personally, I am not a fan of mixing mobile and desktop applications as it is difficult to implement a good usability that works with touch, mouse and keyboard at the same time. A prominent example might be Adobe Lightroom which still fails to have a unified user interfaces that works for mobile and desktop devices.
However I the mookups look cool and also very much like the name Koko for an image application. Unfortunately I never worked with QML and I was not even able to start it (error message: module "org.kde.koko" is not installed :/ ). According to the git log there were nearly no new features added within the last two years, so I am not sure if replacing Gwenview would help to gain activity.

May 30 2020, 12:40 PM · Kirigami, Plasma: Mobile, VDG, Goal: Consistency

May 29 2020

manueljlin updated the task description for T13216: Make Koko a possible successor of Gwenview.
May 29 2020, 7:27 PM · Kirigami, Plasma: Mobile, VDG, Goal: Consistency
manueljlin updated the task description for T13216: Make Koko a possible successor of Gwenview.
May 29 2020, 7:16 PM · Kirigami, Plasma: Mobile, VDG, Goal: Consistency
niccolove updated the task description for T13216: Make Koko a possible successor of Gwenview.
May 29 2020, 6:25 PM · Kirigami, Plasma: Mobile, VDG, Goal: Consistency
niccolove added projects to T13216: Make Koko a possible successor of Gwenview: VDG, Plasma: Mobile, Kirigami.
May 29 2020, 6:12 PM · Kirigami, Plasma: Mobile, VDG, Goal: Consistency

May 19 2020

mart accepted D29462: Fix Kirigami.Units.devicePixelRatio=1.3 when it should be 1.0 at 96dpi.

looks good

May 19 2020, 11:01 AM · Kirigami

May 18 2020

cblack added a comment to D29694: Introduce Avatar component.

This is being moved to GitLab.

May 18 2020, 4:59 PM · Kirigami
cblack closed D29694: Introduce Avatar component.
May 18 2020, 4:58 PM · Kirigami
cblack abandoned D28873: Add SwipeNavigator component.

Moving to a GitLab MR

May 18 2020, 4:50 PM · Kirigami
cblack added a comment to D28873: Add SwipeNavigator component.
In D28873#672598, @mart wrote:

what should happen in this case?

May 18 2020, 4:49 PM · Kirigami
nicolasfella added a comment to D22868: Revamp Kirigami.AboutPage.

can this be closed?

May 18 2020, 3:59 PM · Kirigami
broulik abandoned D25984: Load translations.

Looks like D27595 fixes the issue

May 18 2020, 3:18 PM · Kirigami
ngraham closed D29785: Always use Window colorset for AbstractApplicationHeader.
May 18 2020, 1:45 PM · Kirigami
mart accepted D29785: Always use Window colorset for AbstractApplicationHeader.
May 18 2020, 1:17 PM · Kirigami
ngraham added a comment to D29785: Always use Window colorset for AbstractApplicationHeader.

Not all of the headers use toolbars, but I thought the idea was for them all to use a consistent base appearance? @mart?

May 18 2020, 1:16 PM · Kirigami
apol added a comment to D29785: Always use Window colorset for AbstractApplicationHeader.

I wonder if this should be specified in ToolBarApplicationHeader instead.

May 18 2020, 1:00 PM · Kirigami
mart added a comment to D28873: Add SwipeNavigator component.

what should happen in this case?

May 18 2020, 9:46 AM · Kirigami
mart added a comment to D28873: Add SwipeNavigator component.

can you add an example about it in /examples ?

May 18 2020, 9:44 AM · Kirigami

May 15 2020

ngraham added a comment to D28873: Add SwipeNavigator component.

Looking fiiiiine.

May 15 2020, 5:51 PM · Kirigami
ngraham updated the summary of D29785: Always use Window colorset for AbstractApplicationHeader.
May 15 2020, 5:47 PM · Kirigami
ngraham requested review of D29785: Always use Window colorset for AbstractApplicationHeader.
May 15 2020, 5:40 PM · Kirigami
cblack updated the test plan for D28873: Add SwipeNavigator component.
May 15 2020, 5:23 PM · Kirigami
cblack updated the diff for D28873: Add SwipeNavigator component.

Improve the small toolbar

May 15 2020, 5:14 PM · Kirigami
Zren added a comment to D29462: Fix Kirigami.Units.devicePixelRatio=1.3 when it should be 1.0 at 96dpi.

The plasma-framework patch is D29463

May 15 2020, 5:02 PM · Kirigami
cblack updated the diff for D28873: Add SwipeNavigator component.

Rebase on master

May 15 2020, 4:36 PM · Kirigami
cblack updated the diff for D29694: Introduce Avatar component.

Unsplit template and control for documentation purposes

May 15 2020, 4:11 PM · Kirigami
cblack added inline comments to D29694: Introduce Avatar component.
May 15 2020, 3:51 PM · Kirigami
cblack updated the diff for D29694: Introduce Avatar component.

Split into a template; make borders customisable

May 15 2020, 3:51 PM · Kirigami
cblack added inline comments to D29694: Introduce Avatar component.
May 15 2020, 3:19 PM · Kirigami
broulik added a comment to D27595: Watch for language change events, and forward those to the QML engine.

Is there no better way to do this? e.g. the KWin Rules KCM spends 20% of its startup time in "retranslate" :/

May 15 2020, 2:09 PM · Kirigami
mart added a comment to D29462: Fix Kirigami.Units.devicePixelRatio=1.3 when it should be 1.0 at 96dpi.
In D29462#668542, @mart wrote:

the different Units.qml depend from the style, QT_QUICK_CONTROLS_STYLE
all of them, including those in plasma-framework should be updated at once

May 15 2020, 12:59 PM · Kirigami
mart requested changes to D29694: Introduce Avatar component.
May 15 2020, 12:56 PM · Kirigami
mart added a comment to D29694: Introduce Avatar component.

I would like this class to be splitted in Templates/controls, so different styles could make it look slightly sifferent (or anyways easier for the app developer to make one that looks just slightly different)
the root component should be a Control, with image/icon/initials in contentItem and background collor/border in background
the one in templates would not have a background the one in controls would instantiate the one in templates and give it one.

May 15 2020, 12:56 PM · Kirigami
mart added a comment to D28873: Add SwipeNavigator component.

yes, that screenshot is really broken.
to me is important that the tabbar tries to take all the space available before doing any eliding.
Probably whether starting to elide a lot and make the tabs actually scrollable, will depend case by case depending fro mthe app

May 15 2020, 12:01 PM · Kirigami

May 14 2020

ngraham added a comment to D28873: Add SwipeNavigator component.

When there isn't room to show all labels, eliding the labels or collapsing the inactive tabs to square-ish icons-only things that are still clickable/touchable would seem to make more sense to me. The above screenshot kind of looks like a visual glitch IMO.

May 14 2020, 10:28 PM · Kirigami