View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001420 | MMW v4 | Install/Config | public | 2004-06-01 02:20 | 2008-03-06 19:05 |
| Reporter | rusty | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | assigned | Resolution | fixed | ||
| Summary | 0001420: Support multi-user installs and installs with configs saved to OEM directory | ||||
| Description | MediaMonkey should be able to: a) Install mm with a library/config that is accessible to all users b) Install with library/config stored to a custom location for OEMs | ||||
| Additional Information | See: foobar 2000 has a nice implementation http://www.mediamonkey.com/forum/viewtopic.php?t=1864 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Also mentionde by another user: here is my wish : It would be nice to have user identification. Some users with administrativ rights (Add files, edit tag, delete files, move files, ...) And normal users (create play list, edit there own playlist, ...) n my dreams, i saw : - A login prompt at MM startup (or even more, no prompt but using NT Authority) - A window with user management (creat user, edit password, edit rights,...) - A window with check boxs for each rights. eg : User : Administrator (combo) X File editor . --> X Add files . --> X Delete Files . --> X Rename files . --> X Move files X Edit Tag X All playlist editor X Create virtual CD X Burn CD Note: the above requirements are not that important, and can be moved to another bug. edited on: 06-01-04 14:34 |
|
|
1. I don't think this should be a part of MM. In order to make it helpful, it would have to be a part of installer and I'd like to avoid this (in order to make the install process as easy as possible). 2. The default location was already changed for 3.0 in another issue. 3. Other parts are possible, but need to be more specified. |
|
|
1. Per IM discussion, this functionality must be implemented in a manner that won't confuse most users. So it doesn't have to appear in the installer, but it should be available as an option when MM is initially run. It could be e.g. a button on the scan folders dialog 'Configure Database Access': e.g. Database Access Configuration This will set up the MediaMonkey Library: (o) Accessible to the current user ( ) Shared with all users on this machine ( ) Shared across a network with multiple machines and users Library Name: __MediaMonkey__ [Next] Jiri also raised the point that such functionality could be very confusing in scenarios where the user attempts to re-configure DB Access from Accessible to the current user --> Shared with all users (or vice versa). Suggested approach to dealing with this is to only allow the library access configuration to be set up for a New Library (which might imply a different UI). We need to discuss this further. 2. True, bug 1796 deals with this issue. From that bug, though, it was unclear whether MediaMonkey.ini is also moved to the new location. Can you clarify? 3. From an OEM perspective all that's needed is to be able to compile a build so that the DB and .ini file can be installed to: User/Local Settings/Application Data/<ShortProductName>/<ShortProductName>.db and User/Local Settings/Application Data/<ShortProductName>/<ShortProductName>.ini |
|
|
Based on how winamp does it, we could have MM popup the following dialog whenever it is run after an install: Each user on your computer can customize Winamp with separate settings for color schemes, skins, bookmarks, playlists, and media library content. ... (o) Shared settings for all users ( ) Separate settings per user account [x] Copy user settings to the new place . . From: _______________ . . To: _________________ Note: The 'Copy user settings...' section only becomes active if the user selects 'separate settings'. Side note: it might also be useful to prompt the user to set the following the first time it is run: -Set network settings -Choose skins |
|
|
In 3.0 it was already implemented, all data should be in All Users/Local Settings/MediaMonkey As for configuration by OEM - I'm afraid it would cause problems e.g. when MM + OEM MM are both installed, so I'd rather keep it as is. As for single vs. multi user installs - this would have to be configurable somewhere during setup, I don't know it it's really important, we can probably defer it. |
|
|
As discussed, this will be treated as lower priority. |
|
|
This becomes almost Absolute as introducting BUG 0002439 |
