Uli's Web Site
Heterogeneous outline lists
In his article Forest for the Heterogeneous Trees, Andrew Pontious writes about the malady that are heterogeneous outline views (aka heterogeneous tree views). He also mentions, as one example, my TADS Workbench.
While I fully agree with him that I really am cramming a tad too much into the same list, I'm not sure I agree about how much is "too much". From his comments, I understand he would like to see every of the pseudo-folders in Workbench in its own list.
I guess the problem is that Andrew didn't really define what he meant by "heterogeneous". If one takes a very strict definition, even folders and files shouldn't be in the same list, because a folder is not a file. On the other hand, if we take too loose a definition, we get something like Workbench has, where, because each of the items in the list is simply an entry in the TADS Project File, all of them belong in this list.
Obviously, these are both nonsense. But there's a lot of intermediate positions. In the case of Workbench, one could argue that the Include Folders are file system items, just like the source files and the library files, and thus should be in the main list.
So, how would one go about scientifically determining whether a particular list is too full? Well, I guess apart from checking for heterogenity in the kind of items, one should also check for heterogenity of their use. With this in mind, I would put the Source files and Libraries groups in the main window:
OTOH, while the constant definitions obviously shouldn't be in this list, we now have a rationale that makes us realize why the include paths shouldn't be in this list:
We'll see whether Andrew agrees. Since he will probably be releasing the next version of Workbench, he'll get another opportunity for fixing this before it reaches your hands. I'm looking forward to seeing some of his plans bear fruit. He has lots of ideas that would be really cool to have in Workbench.
Created: 2004-11-14 @709 Last change: 2004-11-14 @740 | Home | Admin | Edit|
© Copyright 2003-2022 by M. Uli Kusterer, all rights reserved.