Best Practice for ExtJS (or indeed any Javascript) use in Setup Options script

If I have the script somewhere in a directory I bring over using a file resolver, having it available won't be a problem but locating it in the unzipped directory might be - will see after some testing if I ever get a chance to do it

If I have the script somewhere in a directory I bring over using a file resolver, having it available won't be a problem but locating it in the unzipped directory might be - will see after some testing if I ever get a chance to do it

Can bring the file over by adding it to a directory which is transported via a file resolver. The issue is boiling down to being able to locate this file when the package is unzipped - it will be somewhere in the unzipped package folder but where remains to be seen

AFAIK the package is unzipped into core/packages, and file resolvers are only executed *after* entering setup options so how much use is that?

May be lucky referencing core/packages but I know plenty of sites where the core dir is out of webroot and you'll not be so lucky.

Well, having done some more testing on this, unfortunately it has all become academic as even inlined client side scripts don't run in the setup options window and there is no way that I can find to hook into the window render event to trigger any either.

One thing I did discover is that the working directory for the installer is in connectors/workspace.

Well, this continues. Had a brainwave about the script execution last night - figured it might be possible to trigger a script in the setup options window by including an image and using the onload event to fire a function and have just tried it - it worked!

Now to try with the blur event for one of the text fields - reason I want to do this is to change the enctype of the form to allow users to upload an image as part of the setup process.