Distribute as Sencha Cmd Package

[ivan-novakov]

See http://docs.sencha.com/extjs/4.2.0/#!/guide/command_packages

[hhandoko]

First of all, thanks for the widget, it's been proving really useful!

FYI, I've attempted to include the widget as part of the build / package process for my solution (i.e. Sencha Architect build command, which actually runs Sencha Cmd in the background) but met with issues. For some reason the Ext.data.Connection.setOptions() is not setting any URL.

It only happens if the solution is packaged (regardless whether the widget is included as part of the build or not), if I publish my app as-is without any packaging (i.e. multiple json under the '/app' folder instead of one massive app.js file), it works.

[tvaughan73]

I am having this issue too. Any idea how to fix? In my dev environment I am calling the uploader with

    var me = this,
        dialog = Ext.create('Ext.ux.upload.Dialog', {
            dialogTitle: 'Attach Files',
            uploadUrl: 'request',
            uploadParams: {
                direc: 'check_register',
                model: 'check_writer',
                action: 'import_file',
                'user_temp_dir': me.userTempDir
            }
        });
    dialog.show();

Everything works great in dev but when I build the app with cmd and try to upload I get the same problem with Ext.data.Connection.setOptions().

Doing some testing I can tell that uploadUrl and uploadParams are not being passed into the initComponent function in Dialog.js. When i log them to console in dev they show as expected but in the cmd app it comes back as null.

Any ideas on how to fix?

[eriveraa]

Hi, in my development machine everything works until i make a sencha app build.

The issues are:

• The component perform a POST in production (after build), but a PUT in dev mode.
• The additional parameters are lost in production, but they work in dev mode.

How do you include this awesome component in the build? please provide detailed instructions. Thanks in advance.