Tips in splash screen on startup (suggestion)

[samuel ammonius]

Hello everyone,

KDE has a lot of features that most people don't know about, so what if a
tip was shown on the splash screen during each startup? For example, the
first startup could show:

> Tip #1: You can open a terminal inside Dolphin using CTRL+SHIFT+F4

at the bottom of the screen. Then the next could show

> Tip #2: You can manage your Google Drive by adding an online account in
the settings

(I'm just using these examples to show what I mean by "features that most
people don't know about". There's definitely a ton of these, so if the
developers of different projects added a few tips to the list, these
features could be used by more people)

There could be a setting to configure them to:

   1. Numerical order
   2. Random
   3. Hidden / Disabled


Thoughts?

Sam

Re: Product organization in Bugzilla

[samuel ammonius]

I actually never even noticed the search bar at the top until now.
It might also be a good idea to place the search bar under the
select a product category" header to make it more obvious.

Re: New releases for bugfixes

[samuel ammonius]

Thanks. I hadn't thought of a lot of these issues before.

I think the biggest one is that If there's an update that the package
manager didn't
know about, the user would have to update right after installing, and the
bug would
come back if the user re-installed or updated the app. Sorry everybody.

Re: New releases for bugfixes

[samuel ammonius]

> and you marry upstream binaries with the distribution update-manager how?

You don't need to. The app can just check the latest bugfix for that
version on git
and install it if it isn't installed. I don't understand why you stress the
need for the
package manager to have anything to do with the update if it's just a bug
fix.

> in the way that distributions have different library versions

Ok, I think I get your point. Some libraries add/remove/replace features
and KDE
projects may be using macros to make all library versions work. I hadn't
thought
of that.

> bla

So the teensy weensy security risk is suddenly a huge deal and when I try
to fix it for you I'm talking nonsense?

> more space than some of my systems at a whole

It's like 30 megabytes.

> a little bit of more realistic view for such nosense would be nice too
> if anything you propose would become real i had to switch away from KDE

If you got a notification saying "Minor bug fix released for Kate. Would
you like
to install an update without using the package manager?", would it be so bad
that you would drop KDE? Because that's all I was suggesting (only without
the
"without the package manager" part because I was just communicating my
point).

Re: New releases for bugfixes

[samuel ammonius]

> because outside the windows world central package management is the norm
> and based on "least privileges" applications must not have the
> permissions to change itself

I didn't mean a background update. I meant the user could get a dialog or
notification asking them to update, and if they press "yes" they can enter
their
root password and the app can update itself and restart.

> and for each distribution with different dependencies and libraries

How does KDE have different dependencies for different distros? (To be
honest
though, I only mentioned this method because I thought having multiple
options
would advertise the idea in the second method)

> if you don't care for security

The security risk is very small, and it can be fixed in a lot of different
ways. The
app could create a folder that only root can access within the /tmp folder.
If even
that's not secure enough, the app could create source files with just
"#define MAIN_CPP_SOURCE" and compile with "-DMAIN_CPP_SOURCE=[the
source code] so that it never has to be stored on the disk before being
compiled.

> which distribution installs a compiler by default so that one can avoid
> touching it?

I don't think I've ever used one that *doesn't* come with at least gcc
installed.
I've tried Ubuntu, Debian, Fedora, and OpenSUSE. Now that I think about it
though,
they don't come with g++ installed, and they definitely don't come with Qt
headers
installed, but they don't take that much space, and maybe they can also
just be
placed in /tmp and removed after the update.

It didn't take me 10 minutes to answer these questions in my head, so I
don't
see why you're trying to scrap the idea so quickly for its faults instead
of trying
to fix them. A bit of constructive criticism would be nice.

Cheers,
Sam

Re: New releases for bugfixes

[samuel ammonius]

Bug fixes don't change the entire package, only the executable, so
why can't apps just be programmed to update themselves? There
could be precompiled binaries stored on the git repos of each project
for a few CPU architectures, or maybe the app could even recompile
itself inside /tmp since most systems KDE runs on come with a compiler
by default (and macros could also be stored so that apps have the
same configuration throughout updates).

Cheers,
Sam

On Thu, Sep 8, 2022 at 11:58 AM Heiko Becker  wrote:

> On Thursday, 8 September 2022 13:59:43 CEST, Ahmad Samir wrote:
> > From the git-archive manual page:
> >
> > «git archive behaves differently when given a tree ID versus
> > when given a commit ID or tag ID. In the first case the current
> > time is used as the modification time of each file in the
> > archive. In the latter case the commit time as recorded in the
> > referenced commit object is used instead. Additionally the
> > commit ID is stored in a global extended pax header if the tar
> > format is used; it can be extracted using git get-tar-commit-id.
> > In ZIP files it is stored as a file comment.»
>
> Before anybody tries that *now*, at least for Gear the tarballs are
> currently created with git archive --remote=kde:$repo $branch ..
> So they currently won't have that information.
>
> Regards,
> Heiko
>
>

Re: Incubating app (Git Klient)

[samuel ammonius]

>From my current understanding, a sponsor is a KDE developer who works with
KDE's GitLab managers to make a new repo for your project and make you a
KDE developer.

On Mon, Aug 22, 2022 at 5:14 PM Hamed Masafi  wrote:

> What is a sponsor and what does it do?
>
> On Mon, Aug 22, 2022, 21:00 Harald Sitter  wrote:
>
>> Heya,
>>
>> You'll need a sponsor https://community.kde.org/Incubator ... not me.
>> I'm lazy :)
>>
>> On Sun, Aug 21, 2022 at 11:01 AM Hamed Masafi 
>> wrote:
>> >
>> >
>> > Hello
>> > As a longtime kde fan(since 3.4), I would love to contribute to this
>> group.
>> > I am developing a graphical client application for git. I think it is a
>> good option to enter the world of kde.
>> >
>> > Features of this program:
>> >   - The icon displays the files in the Gate folder according to their
>> status in Dolphin.
>> >   - For easier access to the right-click menu of files and folders,
>> options such as pull, push, delete, ignore, etc. have been added.
>> >   - Graph display of commits.
>> >   - General Git operations such as pull, push, fetch.
>> >   - Show branches and distance of commits from the reference branch.
>> >   - View files and file contents in each branch or commit.
>> >   - Compare files, folders, branches and commits in a graphical
>> environment.
>> >   - Merge conflicting files in git.
>> >   - Management of remotes, tags.
>> >   - Auto-completion when writing a commit message.
>> >   - Markdown editor (written but not yet added to the main program)
>> >   - And some extra features.
>> >
>> > The source is available here:
>> > https://github.com/HamedMasafi/GitKlient
>> >
>> > Currently, only I (Hamid Masafi) am working on the project.
>> > This project is currently on GitHub, but it can be moved to any other
>> repository if approved by you.
>> >
>> > Please take a look at this repository and let me know what you think. I
>> look forward to hearing from you.
>> >
>> > Best regards
>> > Hamed Masafi
>>
>

Re: Incubating app (Git Klient)

[samuel ammonius]

developer accounts
<https://community.kde.org/Incubator#:~:text=project%20developers%20have-,developer%20accounts,-Contact%20sysadmin%20to>
(I
meant to link it in my last message)

On Mon, Aug 22, 2022 at 2:17 PM samuel ammonius 
wrote:

> I'll try to help by being a sponsor. Reading through the incubator page, I
> found this
> <https://community.kde.org/Incubator#:~:text=(e.g.%20not%20on%20Github)>,
> so the app doesn't currently qualify. It will have to move to something
> like gitlab.
>
> What does developer accounts mean?
>
> On Mon, Aug 22, 2022 at 2:00 PM Harald Sitter  wrote:
>
>> Heya,
>>
>> You'll need a sponsor https://community.kde.org/Incubator ... not me.
>> I'm lazy :)
>>
>> On Sun, Aug 21, 2022 at 11:01 AM Hamed Masafi 
>> wrote:
>> >
>> >
>> > Hello
>> > As a longtime kde fan(since 3.4), I would love to contribute to this
>> group.
>> > I am developing a graphical client application for git. I think it is a
>> good option to enter the world of kde.
>> >
>> > Features of this program:
>> >   - The icon displays the files in the Gate folder according to their
>> status in Dolphin.
>> >   - For easier access to the right-click menu of files and folders,
>> options such as pull, push, delete, ignore, etc. have been added.
>> >   - Graph display of commits.
>> >   - General Git operations such as pull, push, fetch.
>> >   - Show branches and distance of commits from the reference branch.
>> >   - View files and file contents in each branch or commit.
>> >   - Compare files, folders, branches and commits in a graphical
>> environment.
>> >   - Merge conflicting files in git.
>> >   - Management of remotes, tags.
>> >   - Auto-completion when writing a commit message.
>> >   - Markdown editor (written but not yet added to the main program)
>> >   - And some extra features.
>> >
>> > The source is available here:
>> > https://github.com/HamedMasafi/GitKlient
>> >
>> > Currently, only I (Hamid Masafi) am working on the project.
>> > This project is currently on GitHub, but it can be moved to any other
>> repository if approved by you.
>> >
>> > Please take a look at this repository and let me know what you think. I
>> look forward to hearing from you.
>> >
>> > Best regards
>> > Hamed Masafi
>>
>

Re: Incubating app (Git Klient)

[samuel ammonius]

I'll try to help by being a sponsor. Reading through the incubator page, I
found this
,
so the app doesn't currently qualify. It will have to move to something
like gitlab.

What does developer accounts  mean?

On Mon, Aug 22, 2022 at 2:00 PM Harald Sitter  wrote:

> Heya,
>
> You'll need a sponsor https://community.kde.org/Incubator ... not me.
> I'm lazy :)
>
> On Sun, Aug 21, 2022 at 11:01 AM Hamed Masafi 
> wrote:
> >
> >
> > Hello
> > As a longtime kde fan(since 3.4), I would love to contribute to this
> group.
> > I am developing a graphical client application for git. I think it is a
> good option to enter the world of kde.
> >
> > Features of this program:
> >   - The icon displays the files in the Gate folder according to their
> status in Dolphin.
> >   - For easier access to the right-click menu of files and folders,
> options such as pull, push, delete, ignore, etc. have been added.
> >   - Graph display of commits.
> >   - General Git operations such as pull, push, fetch.
> >   - Show branches and distance of commits from the reference branch.
> >   - View files and file contents in each branch or commit.
> >   - Compare files, folders, branches and commits in a graphical
> environment.
> >   - Merge conflicting files in git.
> >   - Management of remotes, tags.
> >   - Auto-completion when writing a commit message.
> >   - Markdown editor (written but not yet added to the main program)
> >   - And some extra features.
> >
> > The source is available here:
> > https://github.com/HamedMasafi/GitKlient
> >
> > Currently, only I (Hamid Masafi) am working on the project.
> > This project is currently on GitHub, but it can be moved to any other
> repository if approved by you.
> >
> > Please take a look at this repository and let me know what you think. I
> look forward to hearing from you.
> >
> > Best regards
> > Hamed Masafi
>

Re: Incubating app (Git Klient)

[samuel ammonius]

Sorry. I was just trying to help.

What would the right action be?

Cheers,
Samuel Ammonius

On Mon, Aug 22, 2022 at 1:08 PM Albert Astals Cid  wrote:

> El dilluns, 22 d’agost de 2022, a les 15:55:24 (CEST), samuel ammonius va
> escriure:
> > Hi,
> >
> > I'm not a KDE developer, but I think I can help a bit. What you may want
> to
> > do is go on the KDE Utilities GitLab <https://invent.kde.org/utilities>
> and
> > open an issue asking them to create a new repository and put your app in
> > it.
>
> Please stop spreading misinformation.
>
> Cheers,
>   Albert
>
> > apps.kde.org just generates itself from KDE's repositories, so you
> > won't need to make any manual changes to it. To get the app on Discover,
> > you can just upload it to Flatpak since that's one of the sources
> Discover
> > gets its apps from.
> >
> > Good luck!
> > Samuel Ammonius
> >
> > On Sun, Aug 21, 2022 at 6:31 AM Hamed Masafi 
> wrote:
> > > Hello
> > > As a longtime kde fan(since 3.4), I would love to contribute to this
> > > group.
> > > I am developing a graphical client application for git. I think it is a
> > > good option to enter the world of kde.
> > >
> > > Features of this program:
> > >   - The icon displays the files in the Gate folder according to their
> > >
> > > status in Dolphin.
> > >
> > >   - For easier access to the right-click menu of files and folders,
> > >
> > > options such as pull, push, delete, ignore, etc. have been added.
> > >
> > >   - Graph display of commits.
> > >   - General Git operations such as pull, push, fetch.
> > >   - Show branches and distance of commits from the reference branch.
> > >   - View files and file contents in each branch or commit.
> > >   - Compare files, folders, branches and commits in a graphical
> > >
> > > environment.
> > >
> > >   - Merge conflicting files in git.
> > >   - Management of remotes, tags.
> > >   - Auto-completion when writing a commit message.
> > >   - Markdown editor (written but not yet added to the main program)
> > >   - And some extra features.
> > >
> > > The source is available here:
> > > https://github.com/HamedMasafi/GitKlient
> > >
> > > Currently, only I (Hamid Masafi) am working on the project.
> > > This project is currently on GitHub, but it can be moved to any other
> > > repository if approved by you.
> > >
> > > Please take a look at this repository and let me know what you think. I
> > > look forward to hearing from you.
> > >
> > > Best regards
> > > Hamed Masafi
>
>
>
>
>

Re: Incubating app (Git Klient)

[samuel ammonius]

Hi,

I'm not a KDE developer, but I think I can help a bit. What you may want to
do is go on the KDE Utilities GitLab <https://invent.kde.org/utilities> and
open an issue asking them to create a new repository and put your app in
it. apps.kde.org just generates itself from KDE's repositories, so you
won't need to make any manual changes to it. To get the app on Discover,
you can just upload it to Flatpak since that's one of the sources Discover
gets its apps from.

Good luck!
Samuel Ammonius

On Sun, Aug 21, 2022 at 6:31 AM Hamed Masafi  wrote:

>
> Hello
> As a longtime kde fan(since 3.4), I would love to contribute to this group.
> I am developing a graphical client application for git. I think it is a
> good option to enter the world of kde.
>
> Features of this program:
>   - The icon displays the files in the Gate folder according to their
> status in Dolphin.
>   - For easier access to the right-click menu of files and folders,
> options such as pull, push, delete, ignore, etc. have been added.
>   - Graph display of commits.
>   - General Git operations such as pull, push, fetch.
>   - Show branches and distance of commits from the reference branch.
>   - View files and file contents in each branch or commit.
>   - Compare files, folders, branches and commits in a graphical
> environment.
>   - Merge conflicting files in git.
>   - Management of remotes, tags.
>   - Auto-completion when writing a commit message.
>   - Markdown editor (written but not yet added to the main program)
>   - And some extra features.
>
> The source is available here:
> https://github.com/HamedMasafi/GitKlient
>
> Currently, only I (Hamid Masafi) am working on the project.
> This project is currently on GitHub, but it can be moved to any other
> repository if approved by you.
>
> Please take a look at this repository and let me know what you think. I
> look forward to hearing from you.
>
> Best regards
> Hamed Masafi
>

Re: Approval request for feature idea

[samuel ammonius]

Hello Sven.

Thank you for the clarification. I tried to make a style plugin since my
last message, and I see what you mean about stylesheets not being styles.
I've been trying very hard to find a way to convert between the two but it
hasn't worked out.

I'm going to try to make my own implementation of the CSS parser idea that
you referenced in your other email, and I'll report back to this thread
once I have a prototype. I'll try to build on top of the QSS syntax, which
I originally thought was the reason everyone seemed against stylesheets but
now I know that's not the case. Again, thanks for all your help!

On Wed, Jun 1, 2022 at 4:44 PM Sven Brauch  wrote:

> Hi,
>
> On 6/1/22 20:41, samuel ammonius wrote:
> > However, I still don't see the point of avoiding QSS because it seems to
> > be able to do everything CSS can (besides transformations, which are the
> > only difference that I've been able to find so far).
>
> Sorry but then you're not looking very hard. Look at e.g. [1].
>
> Just from a quick scroll-through, I find a lot of stuff QSS has never
> heard about, such as animations, box-shadow, caret-color, clipping,
> filter, float, advanced font options, text transform, text shadow, media
> queries, blend mode, overflow, perspective, transitions, n-th-child
> selectors, in general half the selectors, all CSS functions,
> before/after content, etc etc etc.
>
> But that's not even the problem. The problem is that QSS is not a style
> by itself, it is applied *on top of* a style such as Fusion, and does
> *not* give you full control over that style.
>
> So what do you even want to achieve?
>
> Do you want a fully customizable style? QSS isn't, it's not even *a*
> style to begin with.
>
> Do you want to apply some customization while preserving the base looks
> of whatever style the user has configured? Then QSS is a nice thing but
> unless you limit yourself to really basic stuff (mainly colors) some
> widgets will look weird or broken in some base styles, or in some
> applications. They might even break with colors alone, simply from the
> fact that a style sheet is set at all.
>
> I suggest we stop discussing this here at this point, I don't think it's
> very productive. I'd recommend you try to make a complete style changing
> appearance of all widgets (especially the more funky stuff: scrollbars,
> checkable combo boxes, progress bars, tool buttons with dropdowns,
> checkable menu items with icons, tree view items, ...) as you want them
> to look like with QSS, and open a few complicated applications (krita,
> dolphin, kdevelop, gwenview, the KDE file dialogs) with that style. I
> recommend a dark style, it tends to make problems more obvious. Try to
> make it perfect, like you'd actually want it to look like, not a
> prototype. I hope this experience helps you understand the concerns
> raised here. And if not -- well, maybe people here are wrong and this
> idea will fly after all ;)
>
> Greetings,
> Sven
>
> _
> [1] https://www.w3schools.com/cssref/default.asp
>

Re: Approval request for feature idea

[samuel ammonius]

This sounds amazing! However, I still don't see the point of avoiding QSS
because it seems to be able to do everything CSS can (besides
transformations, which are the only difference that I've been able to find
so far).

Re: Delivery Status Notification (Failure)

[samuel ammonius]

This sounds amazing! However, I still don't see the point of avoiding QSS
because it seems to be able to do everything CSS can (besides
transformations, which are the only difference that I've been able to find
so far).

On Wed, Jun 1, 2022 at 3:59 PM Mail Delivery Subsystem <
mailer-dae...@googlemail.com> wrote:

> [image: Error Icon]
> Address not found
> Your message wasn't delivered to *n...@kde.org* because the address
> couldn't be found, or is unable to receive mail.
> The response from the remote server was:
>
> 550 5.1.1 : Recipient address rejected: User unknown in
> virtual alias table
>
>
>
> -- Forwarded message --
> From: samuel ammonius 
> To: kde-devel@kde.org, n...@kde.org
> Cc:
> Bcc:
> Date: Wed, 1 Jun 2022 15:59:23 -0230
> Subject: Re: Approval request for feature idea
> This sounds amazing! However, I still don't see the point of avoiding QSS
> because it seems to be able to do everything CSS can (besides
> transformations, which are the only difference that I've been able to find
> so far).
>
> On Wed, Jun 1, 2022 at 1:25 AM Nate Graham  wrote:
>
>> Hello Samuel,
>>
>> There's an idea for the future of theming in Plasma 6 that would use CSS
>> to define a "universal theme" that would then be consumed by our QQC2,
>> Plasma, and GTK theming to keep them all in sync automatically. See
>> https://phabricator.kde.org/T13467. This is one of the options presented
>> there, but to my knowledge the only one with a prototype implementation,
>> made by Arjen Hiemstra (CCd). If you're interested in pursuing this, you
>> might want to get in touch with him about it.
>>
>> Nate
>>
>

Re: Approval request for feature idea

[samuel ammonius]

This sounds amazing! However, I still don't see the point of avoiding QSS
because it seems to be able to do everything CSS can (besides
transformations, which are the only difference that I've been able to find
so far).

On Wed, Jun 1, 2022 at 1:25 AM Nate Graham  wrote:

> Hello Samuel,
>
> There's an idea for the future of theming in Plasma 6 that would use CSS
> to define a "universal theme" that would then be consumed by our QQC2,
> Plasma, and GTK theming to keep them all in sync automatically. See
> https://phabricator.kde.org/T13467. This is one of the options presented
> there, but to my knowledge the only one with a prototype implementation,
> made by Arjen Hiemstra (CCd). If you're interested in pursuing this, you
> might want to get in touch with him about it.
>
> Nate
>

Re: Fwd: Approval request for feature idea

[samuel ammonius]

I also found this:
https://github.com/Alexhuszagh/BreezeStyleSheets#gallery

On Mon, May 30, 2022 at 4:32 PM Sven Brauch  wrote:

> Hi,
>
> On 5/30/22 20:37, samuel ammonius wrote:
> > I've worked with regular CSS and I'm sure that stylesheets offer just as
> > many customization options as things like QtCurve or QStylePlugins. The
> > reason that it may not seem this way is because Qt didn't document
> > regular CSS syntax in the documentation for stylesheets.
>
> No, the reason is that Qt's CSS has absolutely nothing to do with the
> regular CSS known from browsers. It's a proxy style which tweaks how a
> base style (e.g. Fusion or Breeze) draws elements on the screen, by e.g.
> modifying the palette and then forwarding the draw call to the base
> style. It implements maybe 1% of the CSS stuff a modern browser can do,
> and that's a favourable estimate. And not even all of that will work as
> expected in all cases. For details, see [1].
>
> That this proxy style's behaviour can be configured using a CSS-like
> syntax is coincidental, or, well, intentionally made that way for ease
> of use. But: this is not the CSS you know or expect.
>
> > I can't verify that stylesheets can do everything that a style plugin
> > can do
>
> They can't. Regular CSS 3 in Firefox is probably pretty close,
> practically speaking, but Qt's CSS, not so much.
>
> > but I know for sure that Breeze can be made using a qstylesheet
>
> Where did you get this information? This is certainly not the case. Just
> try to make e.g. the animated fades in Breeze using Qt's CSS and Fusion
> as the base style and you will immediately discover that it's not possible.
>
> Greetings,
> Sven
>
> _
> [1]
>
> https://code.woboq.org/qt5/qtbase/src/widgets/styles/qstylesheetstyle.cpp.html
>

Re: Fwd: Approval request for feature idea

[samuel ammonius]

https://doc.qt.io/qt-5/stylesheet-reference.html#:~:text=widget%2Danimation%2Dduration*

Wouldn't this allow animated fades?

On Mon, May 30, 2022 at 4:32 PM Sven Brauch  wrote:

> Hi,
>
> On 5/30/22 20:37, samuel ammonius wrote:
> > I've worked with regular CSS and I'm sure that stylesheets offer just as
> > many customization options as things like QtCurve or QStylePlugins. The
> > reason that it may not seem this way is because Qt didn't document
> > regular CSS syntax in the documentation for stylesheets.
>
> No, the reason is that Qt's CSS has absolutely nothing to do with the
> regular CSS known from browsers. It's a proxy style which tweaks how a
> base style (e.g. Fusion or Breeze) draws elements on the screen, by e.g.
> modifying the palette and then forwarding the draw call to the base
> style. It implements maybe 1% of the CSS stuff a modern browser can do,
> and that's a favourable estimate. And not even all of that will work as
> expected in all cases. For details, see [1].
>
> That this proxy style's behaviour can be configured using a CSS-like
> syntax is coincidental, or, well, intentionally made that way for ease
> of use. But: this is not the CSS you know or expect.
>
> > I can't verify that stylesheets can do everything that a style plugin
> > can do
>
> They can't. Regular CSS 3 in Firefox is probably pretty close,
> practically speaking, but Qt's CSS, not so much.
>
> > but I know for sure that Breeze can be made using a qstylesheet
>
> Where did you get this information? This is certainly not the case. Just
> try to make e.g. the animated fades in Breeze using Qt's CSS and Fusion
> as the base style and you will immediately discover that it's not possible.
>
> Greetings,
> Sven
>
> _
> [1]
>
> https://code.woboq.org/qt5/qtbase/src/widgets/styles/qstylesheetstyle.cpp.html
>

Re: Fwd: Approval request for feature idea

[samuel ammonius]

I've worked with regular CSS and I'm sure that stylesheets offer just as
many customization options as things like QtCurve or QStylePlugins. The
reason that it may not seem this way is because Qt didn't document
regular CSS syntax in the documentation for stylesheets.

I can't verify that stylesheets can do everything that a style plugin can
do, but I know for sure that Breeze can be made using a qstylesheet so
there shouldn't be any reason to say that stylesheets don't have enough
features to be added to KDE.

On Mon, May 30, 2022 at 3:51 PM Sven Brauch  wrote:

> Hi,
>
> On 5/30/22 19:52, samuel ammonius wrote:
> > Adding this feature won't make the C++ styles disappear. It will only
> > make it possible for users who don't know how to make a style plugin in
> > C++ to make their own styles
>
> the problem is that the Qt stylesheets are pretty bad at that. The
> customization options they provide are limited, work in unexpected ways,
> and sometimes look flat-out buggy, especially if applications have their
> own widgets or drawing code or if the stylesheet is applied on top of an
> unusual base style.
>
> They are fine for coloring a combo box or line edit in red if the input
> is invalid, but they are not a useful user-configurable theme engine.
>
> I do see the value in the feature you envision, but IMO it needs to
> happen in the form of something like the QtCurve style, which does its
> painting in a way that is directly intended to be customized.
> Customization needs to be offered by the style; it cannot be kludged on
> top of the style with the QCssStyle proxy style, at least not in its
> current form (but probably not at all). I suggest looking into something
> like this if you'd like to provide user-customizable styles.
>
> Greetings,
> Sven
>

Fwd: Approval request for feature idea

[samuel ammonius]

Adding this feature won't make the C++ styles disappear. It will only make
it possible for users who don't know how to make a style plugin in C++ to
make their own styles, while other users get to choose between using C++
styles for their performance or using stylesheet styles that may look
better to that user. Besides the performance cost, I didn't understand most
of the items on that chart, but I think the choice to use this feature
should be available for users regardless of the weaknesses QStylesheets may
have, because the existence of the feature won't affect any other choices.

On another note: the performance cost of QStylesheets can be dodged by
making the Style plugin only parse the stylesheet once, and then return the
resulting style to all applications without needing to parse it again.

Approval request for feature idea

[samuel ammonius]

I wanted to submit a feature for kde that would allow users to set the
application style to a qstylesheet file (style.qss for example). This
feature would greatly increase the amount of themes available for KDE, make
it possible for users to tweak themes themselves, and make it easier to
include custom icons/images with themes if necessary by using the url()
function in the stylesheet. It would also make it easier for experienced
developers who can make KDE themes in C++ to make multiple, more complex
themes in less time. The feature would also be very easy to make and would
probably take less than 1 Megabyte of total storage.

I originally wanted to submit this as a project in Google summer of code,
but I missed the deadline for applying. Who should I contact to get
approval for this before submitting a pull request?