[0.8] Context menu

[Philippe Poulard]

Hi folks,

I set a context menu to some widget.
I expect that on a right click event the menu appears, and it does, but
the browser's context menu appeared on top of it !

I have registered a listener and tried various actions on the mouse event:
-e.preventDefault();
-e.stopPropagation();

But it still doesn't work :(
Did I miss anything ?

Moreover, when setting the context menu property on a widget, it would
be kind to disable systematically the browser's behaviour.
If it is not very reliable (due to lack of interoperability of
browsers), perhaps it would be relevant to display the user-defined
context menu at another place, so that the browser one won't overlap it.

Thanks for your help.

--
Cordialement,

               ///
              (. .)
  --------ooO--(_)--Ooo--------
|      Philippe Poulard       |
  -----------------------------
  http://reflex.gforge.inria.fr/
        Have the RefleX !

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Derrell Lipman]

On Mon, Sep 22, 2008 at 7:20 AM, Philippe Poulard <philippe.poulard@...> wrote:

Hi folks,

I set a context menu to some widget.
I expect that on a right click event the menu appears, and it does, but
the browser's context menu appeared on top of it !

I have registered a listener and tried various actions on the mouse event:
-e.preventDefault();
-e.stopPropagation();

But it still doesn't work :(
Did I miss anything ?

Yup.  You're probably using Firefox.  The browser can choose to disallow blocking the default menu, but you can override that.  See here:
http://qooxdoo.org/documentation/0.6/user_manual/faq?s=context%20menu%20firefox#how_to_hide_the_browsers_context_menu

Derrell

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Philippe Poulard]

Derrell Lipman a écrit :

> On Mon, Sep 22, 2008 at 7:20 AM, Philippe Poulard
> <philippe.poulard@...
> <mailto:philippe.poulard@...>> wrote:
>
>     Hi folks,
>
>     I set a context menu to some widget.
>     I expect that on a right click event the menu appears, and it does, but
>     the browser's context menu appeared on top of it !
>
>     I have registered a listener and tried various actions on the mouse
>     event:
>     -e.preventDefault();
>     -e.stopPropagation();
>
>     But it still doesn't work :(
>     Did I miss anything ?
>
>
> Yup.  You're probably using Firefox.

Yes

  The browser can choose to disallow
> blocking the default menu, but you can override that.  See here:
> http://qooxdoo.org/documentation/0.6/user_manual/faq?s=context%20menu%20firefox#how_to_hide_the_browsers_context_menu

Not so user-friendly :(
Of course I can deal with that configuration, but for end users I would
prefer that the context menu be displayed at a different location, few
pixels on the left for example

Is it preferable to avoid using context menus ?

--
Cordialement,

               ///
              (. .)
  --------ooO--(_)--Ooo--------
|      Philippe Poulard       |
  -----------------------------
  http://reflex.gforge.inria.fr/
        Have the RefleX !

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Derrell Lipman]

On Mon, Sep 22, 2008 at 10:46 AM, Philippe Poulard <philippe.poulard@...> wrote:

Derrell Lipman a écrit :

> On Mon, Sep 22, 2008 at 7:20 AM, Philippe Poulard
> <philippe.poulard@...

> <mailto:philippe.poulard@...>> wrote:
>
>     Hi folks,
>
>     I set a context menu to some widget.
>     I expect that on a right click event the menu appears, and it does, but
>     the browser's context menu appeared on top of it !
>
>     I have registered a listener and tried various actions on the mouse
>     event:
>     -e.preventDefault();
>     -e.stopPropagation();
>
>     But it still doesn't work :(
>     Did I miss anything ?
>
>
> Yup.  You're probably using Firefox.

Yes

 The browser can choose to disallow
> blocking the default menu, but you can override that.  See here:
> http://qooxdoo.org/documentation/0.6/user_manual/faq?s=context%20menu%20firefox#how_to_hide_the_browsers_context_menu

Not so user-friendly :(

I agree.

Of course I can deal with that configuration, but for end users I would
prefer that the context menu be displayed at a different location, few
pixels on the left for example

The location where context menus appear is fairly consistent.  I think it would look strange to users if they popped up in some unusual location.  Furthermore, I think it would be particularly confusing for users if *two* context menus appeared in different locations.  That never happens "in real life".

Is it preferable to avoid using context menus ?

I suppose that's one solution.  My solution is to allow everything to be done without context menus, but to allow their use as well.  I use cell editors in tables which bring up modal windows for editing, but I also provide context menus for quick changes.  Those users who like context menus probably already have that Firefox mis-feature disabled, and if they don't, when they get both the application context menu and the browser's, they'll go looking for how to prevent that.  Certainly the product manual can describe how to disable the mis-feature, but how many customers read manuals?  There is, unfortunately, no good solution that I know of.

Derrell

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Philippe Poulard]

Derrell Lipman a écrit :

> On Mon, Sep 22, 2008 at 10:46 AM, Philippe Poulard
> <philippe.poulard@...
> <mailto:philippe.poulard@...>> wrote:
>
>     Derrell Lipman a écrit :
>      > On Mon, Sep 22, 2008 at 7:20 AM, Philippe Poulard
>      > <philippe.poulard@...
>     <mailto:philippe.poulard@...>
>      > <mailto:philippe.poulard@...
>     <mailto:philippe.poulard@...>>> wrote:
>      >
>      >     Hi folks,
>      >
>      >     I set a context menu to some widget.
>      >     I expect that on a right click event the menu appears, and it
>     does, but
>      >     the browser's context menu appeared on top of it !
>      >
>      >     I have registered a listener and tried various actions on the
>     mouse
>      >     event:
>      >     -e.preventDefault();
>      >     -e.stopPropagation();
>      >
>      >     But it still doesn't work :(
>      >     Did I miss anything ?
>      >
>      >
>      > Yup.  You're probably using Firefox.
>
>     Yes
>
>      The browser can choose to disallow
>      > blocking the default menu, but you can override that.  See here:
>      >
>     http://qooxdoo.org/documentation/0.6/user_manual/faq?s=context%20menu%20firefox#how_to_hide_the_browsers_context_menu
>
>     Not so user-friendly :(
>
>
> I agree.
>
>
>     Of course I can deal with that configuration, but for end users I would
>     prefer that the context menu be displayed at a different location, few
>     pixels on the left for example
>
>
> The location where context menus appear is fairly consistent.  I think
> it would look strange to users if they popped up in some unusual
> location.  Furthermore, I think it would be particularly confusing for
> users if *two* context menus appeared in different locations.  That
> never happens "in real life".
>
>     Is it preferable to avoid using context menus ?
>
>
> I suppose that's one solution.  My solution is to allow everything to be
> done without context menus, but to allow their use as well.  I use cell
> editors in tables which bring up modal windows for editing, but I also
> provide context menus for quick changes.  Those users who like context
> menus probably already have that Firefox mis-feature disabled, and if
> they don't, when they get both the application context menu and the
> browser's, they'll go looking for how to prevent that.  Certainly the
> product manual can describe how to disable the mis-feature, but how many
> customers read manuals?  There is, unfortunately, no good solution that
> I know of.

Are you aware of some js magic (for firefox) that indicates whether or
not context menus can be blocked or not ? it would be possible to use
them if they can be blocked, and to fallback to another mean if they are
not.

Another strategy is to use variant and use systematically the fallback
behaviour with firefox.

Thanks for your comments, Derrell ;)

--
Cordialement,

               ///
              (. .)
  --------ooO--(_)--Ooo--------
|      Philippe Poulard       |
  -----------------------------
  http://reflex.gforge.inria.fr/
        Have the RefleX !

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Derrell Lipman]

On Mon, Sep 22, 2008 at 11:07 AM, Philippe Poulard <philippe.poulard@...> wrote:

Are you aware of some js magic (for firefox) that indicates whether or
not context menus can be blocked or not ? it would be possible to use
them if they can be blocked, and to fallback to another mean if they are
not.

If I were to play with trying to find that magic, I'd see if it's possible to request about:config programmatically and get back useful data.  I suspect that the saved value of that mis-feature is someplace in there, so if you could retrieve that data, you'd be able to determine how it's set.  I have no idea whether what I propose here is possible.

Another strategy is to use variant and use systematically the fallback
behaviour with firefox.

Yuck.  That would mean that those users who really like context menus wouldn't have them available. I guess the question is who would grumble the loudest: the not-so-sophisticated user who gets two context menus, or the sophisticated user who can't use his context menu only when using firefox.  I suspect (but it requires testing with focus groups or something if you have such an option) is that the not-so-sophisticated user wouldn't even try to use a context menu unless you told them to, and if you told them to, you could also tell them how to fix firefox.

Derrell

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Alexander Back]

Hi Phillipe,

for your information: the default behaviour of Firefox (at least version
3) is to let the application take control of the contextmenu. So
preventing the native contextmenu from appearing and showing the own
application context menu should work for most people as they stick with
the default configuration.

See http://kb.mozillazine.org/About:config_entries#DOM..2A at "dom.
event. contextmenu.enabled" for more information.

cheers,
   Alex

Philippe Poulard wrote:

> Hi folks,
>
> I set a context menu to some widget.
> I expect that on a right click event the menu appears, and it does, but
> the browser's context menu appeared on top of it !
>
> I have registered a listener and tried various actions on the mouse event:
> -e.preventDefault();
> -e.stopPropagation();
>
> But it still doesn't work :(
> Did I miss anything ?
>
> Moreover, when setting the context menu property on a widget, it would
> be kind to disable systematically the browser's behaviour.
> If it is not very reliable (due to lack of interoperability of
> browsers), perhaps it would be relevant to display the user-defined
> context menu at another place, so that the browser one won't overlap it.
>
> Thanks for your help.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Philippe Poulard]

Alexander Back a écrit :

> Hi Phillipe,
>
> for your information: the default behaviour of Firefox (at least version
> 3) is to let the application take control of the contextmenu. So
> preventing the native contextmenu from appearing and showing the own
> application context menu should work for most people as they stick with
> the default configuration.
>
> See http://kb.mozillazine.org/About:config_entries#DOM..2A at "dom.
> event. contextmenu.enabled" for more information.

Thanks.

That confirms in addition to my dicussion with Derrell that it is better
to let things as they are, since users of Firefox 2 can enable context
menus.

--
Cordialement,

               ///
              (. .)
  --------ooO--(_)--Ooo--------
|      Philippe Poulard       |
  -----------------------------
  http://reflex.gforge.inria.fr/
        Have the RefleX !

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Ian Horst]

I use "CTRL + MOUSE LEFT CLICK" as alternative for mouse right click for contextmenu.

I'm still looking for better solution.

Ian Horst


Philippe Poulard wrote:

> Alexander Back a écrit :
>> Hi Phillipe,
>>
>> for your information: the default behaviour of Firefox (at least version
>> 3) is to let the application take control of the contextmenu. So
>> preventing the native contextmenu from appearing and showing the own
>> application context menu should work for most people as they stick with
>> the default configuration.
>>
>> See http://kb.mozillazine.org/About:config_entries#DOM..2A at "dom.
>> event. contextmenu.enabled" for more information.
>
> Thanks.
>
> That confirms in addition to my dicussion with Derrell that it is better
> to let things as they are, since users of Firefox 2 can enable context
> menus.
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Philippe Poulard]

Ian Horst a écrit :
> I use "CTRL + MOUSE LEFT CLICK" as alternative for mouse right click for contextmenu.

Good suggestion.
Thanks !

>
> I'm still looking for better solution.
>
> Ian Horst
>

--
Cordialement,

               ///
              (. .)
  --------ooO--(_)--Ooo--------
|      Philippe Poulard       |
  -----------------------------
  http://reflex.gforge.inria.fr/
        Have the RefleX !

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Ian Horst]

You would still have not so good usability in cases when you have to make multiple selection (tables, etc). You would get context menu on each selection.

I would prefer not to have keyboard + mouse solution for contextmenu.


I have thought of other alternatives for contextmenu like:

1) tripple click
* it would mean qooxdoo developers would be assigned to do it :). not sure about implications;

2) mouse left click, small icon appears nearby informing end user that contextmenu is available, if end user clicks on contextmenu icon, contextmenu appears. If end user doesn't click on it, contextmenu icon just disappears in 2-5 seconds.
* "maybe annoying, maybe not icon" on each mouse left click

To me tripple click looks really good. However I plan to implement contextmenu icon in my application this week.

Ian Horst


Philippe Poulard wrote:

> Ian Horst a �crit :
>> I use "CTRL + MOUSE LEFT CLICK" as alternative for mouse right click for contextmenu.
>
> Good suggestion.
> Thanks !
>
>> I'm still looking for better solution.
>>
>> Ian Horst
>>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Ian Horst]

I made a spike solution for alternative action for contextmenu. Look at the attachment.

I don't want keyboard to be involved.

On mouse left click, it shows contextmenu icon for short time (200ms seems fine for me), then disappears. When you move mouse over, contextmenu appears.

Any comments, suggestions and ideas are welcome.

Ian Horst


Philippe Poulard wrote:

> Ian Horst a �crit :
>> I use "CTRL + MOUSE LEFT CLICK" as alternative for mouse right click for contextmenu.
>
> Good suggestion.
> Thanks !
>
>> I'm still looking for better solution.
>>
>> Ian Horst
>>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Ian Horst]

I made a spike solution for alternative action for contextmenu. Look at the attachment.

I don't want keyboard to be involved.

On mouse left click, it shows contextmenu icon for short time (200ms seems fine for me), then disappears. When you move mouse over, contextmenu appears.

Any comments, suggestions and ideas are welcome.

Ian Horst


Philippe Poulard wrote:

> Ian Horst a �crit :
>> I use "CTRL + MOUSE LEFT CLICK" as alternative for mouse right click for contextmenu.
>
> Good suggestion.
> Thanks !
>
>> I'm still looking for better solution.
>>
>> Ian Horst
>>
>

/* ************************************************************************

   Copyright:

   License:

   Authors:

************************************************************************ */

/* ************************************************************************

#asset(qtest3/*)

************************************************************************ */

/**
 * This is the main application class of your custom application "qtest3"
 */
qx.Class.define("qtest3.Application",
{
  extend : qx.application.Standalone,



  /*
  *****************************************************************************
     MEMBERS
  *****************************************************************************
  */

  members :
  {
    /**
     * This method contains the initial application code and gets called
     * during startup of the application
     */
    main : function()
    {
      // Call super class
      this.base(arguments);

      // Enable logging in debug variant
      if (qx.core.Variant.isSet("qx.debug", "on"))
      {
        // support native logging capabilities, e.g. Firebug for Firefox
        qx.log.appender.Native;
        // support additional cross-browser console. Press F7 to toggle visibility
        qx.log.appender.Console;
      }
               
               
                var root = this.getRoot();
               
                var menu = new qx.ui.menu.Menu;
               
                for (var i = 0; i < 5; i++)
                        menu.add(new qx.ui.menu.Button(new String(i)));
                root.add(menu);
               
               
                var menuIcon = new qx.ui.popup.Popup(new qx.ui.layout.Grow);
                menuIcon.add(new qx.ui.basic.Atom("M"));
                var hideIcon = function (e)
                {
                        qx.event.Timer.once(menuIcon.hide, menuIcon, 200);
                }
                menuIcon.addListener("appear", hideIcon);
               
                var showMenu = function (e)
                {
                        menu.placeToWidget(menuIcon);
                        menuIcon.hide();
                        menu.show();
                }
                menuIcon.addListener("mouseover", showMenu);
               
                var alternative2 = function (e)
                {
                        menuIcon.moveTo(e.getDocumentLeft()+5, e.getDocumentTop()-5);
                        menuIcon.show();
                }
               
                var container = new qx.ui.container.Composite(new qx.ui.layout.HBox);

                var layer2 = new qx.ui.basic.Atom("Alternate contextmenu");
                layer2.setWidth(200);
                layer2.setHeight(200);
                layer2.setBackgroundColor("white");
                layer2.setContextMenu(menu);
                layer2.addListener("click", alternative2);
                container.add(layer2);
               
                root.add(container);
               
    }
  }
});

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Jean-Baptiste BRIAUD -- Novlog]

Why not using the same convention as some mobile OS : a long left  
click will be interpreted as right click.
In summary :
* short left click : just plain old click
* right click : plain old right click : show the browser menu
* long left click : show the qooXdoo contextual menu

What do you think about that ?
On 8 Oct 2008, at 14:43, Ian Horst wrote:

> I made a spike solution for alternative action for contextmenu. Look  
> at the attachment.
>
> I don't want keyboard to be involved.
>
> On mouse left click, it shows contextmenu icon for short time (200ms  
> seems fine for me), then disappears. When you move mouse over,  
> contextmenu appears.
>
> Any comments, suggestions and ideas are welcome.
>
> Ian Horst
>
>
> Philippe Poulard wrote:
>> Ian Horst a �crit :
>>> I use "CTRL + MOUSE LEFT CLICK" as alternative for mouse right  
>>> click for contextmenu.
>>
>> Good suggestion.
>> Thanks !
>>
>>> I'm still looking for better solution.
>>>
>>> Ian Horst
>>>
>>
> /*  
> ************************************************************************
>
>   Copyright:
>
>   License:
>
>   Authors:
>
> ************************************************************************ */
>
> /*  
> ************************************************************************
>
> #asset(qtest3/*)
>
> ************************************************************************ */
>
> /**
> * This is the main application class of your custom application  
> "qtest3"
> */
> qx.Class.define("qtest3.Application",
> {
>  extend : qx.application.Standalone,
>
>
>
>  /*
>  
> *****************************************************************************
>     MEMBERS
>  
> *****************************************************************************
>  */
>
>  members :
>  {
>    /**
>     * This method contains the initial application code and gets  
> called
>     * during startup of the application
>     */
>    main : function()
>    {
>      // Call super class
>      this.base(arguments);
>
>      // Enable logging in debug variant
>      if (qx.core.Variant.isSet("qx.debug", "on"))
>      {
>        // support native logging capabilities, e.g. Firebug for  
> Firefox
>        qx.log.appender.Native;
>        // support additional cross-browser console. Press F7 to  
> toggle visibility
>        qx.log.appender.Console;
>      }
>
>
> var root = this.getRoot();
>
> var menu = new qx.ui.menu.Menu;
>
> for (var i = 0; i < 5; i++)
> menu.add(new qx.ui.menu.Button(new String(i)));
> root.add(menu);
>
>
> var menuIcon = new qx.ui.popup.Popup(new qx.ui.layout.Grow);
> menuIcon.add(new qx.ui.basic.Atom("M"));
> var hideIcon = function (e)
> {
> qx.event.Timer.once(menuIcon.hide, menuIcon, 200);
> }
> menuIcon.addListener("appear", hideIcon);
>
> var showMenu = function (e)
> {
> menu.placeToWidget(menuIcon);
> menuIcon.hide();
> menu.show();
> }
> menuIcon.addListener("mouseover", showMenu);
>
> var alternative2 = function (e)
> {
> menuIcon.moveTo(e.getDocumentLeft()+5, e.getDocumentTop()-5);
> menuIcon.show();
> }
>
> var container = new qx.ui.container.Composite(new  
> qx.ui.layout.HBox);
>
> var layer2 = new qx.ui.basic.Atom("Alternate contextmenu");
> layer2.setWidth(200);
> layer2.setHeight(200);
> layer2.setBackgroundColor("white");
> layer2.setContextMenu(menu);
> layer2.addListener("click", alternative2);
> container.add(layer2);
>
> root.add(container);
>
>    }
>  }
> });
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Ian Horst]

I like this idea. Proven and known solution. It's brilliant.

What qooxdoo developers think about it? I think it's worth consider this to be implemented in qooxdoo. No mess anymore with alternatives for contextmenu.

Long time (few months) passed since I used my handheld last time and I used it only for phone calls.

P.S. I implemented spike solution in my application. I use it more than mouse right click now. :)


Ian Horst


Jean-Baptiste BRIAUD -- Novlog wrote:

> Why not using the same convention as some mobile OS : a long left  
> click will be interpreted as right click.
> In summary :
> * short left click : just plain old click
> * right click : plain old right click : show the browser menu
> * long left click : show the qooXdoo contextual menu
>
> What do you think about that ?
> On 8 Oct 2008, at 14:43, Ian Horst wrote:
>
>> I made a spike solution for alternative action for contextmenu. Look  
>> at the attachment.
>>
>> I don't want keyboard to be involved.
>>
>> On mouse left click, it shows contextmenu icon for short time (200ms  
>> seems fine for me), then