Like in topic, i dont know how to change web interface sorting (id's), and i dont know which metod of sorting is in use. Can smbd help ?

Sorting of what ?

George wrote:Sorting of what ?

Sorting torrent by file/status/size/etc. Is this possible using some KTorrent core function or we have to implement this using PHP?

BTW. everything I really can do about developing KTorrent is improvming WebGUI.

So if there isn't ready method for sorting torrents and that has to be done using PHP, just let me know. I'll do this with pleasure and other developers will able to spend their time doing something I'll never able to


P.S.
Currently php_interface.cpp uses something that:

Code: Select all

                QPtrList<TorrentInterface>::iterator i= core->getQueueManager()->begin();
                for(int k=0; i != core->getQueueManager()->end(); i++, k++)

In the normal GUI we rely on Qt to do the sorting, so there is no internal stuff which can do this.

Can't we do this with javascript ? So we can be all web 2.0 ish, and we don't have to actually go back to the server to update the page.

George wrote:Can't we do this with javascript ? So we can be all web 2.0 ish, and we don't have to actually go back to the server to update the page.

Will be done, just give me a few days Well, "done" maybe with one little exception?

Default skin doesn't depend on JavaScript and I think it would be nice to keep this state. So my suggestion is to use JavaScript by default but also implement some server-side method. Of course everything would be transparent for end-user. May I do this in such a way? Or there are some objections?

Zajec wrote:

George wrote:Can't we do this with javascript ? So we can be all web 2.0 ish, and we don't have to actually go back to the server to update the page.

Will be done, just give me a few days Well, "done" maybe with one little exception?

Default skin doesn't depend on JavaScript and I think it would be nice to keep this state. So my suggestion is to use JavaScript by default but also implement some server-side method. Of course everything would be transparent for end-user. May I do this in such a way? Or there are some objections?

How about javascript for coldmilk and server side for the default (using an additional URL argument)