[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 155341] Session cannot be saved
From:       ken manheimer <ken.manheimer () gmail ! com>
Date:       2008-12-02 17:26:28
Message-ID: 20081202172628.CCE99105B7 () immanuel ! kde ! org
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=155341





--- Comment #32 from ken manheimer <ken manheimer gmail com>  2008-12-02 18:26:26 ---
i believe that (1) it is incorrect to call this issue a wishlist item, because
that ignores some serious consequences of the problem, and (2) many of the
protests here way overshoot, damning the developers and the development process
counterproductively.  both of those are problems that hurt kde, and i'm hoping
can be reduced.

re (1), while the simple implementation issue is lack of gui hookup of the
sessions save feature, the apparent presence of the feature misleads those
(apparently, few) people who *do* use it, leading to a lot of frustration for
them.  there's no need for that.  if the issue were properly identified as a
bug, then it would be more likely that either the presence of the misleading
stuff or the absence of the apparently present save-session feature would be
rectified.  i have been reluctant to recommend removing the misleading stuff,
because it reveals that kde is actually missing gui-exposed session-save, which
hurts kde's reputation.  but that's the truth of the matter, at this point, and
not calling this a bug obscures that fact.  i know that less harm would be done
by identifying that fact clearly than by obscuring it.

re (2), i don't believe that any developer intends ill, or is even negligent,
in their concern for user features.  i think that accusations along those lines
are equally as or more misguided than calling this issue a wishlist item,
misinterpreting their efforts to great insult.  i hope i haven't contributed to
that, and am sorry if i have.  i understand that the switch to kde 4 was an
enormous effort, for the sake of enormous potential (and now actual!)
improvement, and thank all involved.

this is a classic collision of user frustration versus developer issue
assessment, where overshoot on the user's part can obscure the actual issue at
hand.

i *do* think the harm in terms of confusion and shaken confidence for those
that try to use the feature is being disregarded in calling this a wishlist
item.  i believe that calling it a bug would give it proper prioritization
attention - even if that leads to disabling the session-save gui exposure until
the missing "save" functionality is gui-exposed, that would be a big
improvement, avoiding the frustration and wasted time and presenting that
actual reality of the situation.

if the information about the state of the system is clear and accurate, then
the users and developers don't have to get paranoid about controlling one
another to get results - choices and actions can be based on info about the
system, rather than demands in one direction or the other.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]