Fly-Pie 10: A new Clipboard Menu, proper touch support & much more!

Have you tried Simon Schneegans awesome "Gnome Pie" application launcher, which lets you define your own pie menus? link Gnome Pie: link For his thesis, he also designed and implemented the elegant Coral Menu: link And the cool Trace Menu: link Simon Schneegans' Bachelor Thesis about Gnome Pie, the Coral Menu, and the Trace Menu: link Fly-Pie is his more recent wonderful work: link Fly-Pie 8: New default dark theme and support for GNOME 3.36, 3.38, 40, and 41! link Fly-Pie 10: A new Clipboard Menu, proper touch support & much more! ▶ this video >Fly-Pie is an attractive marking menu for GNOME Shell. Fly-Pie 10 brings improved touch support, a new clipboard menu and a bunch of other new features!

Simon's a top notch interactive graphical user interface designer and programmer. Not just static pictures, not just fixed animations, not just functional code, but rich interactive animated feedback that's actually useful and helps you complete your task while it's also beautiful. When you can design and program stuff like this all on your own and give it away for free, then you can make up any rules you want about commit messages. Look what else he can do with icons and emojis: link >More Fly-Pie Updates! >In the last couple of months several new versions of Fly-Pie have been released. In this post, I want to highlight the major new feature. >New features were added in version 8 and version 10. The versions 9 and 11 were released as well, but they contain bug fixes only. Here are two trailers to celebrate the respective releases: Fly-Pie 8: New default dark theme and support for GNOME 3.36, 3.38, 40, and 41! link Fly-Pie 10: A new Clipboard Menu, proper touch support & much more! ▶ this video

I love Simon's work and artistic sensibility! I posted this earlier about his amazing work with pie menus for Gnome. Here's done even more amazing pie menu stuff since then, including Fly-Pie -- why don't all web browsers and window managers support this yet??? This stuff is extremely useful, practical, easy to use, and deeply customizable, not just beautiful window dressing, eye candy, and fancy effects. More Fly-Pie Updates! link Fly-Pie 8: New default dark theme and support for GNOME 3.36, 3.38, 40, and 41! link Fly-Pie 10: A new Clipboard Menu, proper touch support & much more! ▶ this video Pie Menus: A 30 Year Retrospective link >Spectacular Example: Simon Schneegans’ Gnome-Pie, the slick application launcher for Linux >I can’t understate how much I like Simon Schneegans’ Gnome-Pie, as well as his bachelor thesis work on the Coral-Menu and the Trace-Menu. Not only is it all slick, beautiful, and elegantly animated, but it’s properly well designed in all the important ways that make it Fitts’s Law Friendly and easy to use, and totally deeply customizable by normal users! It’s a spectacularly useful tour-de-force that Linux desktop users can personalize to their heart’s content. link Pie Menus: A 30-Year Retrospective: Take a Look and Feel Free (medium.com/donhopkins) link DonHopkins on May 19, 2018 | parent | context | favorite | on: Pie Menus: A 30-Year Retrospective: Take a Look an... I'm very impressed by Simon Schneegans' work on Gnome-Pie: link And especially his delightful thesis work: Trace-Menu: link I really love how the little nubs preview the structure of the sub-menus, and how you can roll back to the parent menu because it reserves a slice in the sub-menu to go back, so you don't need to use another mouse button or shift key to browse the menus. Coral-Menu: link That looks like a nice visual representation with a way to easily browse all around the tree, into and out of the submenus without clicking! I can't tell from the video if it's based on a click or a timeout. But it looks like it supports browsing and reselection and correcting errors pretty well! (That would be something interesting to measure!) There's another useful law related to Fitts's law that applies to situations like this, called Steering Law: link The steering law in human–computer interaction and ergonomics is a predictive model of human movement that describes the time required to navigate, or steer, through a 2-dimensional tunnel. The tunnel can be thought of as a path or trajectory on a plane that has an associated thickness or width, where the width can vary along the tunnel. The goal of a steering task is to navigate from one end of the tunnel to the other as quickly as possible, without touching the boundaries of the tunnel. A real-world example that approximates this task is driving a car down a road that may have twists and turns, where the car must navigate the road as quickly as possible without touching the sides of the road. The steering law predicts both the instantaneous speed at which we may navigate the tunnel, and the total time required to navigate the entire tunnel. The steering law has been independently discovered and studied three times (Rashevsky, 1959; Drury, 1971; Accot and Zhai, 1997). Its most recent discovery has been within the human–computer interaction community, which has resulted in the most general mathematical formulation of the law. Also here's some interesting stuff about incompatibility with Wayland, and rewriting Gnome-Pie as an extension to the Gnome shell: link

Simon Schneegan's "Kandu" cross platform pie menus, as well as his older "Fly-Pie" and "Gnome-Pie" projects, let you create and edit your own pie menus with a WYSIWYG drag-and-drop direct manipulation interface. Kando: The Cross-Platform Pie Menu (github.com/kando-menu) link link A first glimpse at Kando's Menu Editor! link Development Update for Kando's Menu Editor! link Item labels in Fly-Pie! link Fly-Pie 10: A new Clipboard Menu, proper touch support & much more! ▶ this video Fly-Pie 7: GNOME Shell 40+ and a new WYSIWYG Menu Editor! link Gnome-Pie link Gnome-Pie 0.4 (12 years ago) link link

Agreed! ;) I know you're joking about "ONLY", but actually, linear drop-down menus are just an edge case of pie menus with multiple items in only one direction: down. So you can also make drop-down, -up, -left, -right, and other direction menus with a decent pie menu editor, like the Blender pie menu editor add-on. Pie menus are much more useful if users can edit and create their own, especially in feature-rich extensible configurable applications that different people use in different ways like Gimp and Blender. Blender has great pie menu support, and there's a nice pie menu editor add-on, but it really needs a built-in WYSIWYG pie menu editor, supporting on-the-fly direct manipulation WYSIWYG drag-and-drop pie menu editing, like Simon Schneegans's brilliant Gnome-Pie and Fly-Pie. By "direct manipulation WYSIWYG drag-and-drop" I mean that ideally you should be able to put any existing menu into edit mode on the fly, and edit the circular pie, linear, or hybrid layout directly by dragging items around to different slices, instead of with an indirect linear scrolling list or outline in a separate window. You need to be able directly and immediately edit them as they will appear to the user, not as some abstract linear tree outline (or god forbid, raw xml). Pie Menu Development for Blender: link Blender Pie Menu Editor: link Gnome-Pie (wikipedia): link Gnome-Pie (github): link Gnome-Pie 0.6.1: link Fly-Pie 7: GNOME Shell 40+ and a new WYSIWYG Menu Editor! link Fly-Pie 10: A new Clipboard Menu, proper touch support & much more! ▶ this video And Simon's new project, Kando: Kando - An Open Source, Cross-Platform Pie Menu: link Follow and support the project on Ko-Fi: link Kando on GitHub: link I also love the beautiful Trace and Coral menus he designed for his Bachelor thesis 11 years ago: link The Trace-Menu: link The Coral-Menu: link More of his great stuff: link A retrospective of my 35 years of work with pie menus: Pie Menus: A 30 Year Retrospective (2018): link >Steve Jobs Thought Pie Menus Sucked: “That sucks! That sucks! Wow, that’s neat! That sucks!” >On October 25, 1988, I gave Steve Jobs a demo of pie menus, NeWS, UniPress Emacs and HyperTIES at the Educom conference in Washington DC. His reaction was to jump up and down, point at the screen, and yell “That sucks! That sucks! Wow, that’s neat! That sucks!” >I tried explaining how we’d performed an experiment proving pie menus were faster than linear menus, but he insisted the liner menus in NeXT Step were the best possible menus ever. >But who was I to rain on his parade, two weeks after the first release of NeXT Step 0.8? (Up to that time, it was the most hyped piece of vaporware ever, and doubters were wearing t-shirts saying “NeVR Step”!) Even after he went back to Apple, Steve Jobs never took a bite of Apple Pie Menus, the forbidden fruit. There’s no accounting for taste! The ideas behind pie menus have actually been around for even longer than that, since at least 1969: Flight of the PIXIE - Yuja Wang: link >Dedication and Thanks to: Neil E. Wiseman, Heinz U. Lemke, John O. Hiles, PIXIE: A New Approach to Graphical Man-Machine Communication, Proceedings of 1969 CAD Conference Southampton IEEE Conference Publication 51, pp. 463–471. David Chapman, Cambridge University Library. Remixing and Synchronization with AfterEffects by Don Hopkins. >This film demons

I love your dedication to customizing your own environment! I'm frustrated that Wayland doesn't support all the good ideas (and avoid all the bad ideas) of X-Windows or NeWS, and doesn't even have a built-in extension language like emacs and web browsers do. (What were they even thinking, not making it extensible at runtime? That everybody would want to compile their own server to customize it in C? Or that they'd solved all possible problems perfectly and there would be no need for customization?) I always thought X window managers put the cart before the donkey: the client starts first, then the window manager reactivally wraps it in a generic frame. Instead, window managers should be more like HyperCard, where users can wysiwyg build and script their own stacks that frame and compose and integrate one or more clients together (or none, for fully server side stacks like the clock or drawing editor): the stacks come first, and they start up and pull in whatever clients they want to frame and integrate and even script. Of course you should just be able to run any client and it gets assigned a generic frame, but the user can edit both the generic frame prototype in the warehouse, edit and add scripts and message handlers, and customize any existing frame, including adding more pages (with tabs) and widgets and clients, and save them out to use later, restore all your windows after you reboot, add them to the warehouse, trade them with friends, etc. Users can easily customize and script their own window frames (stacks), and add or edit the look and feel of gui widgets like resize corners, buttons , tabs, and pie menus, and even high level components like drawing editors (great for property sheets that let you edit the graphics and colors and layouts of the gui, clock faces and hands, or graphics you can cut and paste between clients), so they can script and integrate together multiple clients to customize them for particular tasks and workflows. OpenDoc and CyberDog were barking up the right tree, but they didn't have a ubiquitous scripting language that you could use to both integrate and implement components. link link Sun's HotJava browser was also a step in the right direction, but it did not include a Java interpreter or the Java compiler written in Java (which was written by Arthur van Hoff who earlier wrote HyperLook for NeWS), so it didn't have runtime scripting like HyperCard had with HyperTalk. link Later at Marimba, Arthur implemented Bongo, which did include and invoke the Java compiler and dynamic linker at runtime, so you could interactively write and run scripts and message handlers. (IDEs do this all the time now, but it was unprecedented for Java at the time, and Arthur knew how to pull it off, because he'd written the compiler.) link link Danny Goodman, the guy who wrote the HyperCard manual, also wrote the book on Bongo: link At UMD I wrote an X10 window manager scriptable in FORTH (by linking in the C "uwm" X10 window manager that I'd implemented pie menus for, and rewriting its main loop in Mitch Bradley's Sun FORTH, so I could fling windows around and they would animate bouncing around the screen with FORTH tasks), and used it to perform and measure controlled experiments comparing pie and liner menus. link Hacks for flinging windows around with FORTH tasks: link Here's a similar hack in Lisp for the Lisp Machine window system using Flavors to define a pushy-bounce-window-mixin: link And at Sun we wrote an integ

How about taking another step back, and having a browser that functions as a scriptable user-customizable editable window manager like HyperCard? Run the web browser directly on the hardware, and implement the desktop window manager with that, in a way that the whole system is a scriptable integrated development environment. Then it's easy to implement tabbed windows, pie menus, and user-editable HyperCard-like interfaces. Here's a big step in the right direction of supporting pie menus on the desktop: Simon Schneegans's "Kando" project aims to implement cross-platform pie menus on the desktop. Simon implemented the beautiful "Pie Fly" Gnome shell extension and WYSIWYG pie menu editor, so I am really looking forward to what he does with other desktop interfaces! Introducing: Kando: link link >Kando will be a pie menu for the desktop. It will be highly customizable and will allow you to create your own menus and actions. For instance, you can use it to control your music player, to open your favorite websites or to simulate shortcuts. It will be available for Windows, Linux and maybe macOS. Fly-Pie: link >Fly-Pie is an extension for GNOME Shell which lets you open marking menus via keyboard shortcuts. And — to the best of my knowledge — it is the first GNOME Shell extension with achievements! >You can use it to launch applications, simulate hotkeys, open URLs and much more. It features a continuous learning curve which lets you gradually lift-off from a grumpie menu rookie to a snappie menu pielot. (You got it? Like pilot, but with a ). Once you opened a marking menu, you can seamlessly transition between three alternative selection modes: >Point-and-Click: Select items by clicking on them or anywhere in the corresponding wedges. >Marking-Mode: Select items by drawing gestures. To do this, click anywhere and drag your mouse. Pausing or making a turn selects the currently dragged item. >Turbo-Mode: You can also "draw" gestures while holding Ctrl, Shift, or Alt without having to press your mouse button! This is especially useful when you opened the menu with a shortcut involving such a modifier. Fly-Pie 7: GNOME Shell 40+ and a new WYSIWYG Menu Editor!: link Fly-Pie 10: A new Clipboard Menu, proper touch support & much more!: ▶ this video I've written about reinventing scriptable HyperCard-like window managers with pie menus and tabbed windows before: SimCity, Cellular Automata, and Happy Tool for HyperLook (nee HyperNeWS (nee GoodNeWS)): link link >At Sun we experimented with implementing an X11 window manager in NeWS. We didn't have transparency at the time (1992), but we did support shaped windows! >The NeWS window manager supported cool stuff (for both X11 and NeWS windows!) like rooms, virtual scrolling desktops, tabbed windows, pie menus, was easily extensible and deeply customisable in PostScript, and ran locally in the window server so it could respond instantly to input events, lock the input queue and provide feedback and manipulate windows immediately without causing any context switches or dealing with asynchronous locking, unlocking and event handling. You'd never lose a keystroke or click when switching between applications, for example. [...] And here's how I think you should design a programmable "window manager" these days -- but it would be much more than just a window manager! It would be great for integrating legacy desktop and mobile applications into VR, for example! >aQuery -- Like jQuery for Accessibility link >Don asks Peter Korn: Hey I would love to bounce an idea off of you! I didn't realize how much work you've done in accessibility. >The