Let's move there for privacy.

--Marin

Hi James,

For a variety of reasons, editing of posts in the forums is not enabled. I suggest you open a private ticket and let me know what you need removed/updated.

Regards,
Marin Bratanov
Progress Telerik

Thank you for sharing your solution, James. Such acts go a long way in building a community of users.

Regards,
Marin Bratanov
Progress Telerik

Here's a link: https://www.telerik.com/forums/blazor/menu. This required going up the management chain so it took a bit longer than I thought.

--Marin

wow, we've missed creating a forum for the menu, I'll get back to you when it's done.

--Marin

I understand.

I think it could still be an interesting example for the community, so if you are willing, you could post it in the forums.

Thanks,
Marin

That's great news, James. If you like, you could post what you came up with on the forums. With your permission, I could event add it to the knowledge base section of our docs.

Regards,
Marin Bratanov
Progress Telerik

Hello James,

You should be able to do this with templates by adding the desired fields in the model and the necessary markup: https://docs.telerik.com/blazor-ui/components/menu/templates.

If this does not fit your needs, I would encourage you to post a feature request for such a feature in the feedback portal through the "Request a Feature" button. Just make sure to select the "make public" checkbox at the final step. This will let you explain your goals, requirements, even perhaps add a sample of what API and functionality you would expect it exposes. You can then Vote for it and Follow it to get updates on status changes. If it gets good traction with the community, we will consider its implementation.

Regards,
Marin Bratanov
Progress Telerik

We do have a plan and it includes a menu. Hopefully, it will be live in the autumn, or perhaps even earlier. The roadmap page will also soon have information, we are working on a lot of things - setting up an entire new suite and technology requires a lot of work behind the scenes, and we're getting there.

What we are aiming is two major concepts that are, often, contrary to each other:

• Provide the components an app needs, especially those that are harder to get right (grids, charts, calendars, for example), and we know them from our experience through our other suites, and provide them with higher priority than ones that are either relatively easy to make (let's say, basic listview, or basic menu).
• Tackle feedback and requests actively to follow the community interest and provide what most people need right now, in a fashion similar to which Microsoft incorporate customer feedback actively in the development of the Blazor framework itself.

Getting such a balance right is by no means easy, and sometimes we will do what we feel is important, other times we will follow demand. There is no ready-made formula for this. Having feedback is always helpful, however, and we intend to keep using it, combined with our judgement. 

To be candid, this is the reason why there are many requests that stay open for years on end in the older suites - while some of them even get some traction, we sometimes do not find them useful enough for a given suite, in light of our entire customer base, to sacrifice effort and time into them, while we could, instead, do something else that is deemed more important or with higher impact.

We have been, and will continue to use our judgement when prioritizing, and having the public votes, comments and interest available is only a part of the puzzle - you can call that a tool that will help us get things right, if you will. There are other tools in the arsenal of the product manager that we also use, and not all of them are publicly visible.

We are working on a menu control. You can Follow this page to get notifications when it gets implemented.

The first release of the Blazor suite did not include a menu, because we had focused on a grid and on a few POC components to explore how the framework is supposed to work and to be used, and to also support the grid (like inputs that are needed for grid editing). We are building all the components from the ground up as native components, and this is why we can't have a complete suite of 60 or 100 components ready immediately - the Blazor suite is mere months old, as opposed to 10+ or 15+ years we have in the Kendo and WebForms suites, for example. We choose not to wrap JS widgets as this is not how Blazor is supposed to work. You can read more on the subject in this blog post: https://www.telerik.com/blogs/comparing-native-blazor-components-to-wrapped-javascript-components.

Another reason is that we intend to actively incorporate community feedback into our prioritization process. At the moment, the most requests we have received are for a grid and this is the first one for a menu. While we initially also thought that the menu should be among the first components, feedback indicated that it is not exactly true. So we focused on hardening the grid and improving its CRUD functionality, plus integrating validation.

Said simply, if you want something you don't see - add a feature request to the portal, so the community can vote and comment on the idea, which would raise its priority in our backlog.

I hope this explains the situation and how we handle new features and components.