251–257 of 257 posts
Earlier quoted context omitted.
Because its an otherwise very useful and good looking CSS library.
Trying to tell me a big comprehensive CSS library breaking mobile devices in 2017 is useful is like trying to sell me a car that can't drive on pavement.
I've done a few projects with Sematic UI. I think it's great for desktop based business applications. It looks slick, and has great animations. Plays nice with heaps of frameworks, I was using meteor.js However, don't use it on mobile - it will destroy performance.
Curious about this. Any clue why? Too much animation, heavy JS-use? Not familiar with how the framework does its stuff.
Earlier quoted context omitted.
Gosh that irritates me - does that mean that the "tap just above the clock to return to top" doesn't work? Edit: just checked, and yes it does. Also breaks the pattern where iOS shrinks the address bar and navigation bar when you scroll down. Completely unacceptable for a UI library to break these OS-level patterns
> tap just above the clock to return to to Didn't know about that. Thanks!
Fixed the scroll issue in the docs. Should be glorious normal iOS scroll.
Might also check out Ant Design. https://ant.design/ It's integrated with React and there's a separate mobile UI for it. Ant is Chinese, with docs translated into English. Like China, it's huge^^ I've just been fooling around with it today for the first time in create-react-app and seems good so far. Haven't tried on mobile.
I like that you can import just the css you need for a component. Semantic ui should do this too. Some mobile glitches with Ant, but I'm considering trying it. I only need a few components
Earlier quoted context omitted.
Strongly disagree, and the primary reason is that semantic HTML makes your source and stylesheets readable and easy to navigate and change for that reason. That is, setting aside technical arguments about re-usability for a moment, it's disastrous to have to look at a large codebase in this style: when you could look at this: The latter, aside from sparing your brain endless visual noise, makes it instantly clear how…
You're ignoring GPPs argument though, 'basket', 'product' and 'searchResults' aren't reusable. From the POV of a dev on your team (who knows the framework), I know how to change 'pull-left', 'row', 'col-xs-4' to get the result I want without CSS spelunking.
Earlier quoted context omitted.
The worst is when, if you maximize the browser window, the hamburger menu expands into actual menu elements, but then if you resize the browser window to, say, half the width of your screen, it turns into a hamburger button with enough whitespace around it to display the hidden menu elements. Really, really hate that. The web was more usable 15 years ago.
I'm not a big fan of the hamburger menu either, but web developers also didn't have to worry about mobile 15 years ago.
Earlier quoted context omitted.
You're ignoring GPPs argument though, 'basket', 'product' and 'searchResults' aren't reusable. From the POV of a dev on your team (who knows the framework), I know how to change 'pull-left', 'row', 'col-xs-4' to get the result I want without CSS spelunking.
To change it, I'll have to go spelunking through either the HTML or the CSS, and if I was a designer, I'd probably pick the CSS. Looking for the 'product' class and tweaking a few properties sounds much nicer than figuring out how I need to change 'col-xs-4'. I'd rather have a conversation with the layout engine than struggle with some middle-man generic CSS framework like Bootstrap - it's simpler and more flexible (…
Also yet to meet one of these 'designers' that would rather change CSS than HTML. And logically ... you can't understand CSS without understanding HTML, so preferring to make the change in CSS is just an arbitrary decision.