Kendo FileManager Issues

[Marcello]

Hi,

I'm working with Kendo FileManager, it's nice but also pretty immature, I hope you can fix it soon.
Main problems are:

1)The copy/move option during drag and drop it's out of every standard UI, the darg/drop action moves items, eventually a copy/paste context menu allow to copy it. In your strange way a lot of duplicated files are created accidentally...

2) We have no way (or I don't find) to move a file/folder to the root. A standard strategy can be a "..." folder that refers to the parent.

3) We have no way (or I don't find) to stop client actions server side, communicating something, in ie: "I'm sorry, you can't rename this file." We can use command event but not for actions Read and Upload.

4) Upload button allow to uploads something, then if you click it a second time the File list contains informations about previuos sents and if you click "clear list" the windows is closed... terrible...

5) Commands can require long time but no busy indicators appears...

6) How to distinguish Copy from Move? The server receives the same "Create" request.

I really hope you can release a new version in a reasonable time
Thanks,
marc.

[Dimitar]

Hi Marc.,

Thank you for your feedback on Kendo UI for jQuery FileManager component. I will try to clarify the respective topics and provide more resources on them.

1) The drag and drop feature allows dragging and dropping files and folders from FileManager view (GridView or ListView) to the navigation TreeView and vice versa. In addition, files and folders may be dragged and dropped in GridView or ListView to another folder. And folders may be dragged and dropped in the navigation TreeView. On drop a dialog appears, which asks if the file should be copied or moved. The file is copied or moved depending on the action button clicked.

2) The current implementation does not support drag and drop to root. There is a Feature Request logged on the UI for ASP.NET MVC Feedback Portal. You may vote for it as it already has votes and as the MVC wrappers rely on Kendo UI for jQuery for the feature implementation.

3) Yes, the command event should be used. And for Upload requests the inbuilt Upload events may be handled.

4) On clicking the Upload dialog close button or the Done action button the dialog is closed and the list of uploaded files is not cleared. It is preserved and loaded the next time the Upload dialog becomes visible. The Clear list action button also closes the dialog, but it clears the list of uploaded files as well. The list is not present the next time the Upload dialog becomes visible. This behavior is by design. The text of the two action buttons may be customized by messages.dialogs.upload.clear and messages.dialogs.upload.done properties.

5) There is a loading indicator visible on FileManager Overview demo on my side. This is a screenshot with Network throttling to simulate Slow 3G speed.

6) The following forum thread describes how the execute event may be handled and move/copy may be derived from e.command event argument. It also mentions that Copy triggers only a Create request, while Move triggers Create and Delete requests.

I hope this is helpful.

Best regards,
Dimitar
Progress Telerik

[Marcello]

Dear Dimitar,

 

thanks for your long answer, but, at the end it is not helpful.

1) Yes, I understand, and in a nutshell, it's wrong

2) A two years old request, I can't wait.

3) Complex, not standard, not usefull

4) This behavior is by design. And it is stupid :-)

5) Yes, sometime it appears but not for all actions

6) Terrible! Why you are supposing that, server side we implement move as a create/delete?

At the end I wrote my own file manager, so the last question is why I spend every years a lot of money for Telerik controls?

marc.

[Dimitar]

Hi Marc.,

I’m sorry to hear that you had to write your own file manager component from scratch and I understand how this could be frustrating. To help clarify why our FileManager component acts in certain ways I will provide some additional information that I hope you find useful.

Move behavior and feature request

The Kendo UI for jQuery FileManager is a composite component, consisting of a TreeView and Breadcrumb for navigation and Grid and ListView for displaying files and folders, as well as other components. In order to update the composite UI and synchronize back-end operations, we have to use DataSource. And using DataSource is tied to using CRUD operations. That is why move behavior is implemented as a Create and a Delete request.

We prioritize feature requests based on several different factors, the main ones being business value and customer demand. This means that highly anticipated features (features that have gathered many votes) usually take precedence over less popular features that our community hasn't shown any substantial interest in yet. The move file/folder to root feature request has only two votes so far and it is not currently planned for implementation.

Busy indicator

We have tried to reproduce the described behavior but without any luck. It would be really helpful if you can share the steps to reproduce the issue, e.g. on FileManager's demos so we can inspect the issue and take the necessary steps to correct it.

Regards,
Dimitar
Progress Telerik