![]() Convolver lets users play, trying any combination of filters at will, either on their own or with the computer’s aid and advice. >In the past, designers have followed a process of picturing their desired end result in their mind, then applying a series of filters sequentially, without benefit of undo beyond the last-applied filter. It replaces the extensive lineup of filters that graphic designers traditionally grapple with when using such tools as Photoshop with a simple, integrated, harmonious environment. ![]() >KPT Convolver is a marvelous example of kansei design. All were dedicated to building a single, tightly integrated environment – a totality of experience. ![]() So did the Lisa team, and the Mac team after. Kansei starts with attitude, as does quality. >»Where does kansei start? Not with the hardware. >Kansei speakes to a totality of experience: colors, sounds, shapes, tactile sensations, and kinesthesia, as well as the personality and consistency of interactions.« Waterfalls are not simply lined with interesting rocks they are tuned to create just the right burble and plop. Rocks are not just strewn about they are carefully arranged in odd-numbered groupings and sunk into the ground to give the illusion of age and stability. Every rock and tree is thoughtfully placed in patterns that are at once random and yet teeming with order. 618 the Japanese have been creating beautiful Zen gardens, environments of harmony designed to instill in their users a sense of serenity and peace. >Bruce “Tog” Tognazzini writes about Kansei Engineering: On a fan to full blast and aimed it at your neatly stacked paperwork. Your folders and documents strewn over your screen as if you'd just turned ![]() The desktop metaphor was adapted to have more sophisticated layers -īasically, it was the standard desktop but with no filing cabinet and all He did show me one possible interface, where Glowing orbs to fiddle with just to save a simple file. >At the time, Kai was king of the weird interface - Bryce, KPT and Goo wereĪll decidedly odd, leaving users with lumps of spherical rock to swivel, and One of old Apple's very few pieces of good luck that Kai said "nein" Me that Apple had asked him to help redesign the Mac's interface. >When graphics guru Kai Krause was in his heyday, he once revealed to >read me first, Simon Jary, editor-in-chief, MacWorld, February 2000, page 5: You just can't hurt yourself." -Kaiīut all in all, it's a good thing for humanity that Kai said "Nein!" to Apple's offer to help them redesign their UI: "The interface is also, I call it the 'Padded Cell'. Oh, and along the way, he found time to work on software milestones like Poser, Bryce, Kai's Power Tools, and Kai's Super Goo, propagating what he called "Padded Cell" graphical interface design. and now owns and resides in the 1000 year old tower near Rieneck Castle in Germany that he calls Byteburg. Embrace his gaze! He is an absolute legend in certain circles, not just for his software contributions, but his overall life story." >"Now if you're like me, you must be thinking, ok, this is all well and good, sure, but who the heck is Kai? His name's on everything, so he must be special. ![]() >Revisiting the mid 1990s to explore the world of gooey image manipulation from MetaTools! Kai Krause worked on some fantastically influential user interfaces too, so let's dive into all of it. Kai's Power Goo - Classic '90s Funware! : In the modest liner notes of one of the KPT CDROMS, Kai wrote a charming rambling story about how he was once passing through airport security, and the guard immediately recognized him as the User Interface Rock Star that he was: the guy who made Kai Power Tools and Power Goo and Bryce! Love him or hate him (and I do both), Kai was all about cultivating his adulating cult of personality and dazzling everyone with his totally unique breathtakingly beautiful bespoke UIs! How can you possibly begrudge him and his fans of that simple pleasure? ) Glad it's happening, excited to see how well it works! It sounds like perceived needs have changed, and maybe the native APIs allow for bit more flexibility now. There was some discussion of switching back and forth between native and non-native menus based on styling, but that got complicated quickly and it wasn't thought to be worthwhile. The native APIs put heavy limitations on what you could do with a native context menu and it was just not compatible with the expectations of people building against the rendering engine at the time. People expected to be able to change colors and layout with CSS, for example. It has nothing to do with engineering resources, and we always wanted native context menus, but they were not customizable enough to meet the perceived needs of web, XUL, and extension developers at the time. As someone who used to be involved in the decision to not implement native context menus, and did a bunch of work on the non-native ones, I want to try to explain why this took a long time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |