What's new? | Help | Directory | Sign in
Google
                
Search
for
Updated Sep 13, 2007 by alexandru.trutia
GraphicalInterface  
A graphical interface approach for the converter

The first try

I started the project and following the classic style, I made this:

The project can still be modified, because it doesn't have too much code. I hope it's ok.

Introduction

As not all users know how to use command line tools, a Graphical Interface would help them get the best from the converter.

Details

Here's a possible layout i've been considering for the converter:

And a possible skin for the interface:

Of course this is just the first try and I am open to any suggestions.


Comment by tomvanbraeckel, Sep 12, 2007

I like the design (and the skin too :-) but could you add a few use cases ? Like:

  1. Ann clicks "Add media" to select one or more files to add to the filelist.
  2. The source format can be auto detected so she only has to specify the destination format (AMV or MTV)
  3. Then she sets the conversion specific options (say 160x120, framerate,...)

Also, how exactly can a user batch-convert multiple files ? Are they saved in one target dir or in their original dir while given an .amv/.mtv extension ?

Comment by alexandru.trutia, Sep 12, 2007

Well, the user clicks on the add media button and he can choose one file at a time to be converted. Then the filename is written in a box, in the "different format choosing box". There will be another box right near the first one wich specifies the output file. Once the user has chosen the input/output files, he can choose the format to convert to (the controls will be in the "Conversion specific options" box), maily AMV and MTV (and later ACT) and the framerate and resolution and he hits ADD. Now the files and their corresponding settings will be added in the "input output filelist" box. The last step is to press "Convert" and watch the show :).

About the batch-thing, I will have a linked list holding the options and settings for each file added to conversion and fire FFMpeg for each of them.

Comment by tomvanbraeckel, Sep 13, 2007

I think I understand, but wouldn't it be simpler if you had one list or table that hold the inputfilename, outputfilename and their corresponding settings ? If I understand correctly, you now have two lists, "different format choosing box" holds the input-output-filenames and "input output filelist" holds the inputfilename, outputfilename and their corresponding settings. I also don't understand why the different format choosing box isn't called "filename box" or something like that - the destination format is chosen in the "conversion specific options". I'll understand better when I see the app off course, so as long as you keep later adjustments in mind while you code it, my questions (and ramblings) don't matter that much; if you think it has to be done this way, then it probably is :-)

Comment by tomvanbraeckel, Sep 13, 2007

Looks great Alex, good work !

Comment by Sterje, Jan 02, 2008

Is anyone still working on this GUI? I'm willing to try and help if any help is needed.


Sign in to add a comment