As to the structure of playviews being confusing, I know what you mean, I went in before and edited the structure a little to try and make it more sensical before, don't know if I did so at the time, but because you said its still confusing I guess I failed lol. Although I say that I also made the image2GVD program so I do understand the structure and how its supposed to be. I can try to answer anything you have questions to. As for a "pimped GUI" I'm pretty sure I can do that

. And as for IRC I will pop in once in a while so I hope to catch you soon.
Put in my boots for a second, the only two ways i have to start trying to see how this format works is by reading the playview wiki page (but i dont understand it overall) or by looking at the files (and right now i dont have any file but i guess will not be hard to get some to start from scratch)
There is a third way as you said... by asking you, this seems to be the best one XD
But still... the playview wiki page is going to be one of my first worries and the thing that is going to take me more hours to rewrite... i know myself, im that picky
-----------------------
About how is redacted the playview wiki page, is normal, im not trying to critizise it in a destructive way
What happens with that kind of pages is initially are used as a worklog so it suffers lot of corrections and rewritings (and brainstormings and speculations that stays for a time but later is needed to delete them when proved wrong, i use to do this a lot in other wiki pages btw sorry for that but sometimes is the only way to progress)
Ideallistically... that kind of pages when are a bit mature someone rewrites them to become more readable folowing two approaches:
-oriented to non coders
-oriented to coders
There must be some "introduction" for non-coders in most of the sections, of course an overall explain to serve as introduction to get the basic concepts of how it works and what the firmware does with it (this can go as deep as to being useful to coders too)
Playview page lacks some of this... mostly because the format never reached mature (iirc i was told there was lot of unknowns left)
Also, is the kind of page that is needed to be readed while having the files opened in a hexeditor/notepad++ etc at the same time... to compare what you are reading with a sample of the files... otherway is almost imposible to get the overall idea, i never did that btw
----------
About the GUI... before suggesting anything is needed to get the overall idea of the list of features availables in playview format.... this is going to be like the "requirements" for the GUI
Every one of that features needs to be presented in some intuitive way for the user to just "click" in it, or by entering a value in a box
So i have no idea how could be that GUI... but thiking in the features we know at this point (and probably some others we ignore) is going to be a hard and long project