I'm not volunteering to write the script,
#RUBY ZIP CPGZ ARCHIVE#
rbz and find the entire set of 'unzipped' SU Plugins and reinstall the one I accidentally binned etc.Ī script could clean the entire archive and add or remove the 'mac' file structure at the same time if desired. I think it makes sense that if you want a SketchUp ruby it comes in an identifiable package, I can do a search for. The current volume of *.rb & *.rbs currently around, all need to be wrapped in a.
#RUBY ZIP CPGZ MANUAL#
rbz with grep find and replace, and do the same for all the download advice, then any one requiring manual or alternate installs, simply unzips the *.rbz and carries on as usual. So, personally I think SCF and/or the ruby'ists should just change all current. rbz both open the easily on a mac, right click > open with, and you can even have them both 'auto' open after download, if you want to set it up. you can just right-click a file and say "Open with." (or if you use 7zip, or similar, it has a context submenu, with an "open archive" choice.) On Windows, renaming is not even necessary. it's just as easy to rename the file from rbz to zip, as it is from zip to rbz. However, Google chose this obtuse RBZ route - which offers no obvious advantages to we scripters - just more effort.ĭan Rathbun wrote:Anyway. That way the ZIPped sets would work for all users = while the users with the button-installer are mollycoddled, because they can't then mis-install a ZIpped set that way.
#RUBY ZIP CPGZ INSTALL#
RB/.RBS files at the base-level and only then install it. In my opinion it would have been better not to have had the RBZ format at all, and simply to have used ZIP archives for the button-installer, BUT to have had some pre-installtion checking built into it - so it'd unZIP stuff into a temp-folder, check for. AND as time goes by, more frequently RBZ sets and their own instructions - i.e. So looks like we are going to have to continue with ZIPped sets and their instructions.
as there will be many users who can't use RBZ as their SUp version won't have the button-installer for some time, if ever - unless they rename any RBZ as ZIP, and then we have gone full circle in expecting them to have a brain-cell or two. I think there will be an 'overlap' of ZIP and RBZ.
#RUBY ZIP CPGZ ZIP FILE#
BUT ANY ZIP file can be installed using your work around - which is potentially very messy to clean up ! In a way ONLY the RBZ files should be listed no matter what the user does when using the button-installer ***Selecting another file type will produce an error if it can't be unZIpped. and then see the various files/subfolders before moving them into the Plugins folder - and if they looked like holiday-snaps etc, then even the dullest user might reconsider their actions. You are right of course, BUT if users are so naïve that they can't currently extract some files/subfolders from a ZIP file and move them into their Plugins folder, then they are unlikely to have the sense necessary to think to type *+ to get to see ZIP files listed in the dialog AND of course whilst a RBZ is likely to contain only kosher plugin stuff that should be installed into the Plugins folder, a ZIP file could be total tosh, like someone's holiday-snaps, which will then be splattered all over the Plugins folder by the installer so this is hardly an improvement on the manual install method, where at least the user might manage to extract the ZIPped files into a temporary folder. One can just type * in the file name text field, but then you've already defeated the purpose of making things easy and non-technical.
0 kommentar(er)
