profileapi.blogg.se

Firefox for mac - about menu
Firefox for mac - about menu






and now owns and resides in the 1000 year old tower near Rieneck Castle in Germany that he calls Byteburg.

#Firefox for mac about menu software#

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? )

firefox for mac - about menu

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.

firefox for mac - about menu

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.

firefox for mac - about menu

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.






Firefox for mac - about menu