Author Topic: new plugin: help_ui (beta version) (Read 12964 times)

corbosman · « **on:** July 14, 2010, 08:26:09 AM »

I have made a new plugin named help_ui that can be useful in some specific situations where you may have users on your system that dont understand roundcube very well. It adds a link to the messagelist footer, and if you click it starts an overlay which allows you to give help information about UI elements.

This is a BETA version. I am just releasing it to get feedback and bug reports. I would especially like english text modifications as im not native english and im sure my text sucks

You can download the beta version here: http://wa.ter.net/download/help_ui.tgz

ABerglund · « **Reply #1 on:** July 14, 2010, 07:03:19 PM »

Great beginning. Doesn't exit via ESC in Safari 5 on Mac. Have to reload the page to exit. Works fine in Firefox on both platforms.

English text is pretty good, but when you get it ready let me know and I can help with cleaning it up just a bit.

EDIT - IE8 in Win7 is bad - whole screen goes blue...

corbosman · « **Reply #2 on:** July 15, 2010, 03:49:57 AM »

Thanks, i'll work on those issues. I know why ESC doesnt work, thats easy to fix.

Otherwise, looks useful? Im more than happy to hear feedback on other issues, like overlay colors. The red seemed to be the most visible. I cant do anything that would add pixels, like borders or whatever.

How it works is, i use the config file to find UI elements on the page, then create divs the exact same size as those UI elements. I give those divs a bg color, and an opacity so you can see the original element. Finally I overlay a div over the whole screen with a click handler so you cant click on any elements.

corbosman · « **Reply #3 on:** July 15, 2010, 05:48:32 AM »

I have a new version online here: Downloads - roundcube-plugins - Project Hosting on Google Code

This fixes the problems you've mentioned so far.

ABerglund · « **Reply #4 on:** July 15, 2010, 11:09:47 AM »

Good, works as it should in the various test environments I have easy access to.

Any chance of expanding this to the compose and addressbook windows?

corbosman · « **Reply #5 on:** July 15, 2010, 11:12:45 AM »

The problem is, where do I put the overlay activation link? It needs to be consistent across all pages. A taskbar icon seems so... overdone

And I think the RC dev team doesnt like it if you use taskbar icons. That space is very limited.

ABerglund · « **Reply #6 on:** July 15, 2010, 11:17:41 AM »

Yeah, that's a problem all right. I'll ask my UI people for suggestions and pass along anything that sounds useful.

SKaero · « **Reply #7 on:** July 15, 2010, 03:29:30 PM »

How about a triangle in one of the top corners with a question mark, sill seems a little overdone but may look good.

corbosman · « **Reply #8 on:** July 16, 2010, 04:44:25 AM »

I think this may actually be a problem for RC as a whole. If people want to create plugins that have a presence across all page, how do you do that? The only spot right now thats consistent is the task bar.

SKaero · « **Reply #9 on:** July 16, 2010, 10:32:06 PM »

I agree but more or less a its a problem of space, there isn't a real area you could add more buttons without some sort of drop down.

jeffshead · « **Reply #10 on:** July 28, 2010, 03:04:23 AM »

I can't get 0.4-beta (downloaded from front page) to work in IE8.

The toolbar icons (checkmail, compose, etc.) get highlighted but the buttons remain clickable and no tool tip displays on hover.

All other elements seem to work. Just a problem with the toolbar buttons.

I do not encounter this issue with FF, Safari or Opera.

lacri · « **Reply #11 on:** July 28, 2010, 08:49:05 AM »

great plugin, i have fix some little issues and add german language diff is attached.

some little changes in other plugins included to show help for this.

many thx for this great work.

rosali · « **Reply #12 on:** July 28, 2010, 11:28:08 AM »

lacri,

wouldn't it be better to add plugins support to the plugin config?

lacri · « **Reply #13 on:** July 29, 2010, 03:32:18 AM »

hmm i think the best solution is a standards for buttons unique id or class and when class or id is not set is a real solution thats the plugin api the plugin name set as class or id.

corbosman · « **Reply #14 on:** July 29, 2010, 03:56:37 AM »

Thanks for the translation Lacri. I'll try and spend more time on this and other plugins soon. Am a little busy with work.

Rosali, I think what lacri is doing with those plugin patches is make them identifyable to the help_ui plugin. Some UI elements dont have any id or class.