X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Tue, 14 Feb 2017 17:08:19 +0100 (CET) From: Roland Lutz To: geda-user AT delorie DOT com Subject: [geda-user] Internal vs. user-visible changes Message-ID: User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Reply-To: geda-user AT delorie DOT com In the past, I have followed a very conservative approach about user-visible changes. I improved the inner workings of gEDA/gaf to make future improvements easier while putting a lot of effort into not changing anything exposed to the user. When I thought a user-visible change would make sense, I would post it to this list to see if there was a consensus in favor of it. The problem is that this didn't work. For any proposal, even for features which have been requested by many users, there were some people opposing them because they would have preferred me to implement it another way; at the same time, people kept flaming me about internal changes which didn't affect them at all. On Sun, 12 Feb 2017, gedau AT igor2 DOT repo DOT hu wrote: > Let's assume users weight refactorings and cleanups and elegance-of-code > a bit lower than actual features they need in daily use. I think my approach has been wrong. Instead of offering a solid infrastructure and waiting for the actual solutions to follow, I should have put equal emphasis on *using* the new possibilities. There is no point in cleaning up the code unless you intend to do something with it. gEDA/gaf now has back annotation, parametric subschematics, and custom power symbols without a ":1" suffix. Expect more to follow.