Post a reply to the thread: File selection at runtime
Click here to log in
What's the name of our main installation product (in uppercase letters), directly followed by the current year?
You may choose an icon for your message from this list
Will turn www.example.com into [URL]http://www.example.com[/URL].
Re: File selection at runtime Hi Kevin, I would suggest to download the "Examples Package" and the "Learning SetupBuilder Part I". The "Check Box Dialog.sb7" and/or the "Custom Dialog Demo 1.sb7" (if you need custom dialogs) demo projects should do what you want. Does this help? Friedrich
Re: File selection at runtime
Re: File selection at runtime How can I add multiple checkboxes on one panel? I have 3 options I'd like to place checkboxes for on 1 panel. I'm having trouble on how I'm supposed to do that. If I add a wizard dialog in scripting and try and do it that way it places each checkbox on its own panel. Thanks! Kevin
Re: File selection at runtime I agree, the delta patches are not needed. The "update installer" makes more sense along with detecting the previous version. Possibly making a web installer to be used the first time, so if they dont have the wamp stack installed it pulls it all, otherwise it just pulls the new php and updates? Kev
Re: File selection at runtime Hi Kevin, You can create a "stand-alone" upgrade or "live-update" (web update) project for this, no problem. But IMO, it does not make much sense to make use of the binary patch (delta update) feature in this case. The compiler will already highly compress your php. And if the expected "bandwidth saving" is not at least 500MB - 1GB then I would avoid the extra layer of complexity imposed by delta patching. BTW, the install folder is automatically stored. The "Detect Previous Version..." script function lets you detect the path (and even version) of a previously distributed version of your product Friedrich
Re: File selection at runtime Yeah I think since the application files are actually php it's easier to actually save the install directory in a reg entry and then just create an "update" installer that looks at the entry and just overwrites all the php files when its run. The way the app works is when you manually overwrite all the files (except the db config) and run it the first time it self-upgrades, so I think above is the easiest way to accomplish the update. Kevin
Re: File selection at runtime Hi Kevin, It all depends on your deployment strategy. A patch file is an update or revision file that contains only the differences between two or more files. Since the patch file contains only the changes, it is a much quicker and economic method of distributing revisions. You can patch files in multiple-folders. But do you really have to use binary patch here? As I understand it, using delta-patch would over-complicate things in your case. Friedrich
Re: File selection at runtime Ok a hidden file was being left behind that was created when an app ran. Oy. I'm good now. Next question. Can the web update/delta patches be used against a single directory? What I want to do is a full install of a WAMP stack that includes our PHP application. Once installed the WAMP stuff wont change, only the application itself, so only the directory thats in will change. Maybe create a web install version as well. Thanks! Kevin
Re: File selection at runtime I havent done that yet but will shortly. Kevin
Re: File selection at runtime Kevin, Did you try a simple "dummy" project? Just create a new project, add a test folder tree, then compile and install/uninstall. Does this uninstall the folder tree on your machine? Friedrich
Re: File selection at runtime The uninstall log looks normal and shows the directory tree and files in them. Not sure what would be missing. Kevin
Forum Rules