Shareaza

Talking with old_death and using his recommandation we rearanged this dialog and I think this one is much better.

Please provide a screenshot for reference.

Screen shot

This dialog still looks very disorganized to me. I still prefer this one.....but of course that one is much more work to implement

Nice work, Sia!

@ Cyko, your design idea lacks some of the features offered by this version of the dialog. You might want to create a new revision of it...? Because the general look'n feel of your dialog seems good to me, however, if it offers less functionality, it is unlikely to be chosen for implementation.

However, sias dialog currently lacks the possibilities to use intervals (except for 1 week intervals), so you can't do something every 13 days for example... Even if this is not very important for most users...

see my reply here

Is anyone going to commit this?

Several labes not fit even in english language:



I think we must remove custom scheduler code and use Windows Task Scheduler API 1.0 (or 2.0 on Vista and above).

Why you don't think so?

I believe the task scheduler API is supported by Windows PowerShell and third party automation programs. (Please correct if I am wrong.) That would make it possible to script or automate arbitrarily complex behaviours for Shareaza using any tool you happen to prefer. And the API itself is pretty powerful to begin with.

Not sure if it is a must, but it would be more powerful than any custom solution we can make. And Microsoft would take care of bug fixes...

I had the idea of using Windows facilities from the beginning. But preferred not to use it for the reasons I don't remember.

I think we should make current one usable for the next release and we will have time to implement a better one. What I do know is that I am not the one who will implement it as I like to be involved in network core and system parts. But i will continue supporting current Scheduler.

BTW, how should I know how long should my text boxes be?

Please wait, I seriously researching possibility of Windows Task Scheduler implementation in Shareaza.

I think you should really stop adding features before fixing old bugs. Not only fixing detected bugs but devs should also throughly test debug builds to find not detected/reported bugs. Developers are also best testers as they know potentially buggy spots and dangerous scenarios.

There are still many minor bugs that some of them are fatal hanging around.

Fixing Scheduler is a bug fixing.

He is not really talking about adding new features as much as moving some of the current features to use a service Microsoft supports and debugs.

Almost done...

Nice!

Please test new scheduler.