review our use of khelpcenter (and its deps)
Open, LowPublic


we have khelpcenter on the ISO (technically I think kf5 will open a browser if khelpcenter is not installed).

it does however depend on kdoctools which depends on a whole bunch of large data packages such as sgml and docbook-x*.

we could drop khelpcenter, or we could look into why it depends on kdoctools and if that really needs to be installed by default (I am guessing it does because apps install docbooks instead of htmls IIRC)

so, basically devise an action or in-action plan of how to refine the disk cost of khelpcenter.
(mind you, the disk cost of storing html renders of all documentation + translation is higher than the xml/xsl/sgml stuff is)

oh and lastly: it also needs xapian for indexing. so overall, perhaps the best approach would be to drop khelpcenter from the ISO? probably needs talking over with the plasma team but I am guessing since khelpcenter is in apps and not plasma the plasma POV would be that it is not a core part of the experience

sitter created this task.Mar 14 2019, 12:44 PM
sitter triaged this task as Low priority.
sitter updated the task description. (Show Details)Mar 14 2019, 12:48 PM
ognarb added a subscriber: ognarb.Mar 14 2019, 6:21 PM

Just want to point out that System Settings has a lot of help buttons that link to khelpcenter. Maybe someone from Plasma team can implement a fallback to open the web version in case khelpcenter is not running.

Huh, that is actually a bug in all KCM-related tech I'd imagine. They all handle help independently of kxmlgui and thus do not transparently fall back to resolve help via the web when khelpcenter isn't avialable.

sitter updated the task description. (Show Details)Mar 19 2019, 2:36 PM
sitter updated the task description. (Show Details)Mar 19 2019, 2:44 PM
sitter moved this task from Ready To Do to Blocked on the Neon board.Mar 19 2019, 2:47 PM