Version: unspecified (using KDE 4.6.4) OS: Linux For now, user runs the program and... who is the author? What is the web page? Where do I report the bugs -- ZERO information. I have to google for kcolorchooser just to find out, that I have to fill a report for kcoloredit. Such info should be kept within the program. Reproducible: Always
You report is a bit confusing for me, let me try to sort out the issues: * kcoloredit Help menü with all default entries (About/Bug etc), there is no bug * kcolorchooser no product/component in b.k.o looks like a duplicate of No 2 in https://bugs.kde.org/show_bug.cgi?id=87490 please file a bug for product bugs.kde.org * kcolorchooser no Author Info / Bugreport items looks like a duplicate of No 1+3 in https://bugs.kde.org/show_bug.cgi?id=87490 possible solution: Help button with all default help menu items like KFind and KSnaphot
I would be happy to mark this report as duplicate of the other (point 2) but there is a problem -- the poster mixed several issues in one report (BKO rules violation). It is better to either split the other report to several ones, or for point (1) in the other report make a duplicate to this report.
I agree that dealing with bugs like https://bugs.kde.org/show_bug.cgi?id=87490 (several mixed issues) is a mess and will to close it as dup of this and others or file a separate br for remaining issues, but I've to check all issues in 87490 first. But please keep the br also clean, file a report for kcolorchooser (no product/component in b.k.o), add the info here, so that this report is only about one issue (the last issue in my list). Thanks.
> file a report for kcolorchooser (no product/component in b.k.o), I don't quite follow you. I cannot file a report for kcolorchooser in a normal way, because: a) as you wrote -- there is no such product in BKO b) the homepage of KColorchooser links KCC to Kcoloredit in BKO > add the info here, What kind of info? > so that this report is only > about one issue (the last issue in my list). I see here only 1 issue. Missing Help->About entry in menu (there is no menu ATM I know).
(In reply to comment #4) > > file a report for kcolorchooser (no product/component in b.k.o), > > I don't quite follow you. I cannot file a report for kcolorchooser in a normal > way, because: > a) as you wrote -- there is no such product in BKO Hm maybe I was not clear enough, I meant file a bug for product bugs.kde.org about missing component KColorchooser. There is already a br about this issue https://bugs.kde.org/show_bug.cgi?id=250467 with RESOLVED/INVALID. Do you want to reopen that? > b) the homepage of KColorchooser links KCC to Kcoloredit in BKO > File a report for product www (?) and request to correct that. > > add the info here, > > What kind of info? > about the br for product bugs.kde.org about the missing component. > > so that this report is only > > about one issue (the last issue in my list). > > I see here only 1 issue. Missing Help->About entry in menu (there is no menu > ATM I know). And there will be never a menu I guess. I proposed a Help button with all missing actions like KFind (4.7) and KSnaphot (since 4.5)
Reopening that report would be a good idea (I already commented the other report). Help button would be OK. In general it is hard to post any report if the author(s) ignore(s) such basic thing as incorrect bug reporting track. Either somebody cares, or not. There is no middle ground.
Git commit d7104d116bafd6521ec2c3c89b8bc276abb4a87f by Christoph Feck. Committed on 26/07/2011 at 19:25. Pushed by cfeck into branch 'master'. Add Help button Additionally, set bugzilla product to "kdelibs/kdeui", because all code is actually in the KColorDialog class. FIXED-IN: 4.8.0 BUG: 275977 M +7 -0 kcolorchooser.cpp http://commits.kde.org/kcolorchooser/d7104d116bafd6521ec2c3c89b8bc276abb4a87f
Burkhard, the remaining issue is that invoking the Help document actually opens "KColorEdit" help, because .desktop file has "X-DocPath=kcoloredit/index.html". Should I file a separate doc bug for that?
(In reply to comment #8) > Burkhard, the remaining issue is that invoking the Help document actually > opens "KColorEdit" help, because .desktop file has > "X-DocPath=kcoloredit/index.html". Not here, it opens the KColorchooser help locally (a draft, not finished, cause it waited since two years for a help button ;-) > Should I file a separate doc bug for that? No I'll change the X-DocPath and add the help docbook next week.
Git commit 335c37ecece2018ebe976cfa44b8a74c90facbd0 by Burkhard Lück. Committed on 20/04/2012 at 14:14. Pushed by lueck into branch 'master'. set X-DocPath to section about color choosing in new fundamentals documentation M +1 -1 kcolorchooser.desktop http://commits.kde.org/kcolorchooser/335c37ecece2018ebe976cfa44b8a74c90facbd0