[Beta 1] Saki's FileTree for Ext 2.0

[Bobrovnik]

Yes, you are right, sorry. I will correct that

[avsomeren]

Well, don't be sorry, you did a great job fixing these issues!

Thank you for that.

[jpipas]

Thanks for those patches Bobrovnik. However, when I go to click the 'File' button or right-click on the filetreemenu, I get this exception

menu.getEl() is undefined - on line 1747 of FileTreePanel.js

menu.showAt(menu.getEl().getAlignToXY(alignEl, 'tl-bl?'));\n

I can confirm that the contextMenu gets created - however, the second time around when the function just returns it - I get the error.

Any ideas? Appreciate the help.

[Bobrovnik]

That is also my mistake, I have forgotten to add to patches list one line. When you are using Ext 3.0 you will have to render this menu. If I am not mistaken I have added line menu.render(); after

menu.getItemByCmd('sep-collapse').setVisible(this.enableNewDir || this.enableDelete || this.enableRename); 

in file FileTreeMenu.js

But I am not sure about it, I will confirm on monday, when I get to the source code

[jpipas]

Excellent. The menu.render() actually goes in FileTreePanel.js - after the line (1467)

menu.getItemByCmd('sep-collapse').setVisible(this.enableNewDir || this.enableDelete || this.enableRename);

Now the menu renders - however, the upload panel within the menu is missing. The upload panel shows - but theres no buttons, or anything inside, as if it were blank.

I'll see if I can do some more investigating myself.

[wallacer]

Can anyone give me some ideas as to why my uploads don't stop when I click the stop upload button? Has anyone else had this issue?

var newUploadPanel = new Ext.ux.UploadPanel({
            
            url: PROXY_PATH+'newUpload.php',
            path: navPanel.getSelectionModel().getSelectedNode().id,
            method: 'post',
            progressUrl: PROXY_PATH+'progress.php',
            maxLength: 50,
            width: 'auto',
            minHeight: 500
});

[jsakalos]

Stops are done calling browser's window.stop() method so it can be browser dependent. Is it?

[fraric]

hi,
i want an information about Ext 2.3 and file uploader.
i've read in change log 2.3 ext have change Ext.data.Connection doFormUpload

http://www.extjs.com/deploy/ext-2.3.0/changelog.html

Ext.data.Connection
Document request's timeout option.
Document that the url config of Ext.data.Connection may be a function.
Restore form attributes after doFormUpload.
i want to say why you have write this fix/upgrade

i think are this add code

buf = {
target: form.target,
method: form.method,
encoding: form.encoding,
enctype: form.enctype,
action: form.action
};

and at the end function


form.target = buf.target;
form.method = buf.method;
form.enctype = buf.enctype;
form.encoding = buf.encoding;
form.action = buf.action;

this buffer clean target element i frame

in FileUploader coponent when i want to stop upload component find target of form but buffer have clean target and stop cannot find iframe and cannot stop upload

, stopUpload: function(record) in file uploader call getIframe

/**
* Geg the iframe identified by record
* @private
* @param {Ext.data.Record} record
* @return {Ext.Element} iframe or null if not found
*/
, getIframe: function(record)
{
var iframe = null;
var form = record.get('form');
if (form && form.dom && form.dom.target)/**/ this is empty value
{
iframe = Ext.get(form.dom.target);
}
return iframe;
} // eo function getIframe

what i can do for fix this problem?
i change doFormUpload???
i 've read Ext 3.0 doFormUpload already change? and dont use the same code...
(Restore form attributes after doFormUpload) it's a functionality for ext 3.0...


if i make an override of this function doFormUpload version 3.0 in Ext.2.3 upload i can have aproblem?
it's a correct approach?
thanks a lot for help
ric

[smartlit]

jsakalos: the above post by fraric is quite difficult to understand, but it simply means that under Ext 2.3 the STOP function in your component stopped working. It was working in Ext 2.2.1, but it stopped under 2.3.
Can you please check why? What can we do to fix that?
Thanks,

Paul

[jsakalos]

Which one of those three (form && form.dom && form.dom.target)is falsie?

It could be some timing or a changed sequence of something in 2.3