Summary: | no glossary? no search function over all topics??? | ||
---|---|---|---|
Product: | [Applications] khelpcenter | Reporter: | Arwed Starke <Arwed_Starke> |
Component: | general | Assignee: | Documentation Editorial Team <kde-doc-english> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | havaji, jsch, kdevelop-bugs-null |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/khelpcenter/cafde04221d0f0d20b042f9afcf63669f23b7a1d | Version Fixed In: | |
Sentry Crash Report: |
Description
Arwed Starke
2003-04-30 15:20:53 UTC
In edition to full text search, A Index search will be evan more useful: KHelpCenter create an index In the content tree. Enabling a search within this tree will be also very useful. I think this is the right place to state my comments. My version of KHelpCenter is 3.2.2. First of all I totally agree, that a full-text search facility is mandatory in our days. Second, when I open Settings->Configure[...] I get a dialog "Build Search Index" with no explenations what so ever! I'm a computer professional, programmer, researcher, I use almost exclusively linux for more than 8 years and I have no Idea how to use this Index thing. There is absolutely no information in the Help (at least I couldn't find it without a full-text search facility) nor the Web. The only references google (this is a full-text search facility) came up with is that somewhere in version 2.2 full-text search was disabled. So what, and I don't want to sweare, is this dialog for? As for help in generel with KDE-Apps: forget it, there is no useful help with KDE. You may find some help in devoted user-groups (e.g. the gentoo-linux people have an excelent forum useful even for non gentoo distributions). Kdevassistant seems to be a powerful KDE help container. Maybe if we extend it to allow classical KDE docbook management it will be the right choice against the khelpcenter which is no more really functional since some time... What do you think? *** Bug 65239 has been marked as a duplicate of this bug. *** *** Bug 95096 has been marked as a duplicate of this bug. *** I don't mind if someone write docbook plugin for kdevassistant's documentation part. But kdevassistant was created mostly for developer, not user documentation. Yes, and that's why it's so powerful. So, why is it wrong to use its power (or a "subset of it) for classical documentation? Why not using bzgrep for search? Bzgrep could search and display list names of files in which certain term appears. Integrated in khelp. Or index created before. Listbox of file documents grouped by content/topic could be used as glossary. Or display titles of help pages. Using treeview as index is not very usable for me. Also search does not work neither in glossary nor in content. I do not think users would mind if you would copy usability of MS Help.(form). Or something like google search, only for help? Git commit cafde04221d0f0d20b042f9afcf63669f23b7a1d by Pino Toscano. Committed on 12/03/2016 at 23:02. Pushed by pino into branch 'master'. Re-enable the full-index search Now that - Xapian is in place for indexing and searching - ht://dig is removed - indexes are updated automatically each startup we can enable the full-index search again. Related: bug 93664, bug 103266, bug 112958, bug 115935, bug 161514, bug 173767, bug 207519, bug 222494, bug 237329, bug 266290, bug 269260, bug 269619 M +1 -3 navigator.cpp http://commits.kde.org/khelpcenter/cafde04221d0f0d20b042f9afcf63669f23b7a1d |