On Thu, Jun 19, 2008 at 6:18 PM, Endre Bakka <[EMAIL PROTECTED]> wrote: > >> I would rather see the API fixes in Trac core than the original patch. >> Subcomponents really are a feature I would rather see in a plugin, >> because >> the vast majority of people don't need or want them. > > I find it very very hard to believe that the vast majority don't need > subcomponents. And if some don't want them, they won't see them anyway. If > you don't add a subcomponent in the admin window, they don't have to be > showed elsewhere neither. Non-intrusive = all good. It's there for those > who need it, and not in the way for those who don't. When you need it and > it's not there and you have to hunt down a plugin from track-hacks, > install it and worry about maintenance, it get's in the way.
Just to throw in my $0.02 USD on this (what I see as relatively minor) issue. Perhaps you're right that allowing some form of subcomponents can't *hurt*. But I will wave my hand as someone who doesn't need or want them. I have a hard enough time getting people to select the correct component for tickets as it is. No need for subcomponents. Adding a \ is generally good enough for adding a second level. A third level starts to get ridiculous. And I'm not to thrilled about existing implementations I've seen of this anyways. I'd much rather see the API extended to better support the implementation of such a thing. I'm usually happy to see more extension points, because then I can do what *I* need to do with them, and not what someone else thought was a good idea. Erik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
