2007-11-30, 08:35
I think UltraBrutal has the best take on this FR, as from a dev point of view it would need to be broken up into front-end and back-end changes to be made. It seems like the backend changes could be done with relatively minor dev time required, and I think they would allow an existing database to be used without issue or updated. Also, if we simply have these optional fields, it would allow changing the "type" of a record to be done easily. That way if you either rip something you have on DVD, you could keep all of the existing stuff for that item, you would just need tell XBMC its "online".
For the front end I think there would only need to be a few main changes, and those only to the database viewing stuff.
1-We would need to add options somewhere for viewing with and without offline media.
--I think that since the current view types are basically structured around various queries against the dbase, this would be pretty easy.
2-there would need to be a dual-state new button added to the "view item" window
--This would simply be a toggle that would say "make offline" / "make online" as appropriate.
3-The above-mentioned button would call a dialog box depending on which state was currently in effect.
--"Make Online" would need a "Browse To Media" filepath entry button, and OK and Cancel buttons. When you enter a path and hit "OK", the path is checked to see if its accessible (just like the Sources GUI does when entering new Sources pathes), and if it exists, that path + the Bool "offline" elements are written to the item in the database. Again as per the Sources editor, if the path isn't currently accessible, you should be warned but should still be given the option to proceed or cancel.
--"Make Offline" would need some simple text field entry controls, used to fill the optional tags for Offline items, plus again OK and Cancel buttons. When you hit OK, no processing would need to be done on the text inputm it and the appropriate Bool flag would simply be written to the item in the database.
For switching back and forth, if the extra Offline txt fiels or the Online file path !='', these elements should be retained and auto-filled into the dialog boxes.
For the front end I think there would only need to be a few main changes, and those only to the database viewing stuff.
1-We would need to add options somewhere for viewing with and without offline media.
--I think that since the current view types are basically structured around various queries against the dbase, this would be pretty easy.
2-there would need to be a dual-state new button added to the "view item" window
--This would simply be a toggle that would say "make offline" / "make online" as appropriate.
3-The above-mentioned button would call a dialog box depending on which state was currently in effect.
--"Make Online" would need a "Browse To Media" filepath entry button, and OK and Cancel buttons. When you enter a path and hit "OK", the path is checked to see if its accessible (just like the Sources GUI does when entering new Sources pathes), and if it exists, that path + the Bool "offline" elements are written to the item in the database. Again as per the Sources editor, if the path isn't currently accessible, you should be warned but should still be given the option to proceed or cancel.
--"Make Offline" would need some simple text field entry controls, used to fill the optional tags for Offline items, plus again OK and Cancel buttons. When you hit OK, no processing would need to be done on the text inputm it and the appropriate Bool flag would simply be written to the item in the database.
For switching back and forth, if the extra Offline txt fiels or the Online file path !='', these elements should be retained and auto-filled into the dialog boxes.
