Ticket #510 (new Feature)

Opened 1 year ago

Last modified 1 year ago

Device Wizard: configure device in read-only

Reported by: fsck222 Assigned to: bflorat
Priority: 3, low Milestone: To Be Decided by Jajuk Team
Component: (Java Developer) Functional Version: 1.4-trunk
Keywords: Cc:

Description

Can we have a new option in the Device wizard to have the device in read only so we can be sure that Jajuk won't be able to do any changes in the device (tags/images/etc..).

Attachments

Change History

05/31/07 23:05:08 changed by bflorat

  • version changed from 1.4 to 1.4dev.
  • milestone deleted.

Yes, it could be done but I wonder if it worthes the added complexity in code and in UI, what's the use case ?

06/01/07 00:36:13 changed by fsck222

to forbid Jajuk to change tags and also copy covers in the directory. this is useful when you want to connect a media that you don't own and you want to be sure to not alter it.

06/07/07 13:10:25 changed by fsck222

also it is to comfort users and let convince them that Jajuk will not touch any files (not like another popular player (keyword hint: apple) completely messing around with filenames and tags)

06/07/07 18:09:11 changed by bflorat

it could be done by adding a test in all methods performing java.io calls but : - it would add a new option on the device wizard and properties panel, some say that jajuk is complex... - there are *many* of them (to create playlists, covers, tags, reorganize) - it can become complexe if the collection data is store in the device itself (something very waited by users to put all jajuk data + music on a single external disk, see Aero tickets) - it is 99% sure that new developers will forget to check it, even with doc - it looks pretty dirty and error prone on a architecture way, it should be done at the OS level IMO - Jajuk doesn't write anything without that user didn't asked from the UI (like cliking on a save cover button), except about collection data of course. If user think jajuk can mess the device, I 'm not sure the fact of adding a RO option would allay him, some messages in the readme or on the website would make the trick, isn't it ?

06/07/07 19:35:33 changed by fsck222

It is a marketing value. Jajuk isn't well known (yet), it is to comfort users that do not know Jajuk but want to be sure at 100% that is they try Jajuk, it won't reorganise their music collection or tag files. A lot of players changes users data without telling them! Some users have spend hours to sort/tag/download cover for their albums. User data is important, we don't want to screw with it. I know Jajuk is not doing changing data like that but it is not said during the first use, hence some users may not be confident enough to continue.

To make it simpler for now, we could have the read only feature globally and not per media?

06/07/07 20:13:36 changed by anonymous

all my previous remarks apply for a global ro too. you may be right but I think this would be better to give this message to users using the we site, let's say in the feature page that implementing something... at least for now...

06/19/07 22:01:10 changed by fsck222

  • milestone set to To Be Decided by Jajuk Team.

07/10/07 12:23:14 changed by fsck222

  • milestone changed from To Be Decided by Jajuk Team to 1.5 "Lothlórien".

07/10/07 17:37:40 changed by bflorat

  • priority changed from 1 to 3.
  • type changed from Discussion to Feature.

10/17/07 23:08:41 changed by bflorat

  • milestone changed from 1.5 "Lothlórien" to To Be Decided by Jajuk Team.

Add/Change #510 (Device Wizard: configure device in read-only)