I didn't mean to dismiss your work, I just like to explore the reasoning
behind any change and make sure what we are doing is the true to goals
of the project. By asking this question, I wanted to point out that not
all users would find this useful and that we should consider making it
optional. Just because I don't find something useful, doesn't mean that
others won't.. You retorted with some valid points as to why it would be
useful and that was all I wanted; to show a need.
> Now here comes the twist. After that incident.
> 6) Markos, Ander: "We should set it as a preference, since it wastes
> CPU and the user might not want it." Honestly, I don't see how it
> significantly contributes to the CPU usage as the progressbar is
> updated once per second! In any case, the progressbar drawing
> mechanism is infinitesimal compared to the other things that are going
> on, even in the screen updating cycle called every second. And about
> forcing the progressbar to the users, please do a google search on
> popular torrent client interfaces. Look around a bit.
> Still, I set the progressbar to be enabled by preferences.
The one major goal of Deluge is stay as lightweight as possible and give
the user the freedom to choice which features they wish to use. I
understand that using this new bar may not significantly use more CPU
time, but we should still present the option for the user to turn it
off. This is why the majority of functionality is located in plugins,
so that users can decide what they want and don't want.
I personally would use the old-style bar, because I don't have a need to
few the specific pieces downloaded and I am sure there others like me.
I am also pretty sure there are more people who would want to use your
bar. Let's give them the option.
> Unfortunately, this was my first experience in collaborative open
> source programming in linux.
I think that you need to understand that there is a process involved
with adding new features or changing functionality in the project. You
started it off by submitting a patch with the changes for our review.
We looked it over and gave you our thoughts, discussed the changes and
offered opinions in how it can be modified. This process will keep
continuing until we come to a consensus on how the change should look
and fit into the program. Just because we don't accept the 1st, 2nd or
3rd revision does not mean we don't want to apply your patch, it just
means we feel there is more discussion warranted and that some more
tweaks may be necessary to 'fit' the piece into the whole.
I am sorry that you are discouraged with how this process works.. It can
be a bit difficult to adjust to at times (I have problems with it myself
sometimes). We all want things done our own way and it can be difficult
to please everyone's individual vision and (sometimes) more importantly,
that of the users.
All in all, it just takes a little bit of patience and communication. I
apologize if the communication has been confusing or if we've come off
as disrespectful of your efforts.
Cheers,
Andrew