WiiFlow Hypertext Interface Guide?

With all the growing changes and options both existing, and bound for the 
future of WiiFlow, It may be in the programs best interest to include a very 
basic HTML viewer, for the purpose of accommodating wiiflow's ever changing 
list of interface controls. (Or various other wiiflow features to come, which 
may require winded explanation there of.)

This proposed HTML viewer would theoretically be accessed from the config 
screen, in the "Download Missing covers" section. perhaps As:

"DL the WiiFlow Operational Manual for your Version/Build?"
and
"View Operational Manual for WiiFlow v#.#.# b#"

Operational Manuals could be stored on a website, labeled by Version, Build, 
and Language, as HTML documents, so that they could be updated on the fly or as 
seen fit. example: 
"http://someplace.com/wiiflow_om_v#-#-#_b#a_lang.html" 
or 
"http://somewhere.com/wiiflow/om/Lang/v#/b#/index.html".

The user would only need to download from that site once per update of their 
software. The manual would be downloaded to the wiiflow folder, or an /om/ 
folder, or a saved cache, So bandwidth would not be an issue.

It's a big move which requires synchronization, and some for-thought. 
Not to mention some basic knowledge of HTML, Tables, and various Languages. But 
it seems as though, with the success of WiiFlow over all, that this addition 
would be well worth it. 

Here is some Perky reasons to go this direction :) 

♥ This method is preferable to the rigidness and file size of making PNG's of 
the operational manual, Or inccluding such bloat-data per-build per-language in 
each new wiiflow release. 

♥ It's editable -live- at the source, which makes later corrections of 
mistakes or spelling//grammar errors a breeze. (Useful when new  operational 
manuals finally become available in(are finally translated to) additional 
languages!)

♥ HTML means your not uploading a lot of data, and users are not Downloading 
a lot of data. Bandwidth costs are then low! and Users are happy to have short 
DL times! :)

♥ Users would have reliable "accurate-to-their-build" access to the growing 
wealth of features wiiflow has, and will adopt in its future.

♥ The provision of Viewable, Editable, re-down-load-able Hypertext, with, or 
without PNG support, could allow future mods//patches//plugins//themes to all 
have a way to communicate to the User. Or provide written tutorials for 
complicated procedures.

♥ Hypertext inclusion is not too difficult any more, due to the frequency of 
open source applications that provide it. There are lib's available.  

♥ Put it this way,  Look what hypertext did for the internet? It wasn't just 
about downloads any more! ♥♥♥ :D

Lend your imagination to the possibility. Then consider weather the work to 
implement the feature is in your foreseeable future? ♥ 

WiiFlow is awesome! Hypertext is a pretty good next-step for a scalable future! 
*^-^*

~tbe
Original issue reported on code.google.com by ThumpieB...@gmail.com on 3 May 2011 at 10:35
mightymouse2016 / wiiflow

WiiFlow Hypertext Interface Guide? #494
