0001551: AVDump2 CL Interface - AniDB Bug Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0001551	Avdump2 / autocreq	Feature Request	public	2009-05-08 21:20	2012-08-20 22:07

Reporter	DvdKhl	Assigned To	DvdKhl
Priority	normal	Severity	feature	Reproducibility	N/A
Status	resolved	Resolution	fixed

Summary	0001551: AVDump2 CL Interface
Description	Currently I have copied the interface of the original AVDump and most of the options work in AVDump2, but I'm not really happy how it is now. There are too many switches to handle them at the commandline. So here is my idea/plan: Use a configuration file in xml format: http://pastebin.com/fc8d62b4 (First draft) And then point avdump2 to the xml file though a cl option. I'm also thinking of applying XSLT on it (if it is not too hard to do), which would make it highly configurable. With XSLT one could use varibales to get and play with the cl parameters. (i.e. avdump2cl.exe -ac:alpha:beta resulting in <xsl:variable name="ac"><option>alhpa</option><option>beta</option></xsl:variable> ) This way getting backwards compatibility to the old cl interface would be very easy. Is this over the top, or actually useful?
Tags	No tags attached.

Date Modified	Username	Field	Change
2009-05-08 21:20	DvdKhl	New Issue
2009-05-08 21:20	DvdKhl	Status	new => assigned
2009-05-08 21:20	DvdKhl	Assigned To	=> fahrenheit
2009-05-08 22:05	fahrenheit	Note Added: 0002793
2012-08-20 21:59	worf	Project	Avdump1 => Avdump2 / autocreq
2012-08-20 22:06	DvdKhl	Assigned To	fahrenheit => DvdKhl
2012-08-20 22:07	DvdKhl	Note Added: 0003306
2012-08-20 22:07	DvdKhl	Status	assigned => resolved
2012-08-20 22:07	DvdKhl	Resolution	open => fixed

fahrenheit 2009-05-08 22:05 reporter ~0002793	ei, it's your client you are free to use whatever method you feel is good to store settings, xml is a good option for those yes.

DvdKhl 2012-08-20 22:07 developer ~0003306	New CL Args have been implemented. XSLT idea has been dropped.