Well, have you tried this script?
yessir
I wrote it to ease up some of the things I do with fglrx driver, which is performing initial setup and setting up tv-out, adjusting video settings, specifying which screen the video overlay is displayed on. So it does (for me) more than was said here. Besides, it reads and displays various settings from /etc/X11/xorg.conf file.
True, but the purposes of a GUI are typically:
1) Replace a series of command-line entries with a simple click.
2) Allow various perspectives to be viewed at the same time easily without need for scrolling and various commands to display the info.
3) Organize info in a well designed menu.
Looking at the functionality for setting up an xorg.conf file,
aticonfig --initial
That is 1 command. It's not complicated. it takes longer to launch your program, click on the correct tab, and click the button etc.
And being as it was one of the main 'purposes' of the program, it seems to just be more difficult than a command line!
Now, I would keep it included if the panel had alternate functionality etc.
But remember, An Initial Config is created 'only once'. So that option likely won't get used often.
Once again, the TV functionality is very practical for the app, but needs other features such as the ones previously specified to make it worthwhile.
I wrote it since the fglrx-control panel for me was useless, and it's features have been diminishing. I could not set up tv-out with it (well, once I could, with an older version, but not now).
I hear ya. The Ati Control Panel supplied with the drivers is not a control panel at all. It's a very weak dev-util type app.
Could you elaborate on these things: where can I find information on how aticonfig is used to adjust these settings?
As Michael pointed out, they are all listed under aticonfig --help 
Do realize, I am currently using scripts to toggle features such as powerplay on/off. wrote them and created launchers and tossed them on my desktop. So I double-click and boom, powerplay enabled. Click again, powerplay disabled, etc. Now I do not have the desktop space nor the patiance to create them for every single option, but I will say, combining MORE functionality into the single program makes your program more valuable.
I mean no disrespect, but in it's current condition, it's more of a pre-prototype. But I'm sure once you go through all of the functionality etc, and add it, the program will quickly become usefull! 
A snippet from the help re: fsaa:
Code:
FSAA Options:
--fsaa={on|off}
Enable/disable full scene anti-aliasing. Enable this option to enhance
photo-realism in 3D rendering. Disable it to get the most accurate 3D
image.
--fs, --fsaa-samples={off,0,2,4,6}
Set the number of FSAA samples per pixel or 2, 4, 6. off is the same
as setting 0 samples.
--fsg, --fsaa-gamma={on|off}
Enable/disable FSAA gamma.
--fmsp, --fsaa-ms-positions=x0,y0,x1,y1,x2,y2,x3,y3,x4,y4,x5,y5
Change the FSAA Multi-Sample Positions for x0,y0 to x5,y5. You must
specify exactly 12 real number values separated by commas.