[Beta 1] Saki's FileTree for Ext 2.0

[luisparada]

Sadly I must say, that is not what I thought it was, that method is useless, I guess, I don't know, because what it does is to add more horizontal space to the bbar or tbarm (up or down), that's not what i need, maybe is just that i'm kind of newbie and don't know how to set the new position. Please let me know about some method I could try.
Thanks.

[rtrocc]

since the toolbar items are configured on the inside of the extension you wouldnt be able to add the '->' items. I would imagine this can be accomplished with the DomHelper Singleton

[wes]

Saki, there is a bug in IE7 that removes all buttons from the tbar when clicking the "remove all" button.

It even happens in your demo. Try to add a file or files and click the remove all button (before attempting upload). This happens in IE7, works great in FF2. Just thought you should know

I encountered this problem as well. I fixed it by commenting out the following section in Ext.ux.UploadPanel.js onRemoveFile function. I can see no side effects and the Panel is working beautifully in IE and FF.

//if(wrap) {
// wrap.remove();
//}

If anyone is aware of another solution or knows that this solution will cause problems, please let me know.

Thanks again to Saki for a great control.

[njeriextjs]

Saki,

I am looking to add some custom menu (e.g "zip" , "unzip" ) to the context menu of the FileTreeMenu like mentioned in post#296 on this forum. I saw your response in post #297 on extending the FileTreeMenu but I don't seem to get it. I know the concept of extending a class and I have done this on other controls BUT for the FileTreeMenu...I seem lost.

Currently , I don't see an addItem function ( or something similar ) in FileTreeMenu - How do I add new Menu?

Thanks

[rtrocc]

I encountered this problem as well. I fixed it by commenting out the following section in Ext.ux.UploadPanel.js onRemoveFile function. I can see no side effects and the Panel is working beautifully in IE and FF.

//if(wrap) {
// wrap.remove();
//}

If anyone is aware of another solution or knows that this solution will cause problems, please let me know.

Thanks again to Saki for a great control.

Thanks for this solution, im glad I wasn't the only one who found the problem

[yhwh]

Hi Saki!
I think there is a bug in the cmdCallback at line 609 of Ex.ux.FileTreePanel.js
The original look like this.

			if(true === o.success) {
 				switch(options.params.cmd) {
					case 'delete':
						if(true !== this.eventsSuspended) {
							this.fireEvent('delete', this, this.getPath(options.node));
						}
						options.node.parentNode.removeChild(options.node);
					break;

As you can see the node is removed after the fireEvent, so when you listen for 'delete' event in FileTreepanel the node is still present.
So to correct this

			if(true === o.success) {
				switch(options.params.cmd) {
					case 'delete':
						if(true !== this.eventsSuspended) {
                                options.node.parentNode.removeChild(options.node);
							this.fireEvent('delete', this, this.getPath(options.node));
						}
					break;

Then i have some questions
Here an example
Why in deleteNode at line 763 of FileTreePanel do you this?

var options = {
					 url:this.deleteUrl || this.url
					,method:this.method
					,scope:this
					,callback:this.cmdCallback
					,node:node
					,params:{
						 cmd:'delete'
						,file:this.getPath(node)
					}
				};

You could use instead for best REST compliance something like this:

var options = {
					 url:this.deleteUrl || this.url
					,method:'DELETE'
					,scope:this
					,callback:this.cmdCallback
					,node:node
					,params:{
						file:this.getPath(node)
					}
				};

The cmd params isn't needed.

So it's better to use different url for each action creating directory delete rename etc..(by forcing the use of newdirUrl deleteUrl options) and making a difference between deleting dir and deleting a file (so we could use different url for each delete).
Because it could be easy to add to Saki's FileTree a support for database version and it will separate server_side implementation (easy to use with different MVC framework).
Will you integrate big patch for database support (it needs additionnal params in uploadpanel too) and separate server_side implementation ? Because i'am working on it and filetree is in beta state so you may not want to add extra features...

Best Regards,

Nicolas FERRERO

[jsakalos]

1) Why is it bug? Event listener gets node that is going to be deleted as argument as it may need it for some user processing.

2) method can be only GET or POST.

3) You can provide deleteUrl if you want. If it is defined it takes precedence over url. I find it very questionable if different urls for different operations is a good idea. In my backend, the whole processing is done in one PHP script and cmd says what command is to be executed.

[smartlit]

Hello,

I've downloaded your component and trying to use it. One question: it seems that to show the progress of the upload you use a file called progress.php. I cannot find it included in your package. Where can I find it?

I will use the system on a Windows server and I'm programming in .NET. Is there something available in .NET (.aspx)?

Thanks,

Paul

[jsakalos]

I personally do not use M$ "products" except hardware ones and I'm not aware of any aspx FileTreePanel backends. Anyway, there is full client/server doc on the demo page that you can use to code it yourself.

[smartlit]

Hello,

Thanks for your reply. I have found a small bug in FF3 using http://filetree.extjs.eu. You can reproduce it this way:

• Go to http://filetree.extjs.eu
• In the UploadPanel click Add to upload a new file
• Choose the file and click Upload
• Wait for the upload to finish; once finished please read carefully the browser's status bar: although the upload has finished, it still says something like "Transferring data from ..."

Thanks,

Paul