https://bugs.kde.org/show_bug.cgi?id=481069
--- Comment #31 from Flossy Cat <flossy-...@online.de> --- (In reply to Andreas Schneider from comment #30) > As initially said that this is something for power users, I'm the initial reporter of both this bug report and https://bugs.kde.org/show_bug.cgi?id=481068 and I'm a computer SW engineer with decades of work life, contributing to FLOSS since the 80ies. My suggestions are not idle talk. A real power user "does not need" this feature at all, as many use-cases can be implemented by UDEV. Or all by "dbus-monitor" and the likes piping into a named pipe, where some script filters and triggers actions. Both well within my scope. And both even having the advantage of being quite DE independent … The whole point in this feature is to make advanced automation accessible to as many users as possible. There the parallel provision of the details via environment variables improves their experience, IMHO. Then users have both options. The question is not, if you or I can cope, but how to make a solution accessible to a broad user base. > … > If you really need all of those variables to make a decision what to do in > the script. Scripts develop with use – the env vars makes this less hassle. Your approach is IMHO a deterring nightmare to document for end users … So few will use it and it will be dropped again soon … > Then you're advanced enough to quickly code up option parsing in > your bash script. It is a 30 line switch statement in bash. A completely unnecessary hurdle … Intimidating for new users. I'd prefer to encourage many users to extent their skills and DE automation, because that gives KDE a leading edge … > Providing the > expansion on the command line allow you to use them with already existing > executables. That is well understood by me – I suggested to ADD the env vars as parallel IPC mechanism. Doesn't cost much, avoids an additional GUI choice, eases end-users life … But don't bother, I'll do it myself later when your change has stabilized … -- You are receiving this mail because: You are watching all bug changes.
