Semantic UI – A language for sharing UI
31–40 of 85 posts
Re: Semantic UI – A language for sharing UI
#32What I'd really like is a UI toolkit for developers that goes
Frankly, Bootstrap is exactly that, for me. I've been converting our products (Webmin/Virtualmin, which are 15 and 10 year old codebases, respectively, and it shows badly in the current UI). Converting to Bootstrap, while extremely time-consuming, is not requiring significant design skill on my part to make everything look freaking awesome.
Re: Semantic UI – A language for sharing UI
#33Can you guys please stop whining about the name and talk about the features? Didn't your elementary school teacher tell you not to judge a book by its cover? They could always change the name if they had to. They never actually say they're semantic HTML, it could have other meanings. Or, you know, it could just be a name. There's plenty of projects with meaningless names.
Don't be an idiot. Semantic UI has a meaning. The authors chose to ignore its meaning while trading on the cachet of the name. While their web dev skills may be unsurpassed, it's a reasonable criteria on which to judge them.
A single post or two on the name I could understand, but every comment? HN fixates on the absurd.
Re: Semantic UI – A language for sharing UI
#34This. I like this. It's sort of like an OOCSS Bootstrap.
Re: Semantic UI – A language for sharing UI
#35Re: Semantic UI – A language for sharing UI
#36Earlier quoted context omitted.
Yeah that one was too specific for my liking I don't think you should use colors names like 'red' as a class. What if you decide you don't want it to be red?
Remove the "red" class from the element? I used to eschew any and all presentational classes, but it makes development quicker for me to use them occasionally, esp with css frameworks.
Re: Semantic UI – A language for sharing UI
#37Earlier quoted context omitted.
Don't be an idiot. Semantic UI has a meaning. The authors chose to ignore its meaning while trading on the cachet of the name. While their web dev skills may be unsurpassed, it's a reasonable criteria on which to judge them.
Ad hominem attack, really? A single post or two on the name I could understand, but every comment? HN fixates on the absurd.
Calling something Semantic UI and comparing it to another library, that more follows the actually meaning of semantic, is silly. Yes you can change the class name but setting up the name as something meaningful, something semantic, such as 'submitButton' lets you redefine it in the CSS.
If I'm building something that multiple clients will use I don't want each client having buttons with class names specific to the client, but something I can modify easily in the CSS to get the look and feel they want.
It's ass backwards.
Re: Semantic UI – A language for sharing UI
#38I wouldn't call writing "ui large red labeled icon button" in HTML semantic anything. I'd called it confusing orgy of style and content.
I agree. First of all, why is a ui class necessary? Second, what's large? The icon, the button, the label? All of it? What's red, the icon or the button? Certainly not both. There's a reason we have classes like "btn btn-small icon-* icon-2x". A large icon in a small button. I think those names are more 'semantic'.
Re: Semantic UI – A language for sharing UI
#39The bootstrap markup is actually more semantic than Semantic UI. Classes like large, red, floated, right, circular etc.. are presentational not semantic. If you want to use a framework and keep semantic CSS then look in to using the LESS/SASS version of Bootstrap or Foundation. Edit: After a more detailed look, the framework is actually really nice (and very comprehensive). The name still doesn't make much sense thou…
Re: Semantic UI – A language for sharing UI
#40Great idea except you don't namespace anything! I like namespaces because one library or css import from another won't ever stomp on each other. I've seen 'ui', 'button' and 'red' in several other packages and places. They're going to conflict. The one with the greatest specifity is going to win and cause untold hours of frustrating debugging.