MobileRead Forums - View Single Post

dbolack · 02-26-2012, 05:22 PM

My initial thought is sort of neither.

My impulse is to alter the fields to store arrays and allow the user to select ( defaulted value and per field ) which value to go with. Store the value with the plugin name as the index and the corresponding value.

Not sure yet how much a pain that would be to deal with. I should think this would be simpler to implement and the user to use. Might not be as elegant, but it should be effective.

As to custom column meta data, two thoughts.

One, a check on install for custom columns "expected" by the plugin and prompt the user if they should be created if missing.

Two, go ahead and store metadata we don't know how to deal with.

Probably both.

02-26-2012, 05:22 PM	#25
dbolack Junior Member Posts: 6 Karma: 10 Join Date: Feb 2012 Device: Nook Tablet	Merge/Clobber Meta Data My initial thought is sort of neither. My impulse is to alter the fields to store arrays and allow the user to select ( defaulted value and per field ) which value to go with. Store the value with the plugin name as the index and the corresponding value. Not sure yet how much a pain that would be to deal with. I should think this would be simpler to implement and the user to use. Might not be as elegant, but it should be effective. As to custom column meta data, two thoughts. One, a check on install for custom columns "expected" by the plugin and prompt the user if they should be created if missing. Two, go ahead and store metadata we don't know how to deal with. Probably both.