On 8/1/07, John Beckett <[EMAIL PROTECTED]> wrote: > I didn't notice anyone address my big problem: > > By having C and C++ as separate categories, you force a programmer > to search BOTH categories. > > If I were looking for tips on C, I just wouldn't trust that the > editors had correctly used category C++, so I'd have to search C and > C++ categories.
OK, but if you don't trust categories, you will anyway open all the C/C++ related tips. If they are in one or two categories it doesn't change much for you, except that you are more likely to find relevant tips if there are two categories. Note also that the "normal" evolution of our wiki is to converge to the point where all the tips are in the relevant categories. > > it's our responsibility to use the correct categories for each tip. > > The correct way to handle this is to have categories: > VimTip > LanguageSpecific > Cfamily > C > C++ > C# > > Does anyone want that complexity? The problem of our category tree is that it's a tree, while we need a graph :-) If I want a tip to be in the C, C++ and C# categories, I can manually add it to all of these. If I don't know C#, I let it alone, and someone else (maybe you, since you open the tips in all the categories ;-)) with more knowledge will add the relevant category if needed. We don't need a "grouping category" for tips belonging to the sub-categories. In fact, the CFamily category is an arbitrary grouping. For example, why not including Java as well? At least 3 (out of 16 currently) tips in the Java category also belong to the C/C++ categories, and some others (such as http://vim.wikia.com/wiki/Fold_braces_and_javadoc) could be easily adapted for C/C++/C# as well. My point is that many tips should be tagged C/C++/C#/Java, others should be tagged C++/C#/Java, others should be tagged C/C++, others C/C++/C#, etc... Using "arbitrary" grouping categories, like one category for C/C++ or like the CFamily category, will never be flexible enough, that's why I prefer many individual language categories. Cheers, -- Olivier _______________________________________________ Vim-l mailing list [email protected] http://lists.wikia.com/mailman/listinfo/vim-l
