Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIQuick-edit improvementQuick-edit improvement
Previous
 
Next
New Post
5/2/2007 7:02 AM
 

Hi Jon,

I've just spent a few hours building dozens of pages up from scratch with up to a dozen modules per page, mostly Text/HTML. I'm mainly using IE7 and this is DNN 4.51.

There was some hassle with the quick-edit mode:

First, when entering quick-edit mode to edit  the module title, the cursor would often not appear until the mouse was moved. Making changes to the text in the title would then also not be visible until the mouse cursor was moved a little. I had noticed this previously, but it really became apparent when I had to edit hundreds of titles. It also seems to happen in the main text area when that is edited inthe same manner. Sometimes it acts like it's not working.. going in and out of the mode or refreshing the page can fix it.

I also have a suggestion for improving the usability of quick-edit mode. On most of my sites there are two problems with the quick-edit icon/s. First, more often then not, they popup nearly on top of each other and at the same time are in the way of the module-menu. This makes it difficult to find the right one to click on.

And second, on pages with lots of text modules, when using the mouse to edit, the icons popup all over the place and hang around being a pain, making for a messy screen... and then it's less easy to find the one that is wanted. It's like you move the mouse over the screen towards a text area and by the time you get there 20 little icons have popped up all over the screen.

In addition, the module's own menu is also often entwined with all these little icons and it makes a right mess. I have to click away from the browser and wait until they have all vanished, before I then carefully line up the target for another run at it.

I believe that the solution to this would be to provide a delayed activation for all of these menus. If it required a short pause with the mouse on a menu before it pops up, then it would not happen at all when the mouse is moved across the screen.

This is how the Windows Start menu works and remains relatively smooth... by having about half a second delay before any submenu opens.

I think it's worth trying out in any case.

Rob

 
New Post
5/5/2007 9:02 PM
 

ok.. I've had a play around in dnn.controls.dnntoolbar.js to see if I could make it work better, but I can see that it might not be so easy.

I had originally thought that the icon was staying there with some sort of mouseover thing where it would not go into the exit cycle until the mouse left the area or the exit buttons were clicked. Instead, the icon only pops up when the mouse is moved over the area. Then when the mouse stops, the icon goes straight into the exit cycle where it waits a specified period and vanishes. This means that the icon is only really there when the mouse is moving or it is held by the exit-delay.

When I set a shorter exit delay, it is harder to reach the button before they vanish.

Even so.. is there a place I could insert a pre-delay into this? I would still like to test it out as I'm pretty sure that it would reduce clutter in the situation I described.

I also mentioned a situation where the cursor and edited text remained invisible until the mouse was moved.. that makes sense to me now that I see how it works. In certain situations, something is causing a slow-down of the script and changes are not made visible until it catches up.

Not sure how to fix that up.

 
New Post
5/7/2007 1:19 PM
 

I wanted to get a quick post out to say that I am not ignoring you.  I am trying to set aside some time to review your thoughts.
All I can say at the moment is that a considerable amount of thought and discussion went into the current implementation with the delay of the toolbar hiding.


 
New Post
5/15/2007 10:13 PM
 

Hi Jon, I Appreciate the reply.

The issue I had brought up was in regard to having many text modules on a single page and that having possibly dozens of edit icons popping up and staying there was highly confusing to the user. I find that one particular skin I have seems to cause the toolbar script to slow down and cause this. I also find that using a slow computer causes the same issue. It is not a problem on a fast computer and on my other skins.

I do however have one suggestion. Would it be possible to split the popup code between the icons and the toolbar so that they can be timed to vanish differently? It is fine that the edit icons come and go quickly, but I really don't see any particular benefit in the way the toolbar keeps vanishing during editing... I'm finding it's more of a hassle.

It's not as if it hides anything being edited, it also does not provide a better wysiwyg view of the page when it vanishes, but it does mean one has to keep waving the mouse around to make it come back. I'd be keen on a setting to make the toolbar remain visible until the edit mode is exited.

Ideally the icons would delay and vanish at about 500ms and the toolbar either remain until closed or if it has to vanish, then delay for a much longer period.

Regards,

Rob

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIQuick-edit improvementQuick-edit improvement


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out