Installation
Spider Monkey Panel 1.6.1 or higher is required. Only stable releases are supported.
It's recommended to download this mod version which includes some improvements see here. This same version is shared on every new releases of my scripts to make it easier for people (there is no need to redownload or reinstall).
Add the component to your foofar2000 installation at the Preferences\Components section. Then click install and load the component file.
An Spider Monkey Panel must be added to the current layout anywhere on the UI. There are some minor differences between the Default UI (DUI) and Columns UI (CUI), but in both cases the layout can be edited using the menu ’View\Layout\Live editing’:
Multiple SMP panels can be added to a layout (being totally independent entities), therefore multiple script panels may be added. After a panel has been added to the current UI, it must be configured to load the main script file, either as package or file (as required on the instructions below). It can be done by right clicking on the blank SMP panel.
Set an unique name for the panel so popups can use it instead of panel UUIDs.
Copy all files from the zip into ’YOUR FOOBAR PROFILE PATH\scripts\SMP\xxx-scripts´. If the folders don’t exist, create them. Any other path WILL NOT work without editing the scripts. (see ’_TIPS_and_INSTALLATION_vX.X.jpg’). Multiple scripts may share some files (specially helpers) so overwrite if asked to do so. Then load the script named ’buttons_toolbar.js’ (*) into a SMP panel within foobar (see above).
- For standard installations: ’C:\Users\yourUser\AppData\Roaming\foobar2000\scripts\SMP\xxx-scripts...’
- For portable installations >= 1.6: ’.\foobar2000\profile\scripts\SMP\xxx-scripts...’
- For portable installations <= 1.5: ’.\foobar2000\scripts\SMP\xxx-scripts˙..’
If you upgraded to >1.6 from an older portable version then it may be possible that the ’profile’ folder does not exist. In such case you have to create it and move all the configuration folders/files to it, where they should reside (instead of the root of foobar2000 installation path). If you don’t move all the configuration folders/files, then, on startup, default values will be used for things not found, probably ”losing” the theme or other customization. You may ”fix” it later moving the missing files which still reside in the root. May take some tries to do them all.
- Some native folders and files which must be moved include: index-data, js_data, component-updates, configuration, crash_reports, user-components, foo_spider-monkey_panel, library, playlists, theme.fth, LargeFieldsConfig.txt, version.txt
- Some extra folders from other components which must be moved include (non extensive list): autobackup, dvda_metabase, foo_httpcontrol data, foo_youtube, images, lastfm, python, sacd_metabase, vst-presets, yttm, minibar.db, playlist-tree-0.pts, playlist-tree-1.pts
When the script finds it’s being loaded within a portable installation, it will set the default paths using relative paths. It will also warn with popups and/or the console about the -non recommended use of absolute paths on portable installations.
When using this script along Search-by-Distance-SMP or other button tools, all buttons files must be loaded within the toolbar (instead of an independent panel per button). Go to Toolbar Configuration for further instructions.
Multiple panels (toolbars) are allowed without any special requisite. Note some panels may use share some files (to speedup their processing). Some features may require every panel to have different names, it will be warned via popups.
There is nothing special to do but following the standard installation steps and overwriting all files as needed. In case an update changes something or requires an additional step, that will be warned on the release itself.
it's possible to download the more recent version directly from the repository, instead of the releases page. In such case it's possible that some changes are not fully tested; the list of "unreleased" changes is always shown -and updated- at the changelog. The installation instructions are the same than the other cases. To download the current repository, look below:
