This is why I love working on the web! People constantly experimenting and trying to find new/better/alternative ways to do things then others run off and apply them in wonderful new ways but only after the creator gives it out freely. Thank you for this! It's so cool! I don't have a use for it but I certainly appreciate it anyway and I'm sure I can find a legit use.
Path menu in pure CSS3
31–40 of 55 posts
Re: Path menu in pure CSS3
#32Earlier quoted context omitted.
i'm sorry, i don't understand who is competing or how this hurts Path. all i've seen are people being inspired by Path, saying as much, then cleverly recreating the effect for themselves. these same people turn around and share their own code with the rest of the world via blog post or GitHub. if anything this has helped spread the word about Path. this was how i first heard of them. throw in a bunch of people sharin…
> i'm sorry, i don't understand who is competing or how > this hurts Path. > > all i've seen are people being inspired by Path, saying > as much, then cleverly recreating the effect for > themselves. these same people turn around and share > their own code with the rest of the world via blog post > or GitHub. Looking at this from the perspective of Path, who have probably spent a fair amount of time thinking and conc…
Radial menus have been around for a while. Path have done it very well though. It would be somewhat unwise to have your whole business model based on a menu animation.
I wouldn't have found out about Path without this post, so I imagine that Path are happy about the publicity. It looks like a cool app.
Re: Path menu in pure CSS3
#33Earlier quoted context omitted.
Well the code is on github - fork it and update it!
I don't understand the "you aren't allowed to comment if you haven't submitted code" sentiment.
Don't take it wrong. It probably just means that the author was nice enough to make it and give it for free and if you have a problem, try to fix it instead of acting like an entitled asshole and demanding X feature or bug fix for code you didn't contribute to and are using for free.
There are a ton of people who like to bitch at open source developers about not including or fixing something and for projects like this tht isn't cool. This is just a guy showing off some cool thing he did. If you want to use it, have at it! Make it better? Contribute! Have a complaint? Go fuck yourself.
It's not meant for people who have constructive criticism or are just discussing the merits of the code or technique like us.
Re: Path menu in pure CSS3
#34Would it work on firefox if you just remove "webkit-" from the code?
s/webkit/moz/
I hope this isn't dumb but what does "s/Webkit/moz" mean? To answer the poster above you, it would work by adding "-moz-propertyname" not removing the "-webkit" stuff. Each browser will ignore the proprietary prefix that doesn't apply to them and then apply the CSS to any style that is prefixed for them or the official implementation. So you can put prefixes for all vendors in your rules and the browser will choose the one that applies while safely ignoring the rest. Just make sure to add the "official" non-prefixed version last so that future browsers or those who implement the spec completely today can render the final version of their implementation of the specific CSS style instead of the half baked proprietary one.
I'd add that vendor prefixes are one of the best reasons to use LESS (or SASS or SCSS, I just prefer LESS). Write one mixin (6 lines of code if you line break between each property) and you've just saved yourself countless keystrokes.
Re: Path menu in pure CSS3
#35Earlier quoted context omitted.
s/webkit/moz/
I hope this isn't dumb but what does "s/Webkit/moz" mean? To answer the poster above you, it would work by adding "-moz-propertyname" not removing the "-webkit" stuff. Each browser will ignore the proprietary prefix that doesn't apply to them and then apply the CSS to any style that is prefixed for them or the official implementation. So you can put prefixes for all vendors in your rules and the browser will choose t…
Not dumb at all! It's a common shorthand around here because in vim (and presumably other text editors) that is the syntax for replacing strings - in this case, replace "webkit" with "moz". It was a useless comment on my part. What I meant (and should have said) is that merely removing the vendor prefix "webkit" wouldn't make it work with Mozilla, but replacing it with "moz" probably would. (I'm not certain about the details of Mozilla's feature parity with Webkit when it comes to CSS animations but I suspect they are almost equal.)
Re: Path menu in pure CSS3
#36Can someone enlighten me as to why "pure CSS" is seen as the pinnacle of web design? It seems that for problems involving a computational element like this, Javascript would be much more concise and readable. Having said that, it is beautifully done.
Javascript is turing-complete. That's a /lot/ of power and that means that security-conscious users (especially given the proliferation of more-powerful JS apis allowing the possibility for exploits in file, GPU, etc. access, along with JIT-enabled exploits as opposed to the old simple interpreting) will have it turned off whenever possible. Using CSS for non-turing-complete interactions which are limited in their co…
Let's be clear: "security-conscious users" who turn off Javascript are a very small minority. If a site is geared towards serving developers or small startups, it might be serving this minority. If not, SEO ("how do I make this site readable by search engines?") will be a much larger concern than "graceful degradation for the benefit of the tiny few who care about security enough to disable Javascript or use NoScript but not whitelist my sites' scripts". Often designing something to gracefully degrade will serve both SEO and security-conscious users, but in cases where it won't (this case for example -- where Google decidedly doesn't care about the layout of the navigation items, as long as they're accessible to it), there's not much incentive to find a pure-CSS approach when a pure-JS approach might be simpler.
Re: Path menu in pure CSS3
#37Earlier quoted context omitted.
i'm sorry, i don't understand who is competing or how this hurts Path. all i've seen are people being inspired by Path, saying as much, then cleverly recreating the effect for themselves. these same people turn around and share their own code with the rest of the world via blog post or GitHub. if anything this has helped spread the word about Path. this was how i first heard of them. throw in a bunch of people sharin…
> i'm sorry, i don't understand who is competing or how > this hurts Path. > > all i've seen are people being inspired by Path, saying > as much, then cleverly recreating the effect for > themselves. these same people turn around and share > their own code with the rest of the world via blog post > or GitHub. Looking at this from the perspective of Path, who have probably spent a fair amount of time thinking and conc…
I'm unsure why I was down voted for this. Was it because the down-voter didn't agree with my post (strange reason to down vote), or was it because it didn't contribute to the conversation (which I tried quite hard to do - by balancing both sides of the argument).
All I was trying to say was that in the field of UI, it is very hard to innovate though very easy to copy, and I can't help but feel that's what's happened here.
Path have made a very sexy looking widget which definitely added that certain something to their application, and someone has copied their hard work and made it free for everyone to use.
Re: Path menu in pure CSS3
#38saw this one earlier in dribbble, http://dribbble.com/shots/340844
http://sparanoid.com/lab/path-menu/
Re: Path menu in pure CSS3
#39Earlier quoted context omitted.
I don't understand the "you aren't allowed to comment if you haven't submitted code" sentiment.
Don't take it wrong. It probably just means that the author was nice enough to make it and give it for free and if you have a problem, try to fix it instead of acting like an entitled asshole and demanding X feature or bug fix for code you didn't contribute to and are using for free. There are a ton of people who like to bitch at open source developers about not including or fixing something and for projects like thi…
Exactly my sentiment :)
Re: Path menu in pure CSS3
#40Earlier quoted context omitted.
I don't understand the "you aren't allowed to comment if you haven't submitted code" sentiment.
Don't take it wrong. It probably just means that the author was nice enough to make it and give it for free and if you have a problem, try to fix it instead of acting like an entitled asshole and demanding X feature or bug fix for code you didn't contribute to and are using for free. There are a ton of people who like to bitch at open source developers about not including or fixing something and for projects like thi…
thanks Bill. This is exactly that.