Feature Request : Similar or identical file browsing than WINDOWS VERSION.
One of the missing things why people is still using windows version, or in linuix Eiskaltqt, is because the file browsing is very pooor compared to PC, the file browsing in PC, that is kind of standard in dc clientes is very useful to browse large filelists and choos what download.
I miss this in web version, i can imagine is something very complicated to do.
What do you specifically miss from the filelist browser in the Windows version?
I miss, the two columns view, where i can see all the directories in first column, files and dir ins econd column, and i can browse with the keyboard up down, intro opens the directory, left click and i can download etc. I miss it, and i'm not the only one that ends using desktop or eiskalt in linux. Also i suggested for retroshare, same concept and a third column for users, so un can choose them from the first col.umn, and the second and the third for browsing.
I miss, the two columns view, where i can see all the directories in first column, files and dir ins econd column
Can you show me how is windows for retroshare?
I miss, the two columns view, where i can see all the directories in first column, files and dir ins econd column
Can you show me how is windows for retroshare?
rs filelist browsing is similar as the airdcc web client, so is not very good, there is a tree mode, and also something that is not a bad idea that is "flat mode" where you can order by latest modified files.
But rs code is crap, so tree view appart of the tree browsing problems i don't like also in eiskalt web, it has lot of qt bugs that makes browsing impossible, and flatmode is also fucked so is not working properly, anyway you can install rs and see how it works.
But maybe even the tree mode view of rs is better than airdc web file browsing.
@felisucoibi can you take screenshot to illustrate what you want?
what i want is the same filebrowsing as airdc desktop client. simple.
It should be an option to enable tree-view panel. Some users like it others don't.
I'd prefer the tree as well, but that would require reworking the filelist API (and possibly the shared filelist implementation from the core too). Not counting the UI implementation. This is about the amount of work, but contributions are welcome.