TVs, Helptext and user experience

Though revo brought many usability improvements, I’m still missing an important feature: Helptexts

Especially for TVs they can give end users valuable advice on how to properly use a TV. Though there is form customization, I think this is a bit overpowered for most cases.

Here are my ideas for a better user experience:

1: Allow html markup

It would be nice to have the opportunity to add html markup to TV captions and descriptions.

Right now all html markup is automatically removed. Therefor it is impossible to add a strong tag to a word or to add a link to a help page for a specific TV.

This is an Extjs related thing. From my point of of view there is now reason why it should act like that.

2: Allow modx syntax

I would be much better if MODx tags could also be used, so I cold create a document inside modx describing the TV and its use.

MyTVname <a href="[[~999]] title="Read the manual" target=_blank"> ? </a>

3: Use ExtJs to open links within a caption inside a lightbox

I would go crazy, if ExtJS would open that helptext inside a ligtbox...

4: Perfect solution
Alternative appriach: Add a new field to all TVs: "Help url". It can contain a simple link or a MODx link [999]]. If used, EXTjs will add a link to the captiontext of this TV that opens a helptext inside a lightbox.

I have submitted a ticket: http://bugs.modx.com/issues/5534
No, this is not a bug. Can somebody change that from "Bug" to "Feature Request" or whatever fits to this topic. I would also like to remove all those ugly typos, but I can’t...

Please support this request with your personal oppinion and ideas.

Regards,


pepebe

1:
HTML isn’t filtered from the caption. The <strong> tag is, for whatever reason, being set to font-weight: normal in the ExtJS CSS but you can use:

or

and probably anything else, too!

It’d be good to find out why ExtJS sets the strong tag to a normal font-weight. And perhaps a longer limit for the caption - when using HTML you quickly use up the number of characters you can use...

The description does seem to filter out the html before it hits the update screen, and I support your request to not do that there.

2:
I’m not sure if I would use this.. resources are supposed to be front-end and this would be mixing up stuff..

3:
There is a javascript function MODx.loadHelpPane that opens the page linked to with the MODx.config.help_url variable... a custom JS function could abuse that.

4:
Guess that combines all the above...


Do you really write a help document for every TV? Typically I don’t even set a description as it’s just so self explanatory and the client will get a short training in which everything is connected anyway.. If a TV is too hard to understand I’d say something went wrong during development