Alvin said: > To Freddy's point, I think method chaining would be nice, especially > when dealing with large and complicated forms or tables. I won't argue > that it'd be worth the API bloat one way or the other because I don't > have to maintain the code. > > But still, from a user's standpoint, it would be handy.
I agree with Alvin and Bob that it would lead to API bloat and should probably not be added to the Click core. So I've created a very simple utility that generates a subclass and adds method-chaining setter methods. I need to clean it up and package it up nicely, which I'll try to do in the next few days. There are probably disadvantages of using something like that, so please don't think I am trying to convince anyone to use such a tool. I'm just throwing an idea out there for those who might find it useful. Bob said: > The column example does show where the pain points lie, [...] Well, I was just talking about a nice-to-have. I wouldn't go so far as to use the word "pain" when talking about Click. ;-) Cheers, Freddy
