Simple port of Fluent UI (formerly Office Fabric) React components and style to Blazor
https://www.blazorfluentui.net/
https://blazorfluentui.azurewebsites.net/
https://t.me/joinchat/TuHGR8AZmYe1SKlH
On each commit new dev nuget builds will be created automatically. To access those, add a new Package Source to Visual Studio or your project with the following URL:
https://pkgs.dev.azure.com/blazor-fluentui/5355f597-190a-4424-83da-cd89cd362a24/_packaging/DevChannelV5/nuget/v3/index.json
For a more detailed tutorial, head over to our Public Feed, click on "Connect To Feed" and select the platform.
All components have dropped the BFU
prefix and names are now on par with their Fluent UI React counterparts (or will be soon). Change was made to not litter the codebase with the term BFU
everywhere.
The demo sites have been given some attention and look a lot better now (more in line with Fluent UI Rect docs).
You will now have to define your list's container separately from the list component. Pick a <div>
or other container element and apply the data-is-scrollable
to it. You'll also have to style it appropriately for your page. (For example, add overflow-y:auto;height:100%;
or something similar.) You do not have to place your list component as a direct descendant of this container. If you fail to place the data-is-scrollable
tag, then the component will traverse the nodetree to find the first container element that has overflow-y:auto;
set.
You also have to define GetKey
for your list component. This is a selector for your items to tell the component how to uniquely identify each item.
A big change is that OnItemInvoked
will only work when SelectionMode
is set to None
. If you need Selection active and the invoke item function to work at the same time, you can attach an event handler to the Selection.OnSelelectionChanged
event or subscribe to the SelectionChanged
observable.
These components and interfaces must be removed as they no longer function within this library. Switch to using CSS isolation with your razor components instead. BFULocalCS
is still present and encouraged for dynamic styling that requires flexibility. (Using the style attribute on an element makes it difficult for users to override the style.)
If you need to reference the theme from a css file, you can reference the global css variable instead. For example, where before you would get a white color in C# as Theme.Palette.White
, now you will write in css, var(--palette-White)
. Css global variables always start with two dashes and a lowercase name. Instead of a dot, use a dash followed by capitalized names.
Home
Installation
How To Use: ClientSide Blazor
How To Use: ServerSide Blazor
Theming \
There are no MergeStyles in this port. It's just each control packaged into its own project so you can limit what gets added to your Blazor project.
Control | State | Information |
---|---|---|
Calendar | Done | |
ColorPicker | ToDo | |
DatePicker | Done | |
PeoplePicker | ToDo | |
Pickers | ToDo | |
SwatchColorPicker | ToDo |
Control | State | Information |
---|---|---|
Breadcrumb | ToDo | |
CommandBar | Done | |
ContextualMenu | Done | |
Nav | Done | |
OverflowSet | Done | |
Pivot | Done |
Control | State | Information |
---|---|---|
Coachmark | ToDo | |
MessageBar | Done | |
TeachingBubble | ToDo |
Control | State | Information |
---|---|---|
ProgressIndicator | Done | |
Shimmer | ToDo | |
Spinner | Done |
Control | State | Information |
---|---|---|
ResponsiveLayout | Done | |
RichTextEditor | In Progress | Works with limited styles available |
GlobalCS | In Progress | |
LocalCS | In Progress |