Improvements for algorithm / component overview

[tmadlener]

Reviewing this now, looks good. I think some columns in the tables do not format very well, applying or removing zoom does not change them for example; in my screen there was plenty of space but lines are broken sometimes for short amounts of text. There is also the issue for input and output collections, the types in functional algorithm are very complicated. I think there we should put simply the collection, which is the interesting part.

Originally posted by @jmcarcell in #132 (comment)

[tmadlener]

Yeah, in general Properties that are in any way DataHandles are far from ideal currently. I didn't look into it further so far. In principle we could filter them here

key4hep-doc/scripts/collect_gaudi_alg_info.py

Lines 75 to 90 in e9356d6

	def _filter_prop_type(prop_name, properties):
	"""Filter the property type to try and make it a bit more readable"""
	if prop_name not in properties:
	return ""
	prop_type = properties[prop_name][0]
	# Remove the std::allocator part from vectors
	prev = None
	while prop_type != prev:
	prev = prop_type
	for pattern, repl in _STL_REPLACEMENTS:
	prop_type = re.sub(pattern, repl, prop_type)
	# Remove the std namespace because it takes up too much unnecessary space otherwise
	prop_type = re.sub(r"std::", "", prop_type)
	return prop_type

The problem is that they all report the same type regardless of which one it actually is, so there is no easy way of associating it with the the actual collection type, and getting more information in would need changes in Gaudis genConf, I think.

Column widths is a fair point, I have not tested on a wide enough screen it seems.