Progress and CLI options

We continue to make progress. We now have a target feature set for an initial working build, and are closing in on completion. I just performed the first successful conversion using my Converter framework, the descendent of the Plugin architecture I talked about in our first presentation. We are targeting for feature completion tonight, so that we can work out integration issues and get a program that actually runs.

For the most part, progress is going well. Within my code, the biggest obstacle to having a full set of basic functionality is what I’ve been referring to as argument options. These are command-line flags that take arguments. The problem is there is no clear standard for these options, from -l{filename} in GNU ld to -V{0-9} in LAME to -loop {number} in mplayer and -o {filename} in FLAC. The Converter framework needs to:

Pass the arguments to the program correctly – programs with a space before the option expect it as the next argument passed, while those without expect in the same argument.

Handle the option content – some options are one of a set of possibilities, some are a number, some are an arbitrary string.

Provide configuration hints to the GUI – We are generating the settings pages dynamically, so I need to tell the GUI what is valid, and give info on a sensible way to expose it.

Once this issue has been dealt with, the framework will be largely complete, enough to start building out converter support.

Many thanks for finding the time to share with you this, Personally i think fervently about this and that i get pleasure from studying this topic. Please, while you gain information, please update this website with increased information. I’ve discovered it very beneficial.

I prefer the helpful info you provide in your articles. I’ll bookmark your website and check again here regularly. I am quite certain I am going to learn lots of new stuff below! All the best for the following!