Is it just me or is the first thing you want to to see and try the damn things out?
Ctrl+F "Demo" - nope.
I think I found them eventually under "Component Explorer" - but that's in the secondary nav and not in the main menu.
Microsoft Fast Design
51–60 of 216 posts
Re: Microsoft Fast Design
#52I was looking at the code it looks optimized, will do a couple of tests later maybe combining this as the main webcomponent controller with something like tailwind css makes sense, but just using this plain look and feel I don't think it's viable at this moment but it's a good structural start I would say. Was looking forward to do this with lit so maybe I might test this and see how the code looks, from a code output perspective it looks promising let us see this with something like snowpack.
Till now Lit looks a lot easier to use and all let us see how it goes.
Re: Microsoft Fast Design
#53To my understanding, the point of this system is not actually how its default component looks or how rich the default components set are. It's to provide a framework to create Custom HTML Elements (which are browser native?) that we can re-use across projects with different front-end frameworks.
e.g., Creating a React Button component using Fast Button like this:
`const ReactButton = () => Button`
Re: Microsoft Fast Design
#54I love seeing a wider adoption of webcomponents, but I have some complaints about this library, mainly because they're really pushing the whole, "lightweight and low memory" lines. Take a look at the accordian component (the very first one in their system) and check it out in the dom inspector - it has a shadowroot that has precisely one child: a element. In this situation a shadowroot does nothing to help. All it me…
To clear my understanding of your first statement, you're saying that their "lightweight / low memory" claim is invalidated by components having one unnecessary level of nesting in DOM?
No. They’re saying that it’s creating an entirely separate DOM tree unnecessarily by using shadow DOM where it isn’t needed.
On a related note, I’m curious if anyone has a benchmark comparing performance and memory consumption when attaching a shadow root vs not.
Re: Microsoft Fast Design
#55On mobile Firefox the side menu is quite janky
Re: Microsoft Fast Design
#56Microsoft recently wrote a blog post saying they would be rallying around a single component library. [1]
> What’s in a name? A lot it turns out. And we have a lot of them. Too many? We hear you and agree. That’s one of the key reasons we’re simplifying our story. To collectively rally around a single UI library for our web components—Fluent UI.
Yet, here we are, and they've released another component library. They really seem to love these things. It's not entirely clear what the difference is between them.
1: https://developer.microsoft.com/en-us/office/blogs/ui-fabric...
Re: Microsoft Fast Design
#57I love seeing a wider adoption of webcomponents, but I have some complaints about this library, mainly because they're really pushing the whole, "lightweight and low memory" lines. Take a look at the accordian component (the very first one in their system) and check it out in the dom inspector - it has a shadowroot that has precisely one child: a element. In this situation a shadowroot does nothing to help. All it me…
Another funny thing with the accordion component: the icons for expand and collapse seem to my mind to be reversed (- for expand and + for collapse)?
Re: Microsoft Fast Design
#58Don't want to be ride but that is yet more JavaScript fragmentation. That's it
Re: Microsoft Fast Design
#59Ok, so it looks like the main point of this is fast-components, which is a just a bunch of components styled as MS-style, but I'm more interested in the fast-foundation package. According to the instructions: > The exports of this package can generally be thought of as un-styled base components that implement semantic and accessible markup and behavior. > it exports parts and pieces intended to be composed into Web C…
Lit has been doing this for a while it's from that Polymer project.
https://lit-element.polymer-project.org/
Web Components is a huge deal, you can do just web components on plain notepad and not need any build system for something very simple just using module based packages on the browser this is really cool.
Snowpack for me was something huge, getting away from webpack was like getting back hours of work.
But I don't know, till now for me I still see the Lit-Element and stuff as being more flexible than this one, the beauty is for example you can have a component in react and another on in Vue, it doesn't really matter and another one in JQuery. You can have whatever works best for you for each case.
Re: Microsoft Fast Design
#60Ok, so it looks like the main point of this is fast-components, which is a just a bunch of components styled as MS-style, but I'm more interested in the fast-foundation package. According to the instructions: > The exports of this package can generally be thought of as un-styled base components that implement semantic and accessible markup and behavior. > it exports parts and pieces intended to be composed into Web C…
edit - to thank everyone who took time out to explain what's going on - I'm still cynical but it all makes more sense now. I also like to think the ignorant guy asking the ignorant questions (in this case me) can sometimes be valuable for others who aren't in the club. Previous rant intact below for fun and hijinks.
---
As a jaded old web developer I've seen so many frameworks along the way all promising this and that.
Can someone who is familiar with this answer me this: Does this framework automatically sort out ARIA standards for me? Like tab ordering and stuff is dealt with automatically?
I know it seems I am being lazy but I am just fed up.
"FAST is a collection of JavaScript packages centered around web standards, designed to help you efficiently tackle some of the most common challenges in website and application design and development."
COOL! (/s)
"Have you ever needed a reusable set of UI components that you could drop into your app and have an amazing experience? That's FAST."
UNIQUE! (/s)
"Have you ever needed to create your own components, and share them across your company, including across groups that use different, incompatible front-end frameworks? That's FAST."
Different, incompatible front-end frameworks?
So like, this shit is magic that will let me streamline components between my Oceania team's WordPress and my German team's Magento frontends?
And I don't have to learn any new paradigm to make this work?
I don't have to use their specific, custom HTML in order to leverage it? https://www.fast.design/docs/components/accordion
SWEET! (/s)
Come on. We'd have to re-write everything to use this library specifically, and train our teams.
Honestly this is to me just another bunch of shit that will get tacked into projects and have to be known and supported, because some sprightly young thing will convince management this is the panacea to seemingly redundant development work.
What's the actual selling point here.