On 16 Dec 2005 19:17:38 -0200, Jorge Godoy <[EMAIL PROTECTED]> wrote: > If it was like that to me, I wouldn't disagree with you. I don't see any > reason for not having both alternatives.
Pardon me for jumping in, but I think that retaining two widgets for the sample feature is a very bad idea. 1. It makes maintenance more difficult--if we add features to or fix bugs in one, we'll certainly have to do the same thing again. 2. It causes confusion among users--"which of the two should I use" will be a very frequently asked question. 3. It shows indecision on the part of the library designer--not good for instilling confidence in potential users. TurboGears doesn't come with multiple database mapping layers, templating engines, or application servers, even though there are others out there as good as SQLObject, Kid, and CherryPy. There's a reason that the Zen of Python says "There should be one--and preferably only one--obvious way to do it." -- Tim Lesher <[EMAIL PROTECTED]>
