Summary: | app-portage/ufed: Shortening/cleaning flag descriptions by eliminating "[Enables/Adds/Includes] Support [for] ..." | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Roman Žilka <roman.zilka> |
Component: | Third-Party Tools | Assignee: | Sven Eden <sven.eden> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | fuzzyray, kripton, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Roman Žilka
2013-01-23 13:08:53 UTC
A toggle-able feature, of course. Sometimes grammar becomes mangled after such shortening, but that's OK, I think. Although it would be easily doable in perl due to its strong regex engine, the texts are held in C program and are "just" delivered as is. I have to think about this. The easy way would be some kind of command line option to turn on the cleansing. The perl program that actually does the collection of the data that is to be displayed would then prepare the descriptions. But what if a descriptions is mangled to a point where the user would like to see the whole message, because it is not clear any more what it means? A "life" change of the descriptions would be by far better then. I am not convinced that some gaining of space would be worth the amount of work this *seems* to need. Next week I'll do some experiments and then report back. (In reply to comment #2) > But what if a descriptions is mangled to a point where the user would like > to see the whole message, because it is not clear any more what it means? A It certainly would be a togglable feature. Due to private matters it took me a (longer than expected) while to get back to this. To have this feature toggable there are only two ways to implement this. Possibility 1: Add the shortening to the interface itself. This would mean that streams of characters must be parsed over and over again. Hitting up/down key means parsing every single line displayed to change the text. Further the texts must be held twice. Once in their original form and once in the form to display. The latter would either be a shortened version or simply a copy. Possibility 2: Prepare an alternative text. While preparing the descriptions a reduced version could be build and sent to the interface as an alternate text. The interface then only needs to decide upon which of those to use. I strongly favor the second alternative, it seems to be of much more use. And the impact on the current code *looks* like to be a lot less. Currently I have a local branch to test possibility two. I'll report back when the tested solution is either worth merging into master or ends up being thrown away. The changes are made, the new key F10 toggles the decscription between the original form and the stripped version. Please note that only wordings at the beginning of the description lines are stripped. Similar words in the middle or at the end will be left alone. However, this reduces the needed length greatly. Please feel free to test the new feature in the live version. This feature has been added to the new version 0.91 in the tree. |