[
https://issues.apache.org/jira/browse/CAMEL-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407924#comment-13407924
]
Claus Ibsen commented on CAMEL-4931:
------------------------------------
Reuben, I have applied your 1st patch. Maybe you want to work on the other
Camel Karaf commands, and maybe refactor the compute column length logic into a
util class to be reused among the commands.
Then when Karaf has some util JAR we can use, then we can switch to that in the
future.
> Improve column display in camel:route-list and similar Karaf commands
> ---------------------------------------------------------------------
>
> Key: CAMEL-4931
> URL: https://issues.apache.org/jira/browse/CAMEL-4931
> Project: Camel
> Issue Type: Improvement
> Components: karaf
> Affects Versions: 2.9.0
> Environment: Karaf
> Karaf version 2.2.5
> Karaf home C:\Users\rgarrett\bin\apache-karaf
> Karaf base C:\Users\rgarrett\bin\apache-karaf
> OSGi Framework org.apache.felix.framework - 3.0.9
> JVM
> Java Virtual Machine Java HotSpot(TM) 64-Bit Server VM version
> 20.4-b02
> Version 1.6.0_29
> Vendor Sun Microsystems Inc.
> Uptime 3 days 16 hours
> Total compile time 1 minute
> Threads
> Live threads 81
> Daemon threads 62
> Peak 83
> Total started 435
> Memory
> Current heap size 54,287 kbytes
> Maximum heap size 466,048 kbytes
> Committed heap size 251,904 kbytes
> Pending objects 0
> Garbage collector Name = 'PS Scavenge', Collections = 198, Time =
> 1 minute
> Garbage collector Name = 'PS MarkSweep', Collections = 12, Time =
> 43.999 seconds
> Classes-
> Current classes loaded 6,204
> Total classes loaded 6,451
> Total classes unloaded 247
> Operating system
> Name Windows 7 version 6.1
> Architecture amd64
> Processors 4
> Reporter: Reuben Garrett
> Priority: Minor
> Fix For: 2.11
>
> Attachments: CAMEL-4391-1.patch, camel-route-list.png
>
>
> Camel's shell extensions for Karaf print poorly-formatted results in some
> cases (particularly camel:route-list), impeding legibility and ease of use.
> It appears that the fields are right-padded with spaces to 18 columns
> regardless of maximum actual column length.
> I understand there's ultimately a limit to the width of the console.
> However, if the width of the console can be determined, it should be filled
> appropriately; middle truncation might be an option for excessively long
> fields (e.g.: "thisIsAVeryLongField...ThatHadToBePartiallyTruncated").
> If the console width cannot be determined, it may still be acceptable to scan
> for the longest field and set the entire column to its width in the interest
> of uniform appearance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
