I'll stay with 0.5.7.1

[nargh]

i'll say it again...the search and browser *DO NOT* increase memory or cpu usage at all if you have them disabled. heck, they dont even show up if you have them disabled, so you can pick and choose.

That's not the point.

There are two points:

• they break the idea of plugins - heck, torrent search was a plugin
• they are turned on by default, contrary to plugins

Now the user has to manually activate really essential stuff like the file tab plugin... but get's a browser enabled by default he's not likely to use - and has to disable in a completly different place.

[markybob]

i'll say it again...the search and browser *DO NOT* increase memory or cpu usage at all if you have them disabled. heck, they dont even show up if you have them disabled, so you can pick and choose.

That's not the point.

There are two points:

• they break the idea of plugins - heck, torrent search was a plugin
• they are turned on by default, contrary to plugins

Now the user has to manually activate really essential stuff like the file tab plugin... but get's a browser enabled by default he's not likely to use - and has to disable in a completly different place.

that's not even close to true. the file tab is enabled by default. so's the peer tab.

[mezz]

After a while statistics just stop updating.

And after some times like hour or two whole UI freezes becomes completely unresponsive and gets grayed out by OS. (Ubuntu)

I hope that if someone else has encountered these same problems they would report it. Because I can't provide enough detailed information right now. I hope that after checking out how system works after downgrade I could tell exactly that it's the changes that have been made from 0.5.7.1 -> 0.5.8 that cause these problems.

I have a similar report from a FreeBSD user other days ago. I have suggested him to disable advanced progress bar in the Preferences -> Others. If it doesn't help, then try to come in here and ask for help. I haven't heard anything from him yet, so maybe my suggest helps or he went with different way.

[sluthead]

I agree with the original poster that those features should be plugins instead of additions to the core code and selectable in the plugin manager, not the "other" tab. The reason being is that Deluge (in my opinion) should concentrate solely on the focus of the basic application rather than extra features. It should also mean that by using the plugin system that it is much safer in the long term to the purity of the core code. The very reason I switched and longed for a client like Deluge was because it did exactly what I needed without the billions of menu options like Azureus provides. That and the fact it's not java based. Particulary with Gnome, it's clear that the focus has returned to using a plugin system for every feature not covered by the application and with apps like Totem, the things that were part of its core are now moved to plugins.

Of course, it's not a condition that stops me upgrading to the new release, because it really rocks, but it does break the consistency of having a core utility and then plugging in all the extras that one might need.

The detailed progress bar, internal browser and search bar should be in the plugin manager because if the current trend were to continue with option extras the "other" tab would expand rapidly

[Ux64]

I have a similar report from a FreeBSD user other days ago. I have suggested him to disable advanced progress bar in the Preferences -> Others. If it doesn't help, then try to come in here and ask for help. I haven't heard anything from him yet, so maybe my suggest helps or he went with different way.

Thanks! I disabled advanced progress bar. (Even it has been working great earlier)

I also got some errors when torrent should be finished. Maybe related to move feature which I'm using?

Those are reported here: http://forum.deluge-torrent.org/viewtop ... t=10#p4983

[atria]

Well deluge is GPL. If you dislike the way it is currently heading towards, just fork it and remove the offending code.

[markybob]

By the way, it's why most of us want browser and search to be part of plugins. That way, I can split the package of Deluge. Like for example, create a new package called deluge-plugins-browser and the orignal Deluge package dependencies would be stay small unless users want to install deluge-plugins-browser.

i buy that, so i'll go ahead and make them plugins for the next release.

[sluthead]

Well deluge is GPL. If you dislike the way it is currently heading towards, just fork it and remove the offending code.

Or we can just discuss things as a community and throw ideas into the pot about it's future direction and try to do the best for the software instead of having a load of other "new" ones.

[johnnyg]

you could always give users the option to enable/disable the search bar & anonymous browser in the configuration wizard.

[Ux64]

you could always give users the option to enable/disable the search bar & anonymous browser in the configuration wizard.

That's already possible. (0.5.8)

I think you kind of missed the point. It's different thing to have small install and download package than have program with small memory footprint. And after all when I start deluge it seems to initialize all plugins even if those aren't enabled. I didn't do any in depth analysis about that. But markybob says that it won't use any more memory. That's just great.

But it would be more reassuring if it wouldn't even initialize / load modules that aren't loaded. Then it would be clear that those aren't being used. (I know, once again totally technical babble about some minor issue)

After all I don't care personally about download size or RAM usage or even CPU usage, because I got plenty of everything. Often the most expensive resource is programming resources. That's why I didn't like browser etc. Because it takes resources away from more important things (my point of view). But we all are (hopefully) allowed to have own opinions. And actually most of us (like I) don't have any authority about this, so feel free to ignore my boring long posts.

Or we can just discuss things as a community and throw ideas into the pot about it's future direction and try to do the best for the software instead of having a load of other "new" ones.

I agree about this. But when I do it, I usually seem to upset developers. Maybe my style is completely wrong. I have been doing this for 20 years now, working in software development companies.

But when we're talking about programs. It seems that I often take too technical view. And forget that program is developers baby. Any criticism is a bad bad attack against his or hers beloved. And it's quite rare that someone instantly admits that something is wrong. Change might be long process and come out after a years.

AFAIK: Anyway it's important to allow throwing in ideas. And not to take any criticism personally. It's just discussion how things might could have been done. Open discussion about problematic issues is what I have been missing in many projects. Usually some easy kludge solution is taken, without even thinking what kind of problems it might cause in future. And I have seen this way too many times.

I wonder why you did read old software project managers feelings this far.