[Bug 207064] Re: LiveConnect/javascript not yet implemented in icedtea-gcjwebplugin
When running an applet that uses live connect the class netscape/javascript/JSObject is not found. This has been tested using the 64-bit version of Firefox in Ubuntu 8.04 beta. The following is written to standard out as soon as the applet attempts to use live connect: java.lang.NoClassDefFoundError: netscape/javascript/JSObject GCJ PLUGIN: thread 0x622950: plugin_in_pipe_callback GCJ PLUGIN: thread 0x622950: plugin_in_pipe_callback: setting status error: netscape/javascript/JSObject. at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406) at java.lang.Class.getConstructor0(Class.java:2716) at java.lang.Class.newInstance0(Class.java:343) at java.lang.Class.newInstance(Class.java:325) at sun.applet.AppletPanel.createApplet(AppletPanel.java:796) at sun.applet.AppletPanel.runLoader(AppletPanel.java:725) at sun.applet.AppletPanel.run(AppletPanel.java:379) at java.lang.Thread.run(Thread.java:636) PIPE: plugin read: status error: netscape/javascript/JSObject. Caused by: java.lang.ClassNotFoundException: netscape.javascript.JSObject GCJ PLUGIN: thread 0x622950: plugin_in_pipe_callback return at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:201) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at sun.applet.AppletClassLoader.loadClass(AppletClassLoader.java:145) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336) ... 9 more Caused by: java.io.IOException: open HTTP connection failed. at sun.applet.AppletClassLoader.getBytes(AppletClassLoader.java:304) at sun.applet.AppletClassLoader.access$100(AppletClassLoader.java:62) at sun.applet.AppletClassLoader$1.run(AppletClassLoader.java:191) at java.security.AccessController.doPrivileged(Native Method) at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:188) ... 13 more -- LiveConnect/javascript not yet implemented in icedtea-gcjwebplugin https://bugs.launchpad.net/bugs/207064 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177514] Re: firefox 64-bit IcedTea java not working.
The icedtea-gcjwebplugin seems to still be missing some components, I'm getting the following error: java.lang.NoClassDefFoundError: netscape/javascript/JSObject Is there something else that should be added for live connect? -- firefox 64-bit IcedTea java not working. https://bugs.launchpad.net/bugs/177514 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87947] Re: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
We are experiencing the same issue as we prepare for our migration to Hardy. Java 5/6 is a requirement for us so I'm anxious to see a resolution to this. Are you saying that the same work-around used in Gutsy for Java 5/6 will be available in Hardy? Or are you saying if someone makes the fixes to libx11 you will be happy to include them? I just want to make sure I understand and try to see if there is a way to help move the process along. -- xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://bugs.launchpad.net/bugs/87947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527458] Re: please include status messages/tooltips
There is a difference here. Removing icons from menus is more of an aesthetic change, removing tooltips removes functionality that users depend on. I'm crossing my fingers hoping it won't be long until the tooltips are restored. -- please include status messages/tooltips https://bugs.launchpad.net/bugs/527458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527458] Re: please include status messages/tooltips
Tooltips do not take input focus away from your current work flow, clicking the application icon does. For example, I can leave the tooltip up monitoring information the entire time I write this response. The only time tooltips aren't the best approach is for mobile devices where the mouse is replaced by touching and there is no "hover" equivalent. I'm afraid that the motivation for this change may be a misguided effort to sacrifice desktop capabilities in hopes of a unified approach for mobile devices. A simple fix to satisfy everyone is to allow applications to register an information/status panel and have the GUI show it according to user preferences. The user then decides if the information/status panel shows in the top part of the menu or as a tooltip. This creates no extra application development effort since only one object is being created and managed and it gives users the information in the manner they most prefer. Does that not sound like a win/win? -- please include status messages/tooltips https://bugs.launchpad.net/bugs/527458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527458] Re: please include status messages/tooltips
As some have mentioned, knowing what an icon in the panel is does not require a tooltip. However, that isn't always true. The icon may sometimes make it clear what the application is, however, there are many cases where that isn't true. 1. I have 6 configurations of eclipse for different development configurations. These are non-trivial to set up, so having the quick- access buttons on my panel is awesome, but of course I need the tooltips to make sure I'm clicking the right one. 2. I have 3 servers I connect to regularly to do maintenance. So the maintenance application icon is repeated three times, the tooltips tell me which server it will connect me to. 3. I have both the remote desktop viewer and terminal server client on my panel. I never remember which is which, but lucky for me I have a tooltip that nicely pops up in a few seconds to help me remember. There are other examples, but the point is that the assumption that a "well designed icon is so obvious that a tooltip is redundant" is simply not valid. -- please include status messages/tooltips https://bugs.launchpad.net/bugs/527458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527458] Re: please include status messages/tooltips
The reason that many of us don't want to let this issue go is because all of the justifications to remove tooltips don't make up for the loss of functionality that can't be replaced. Hover based tooltips are a powerful model that play a much needed role in a pointer based UI: - they do not take input focus away from your current work as click operations do - they do not invoke any pop-up windows that need to be managed or closed by the user - they have no time limit and will stay open as long as the cursor is over the icon, even while you work in another window - they are safe and are not overloaded with an action that also runs things (like click). Hover adds a great deal of comfort for the user. Anything can be harmlessly examined without fear of making it do something. For new users this is especially important. Clicking on an icon to learn more about it will often run it, which is not what you want. Hover is the natural "what is this?" action. Why not simply manage tooltips better? Move their information around according to the type of system. Pointer based systems could use tooltips while touch based systems could have long-press pop-ups or menu captions. Let the user decide when to disable them, move them, even theme them. They are essentially information / status objects. Let's be creative about what an information / status object can do, where they can show and then "show as a tooltip" is simply one of the options. I think what is getting people worked up is that any software designer can see a number of solutions where we accomplish the "less is more" objective, address all tooltip concerns and encourage creativity without having to tell users who love tooltips to take a hike. As a result, the current decision is sort of a slap in the face. I'm not saying that Canonical doesn't have the right to do what they want with their distribution, I'm just questioning if it is the right thing to do. What is wrong with a win/win solution? -- please include status messages/tooltips https://bugs.launchpad.net/bugs/527458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527458] Re: please include status messages/tooltips
Dmitrijs, your screen shot is clearly a good example of badly tuned tooltips. On my system they do not cover the other indicator icons because I have them on the top panel and they are correctly set to pop-up below the panel. This way they do not block your ability to see any of the other indicators. Your case of having the indicators on the bottom panel should work just as well by default. Somehow that was overlooked by testers and left your bottom panel tooltips broken. Clearly that is a bug that should have been cleaned up prior to release. If the tooltips were tuned properly and popped up just above your bottom panel, nothing else in the panel would be covered by them and you'd find your entire list of issues to be resolved. So what you found is clearly a bug, but I have a hard time seeing why it's better to throw out the feature rather than just fix the bug. -- please include status messages/tooltips https://bugs.launchpad.net/bugs/527458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527458] Re: please include status messages/tooltips
We consider tooltips a core feature, they fill a unique role because they are never in your way and only pop-up if you hover, implying you want to see them. Information that is automatically there when you need it and never there when you don't is about as perfect as user interaction can get. The guidelines assume a vary narrow set of use cases. Consideration needs to be given to vertical applications that take full advantage of the framework allowing enterprise users enjoy a satisfying user experience. We are in the enterprise market, so our expectations go beyond a few simple social networking applications. There is a subset of on-demand information that must be extremely quick and easy to access, have minimal disruption on the work-flow, not have a time-out (you can leave them up as long or as short as you want) and be intuitive to get to. There is simply no better option than a tooltip. They fill a unique role that has no equivalent. They also do not clutter up the user interface or the menus, which the work-arounds would require. Is there any way that tooltips can remain available as a configuration option? I'd also like to request that core features not be removed just before an LTS. Experimentation is great and innovation is critical, but LTS is about stability based on what we've innovated so far. -- please include status messages/tooltips https://bugs.launchpad.net/bugs/527458 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
