> What the last couple of days have shown is that making undiscussed changes is
> just going to get circular due to differing user requirements and opinions.
Yes and we all did that, when initially my intent was just to fix a bug.
But instead we changed the user interface, things expanded when they didn't
before,
and conversely, changing the meaning of ` etc,
and some of the edbrowse users, who are not on this list
contacted me and were confused.
So now it works all as it did before, except the bug is fixed,
and the code is much cleaner inside.
Of course there's nothing wrong with cleaning up code,
but we do have to talk more and plan more
before changing the user interface.
I had the same problem with some of the plugin work,
which we all agreed was great, and even the users agreed was great, so no
trouble there,
they are really quite enthusiastic about it,
but we rather innocently said,
Hey let's change mime { to plugin { in .ebrc
Sure that makes sense, but some of my users out there had edbrowse fail on
startup
for reasons they didn't understand.
And even if they waited til the next release, it would have been the same
problem.
No backward compatibility.
So at their suggestion I allow either syntax now
mime { or plugin {
and edbrowse runs again with the previous .ebrc
I have to temper what I do, and what we do, with some feedback that I get
from others that is, unfortunately, not always on this list.
It is, I suppose, my job to relay some of this information to this list,
so we can all talk about it.
Sorry if I missed some of these steps.
Karl Dahlke
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
