I guess "A UI Toolkit for Desktop Web" (as opposed to "Mobile Web") would be clearer but sound more awkward.
In general, it seems English doesn’t try to make a distinction. Is a small, red bird a small bird that’s red or a red bird that’s small? Same difference, and in fact the standard ordering of adjectives (1) would preclude such a distinction from being possible.
There are dozens of libraries like this, especially many that follow the Ant Design guidelines created by the major Chinese company Ant Financial for their own apps. Vue has a large Chinese community and is more often used in projects there, which also means the documentation might be a little wonky when translated to English.
Some other design systems and component frameworks, with varying support for mobile and corporate backing:
A Nuxt core member is a core contributor to the project.
I like it because it's not over-engineered with like 10 classes to do a simple dialog. You can go to any .vue file and look how they do it. It's not very difficult to copy some bits of the code and css, to do your own components. They use a bit of mixins and whatnot but for the most part you can reuse some of that code without having to bother with the node packages and whatnot. Plus they have a bunch of useful little bits of js in there for dom manipulation etc.
I also learned how to manually instantiate components and passing props to them, from this codebase. It wasn't made obvious in the Vue docs.. and it's actually SUPER useful when refactoring old codebases (like YUI2).. where I do'nt have the luxury of wrapping everything in a view, I can make a Vue dialog, or a Vue bar chart.. and "mount" it to the page. Then I can use the webpack build, single file components & all the good stuff from a modern Vue build in a legacy web app.
VueJS makes that all very clean and simple compared to everything else I looked at which wants you do to do it "our way or the highway".
- since we're mounting components and using SFC, we can use the "runtime only" build (though I keep the full one when I want to make something quick, because the savings in the minified Vye library were very small)
- it can be a small performance improvement in cases where we want to mount something in response to user input, whereas the template in the html page will be compiled on page load (afaik).
I suppose if they’re committed to being desktop only they could at least remove the meta zoom tag so I could see a scaled down version on my phone and zoom and pan around, ala the original safari mobile experience.
"Designed with web technology" doesn't necessarily mean "designed for the public web".
In many enterprise settings desktop-only is perfectly fine because applications developed for these environments often won't ever be accessed from a mobile device anyway. Even if they are it's usually only a small part of the application that needs to be available for mobile devices.
In these cases, devoting an inordinate amount of time to making all of your design work flawlessly on mobile devices can mean a huge waste of resources.
By the way, from a cursory check - while not particularly mobile-friendly - this UI toolkit is responsive (probably also because that makes perfect sense on the desktop as well) and seems to work alright on mobile devices, too.
There's no need to be good at something that doesn't apply to your situation, especially considering how much more work mobile UI takes.
It integrated perfectly with Vue.js.
We plan to use it throughout the rest of our application as we replace Rails views/jQuery with Vue.js components.
Apparently the Select component doesn't support any keyboard commands - something quite many users do use on a regular basis. So apparently it's a downgrade over the default browser behaviour.
I don't think that ever makes sense when it comes to design. No one ever says there are so many shirts out there let's not design another one...
Perhaps not, but many should.
I'm sad it didn't get much traction. At the time, it seemed Apple was trying similar things with SproutCore
It looks VERY similar
Makes me wonder who ripped off^h^h^h forked whom.
edit: found https://github.com/AT-UI/at-ui
Element repo history starts in September-ish 2016, AT-UI in Apr 2017. The content is very close, but I'd guess Element is the original. Not sure.
It's just another CSS framework ala Twitter Bootstrap, very misleading.
Really like the clean interface. Ended up using this instead of Vuetify. Vuetify is really well put together and maintained, I just found that I really dislike Material design.
Does Element have something similar?
It's not 2010 - we have grid for grids. Unless someone is paying you vast quantities of money for IE support why use something else?