Version 16 Release Plan

I think having some built in options to customise the look would be a great addition.

This project, or built-in options like it, would be a good alternative to allow for simple UI changes from within a frappe app without have to create new apps to apply themes.

Also, for the existing light and dark themes, might be worth tweeking some of the lighter grey colours to improve accessibility.

As you can see below, using the WAVE accessibility tool, some text on the login in could have a better contrast. Might apply to other elements too but don’t have a publicly visible site to test with. Improved accessibility is rightly becoming more prominent in web design and applications.

2 Likes

may be you can consider it the theme setting for erp just like Oracle Cloud they have custom theme. You can update the bg of the erp and put some effects on it just like Friendster etc.

1 Like

Why are datatable maintainers completely ignoring contributors outside of frappe team. I have PR that adds option for fuzzy filtering rows filterMatchStrategy: ā€˜strict’, // strict, fuzzy, tokens. Its waiting for 2 months to be merged while team PRs are instantly merged.

5 Likes

Excited for the Update

Maybe @sohamkulkarni can check this. Please @MrKovalski, can you link the PR here?

1 Like

Wow, fuzzy filtering in Datatable, that’s something. We still can’t do that on Links.

1 Like

Yeah. While onboarding my coworkers. I noticed that was one of the big pain points. They were like, ā€œWhy can’t I find this item?ā€.

If you are interested in how to do it, we can create new topic. But basically create python function and define from JS all the fields where it should be triggered on.

5 Likes

No all plans seemed delayed for now.

Context: We wanted to upgrade the UI for version 16 to match it with the more modern Espresso Design system and Frappe UI (much like Frappe CRM), but that project seems to be taking a new direction. We don’t know that it will be yet - but you an expect some PRs soon. Frappe UI will get 1st class integration in Framework 16 and also ERPNext 16. UI will be a breaking change, but it will take the UX to the next level.

In general, we don’t have a big feature gap between 15 and 16. 16 is way more performant and there are some UI upgrades. The goal is to release an amazing version 16 and set a very high bar. Time is not a constraint.

There will definitely be a major preview at Frappeverse if not a full release.

12 Likes

Thank you very much for this information!
I guess many of us are very happy about any information and may desire more of this frequent updates about major development steps. Especially if set dates will be delayed.

One additional question about the new design: As accessibility gets more and more important in Europe, do you consider this while designing the new UI?

3 Likes

So should we postpone any development on frappe UI based apps if it will have breaking changes in version 16?

This is excellent news. It’s already possible to create some pretty amazing custom interactivity by hooking into HTML fields, dashboards, and blocks, but it sometimes gets a bit messy.

Having a single design language that can work across the desk, standalone applications, pages, portals, etc. would boost power and minimize complexity at the same time.

2 Likes

I’d be very happy to be corrected if I’m wrong about this, but I wouldn’t think that Frappe UI’s integration into the framework would have any impact on standalone applications. Those have an entirely separate build step and could continue compiling against arbitrary versions of the library.

What does seem likely to happen, though, is that many things currently being built as standalone applications would suddenly become much easier to make in Desk directly.

1 Like

That is a great news. All apps must have the same design language.

This is very important and a great decision.

@mohamed-ameer with the new UI capabilities and integration possibilities we will have a lot of new areas to cover in your tutorials :smile:

With the very high bar set, the doc will thus be amazing.
First step probably being to be and stay in sync with any new code, lest the doc-linter refuses to merge.

like literally :smile:

Hi, different from what is seen in the develop branch?

100%! I’ve been closely watching the client-rework branch and experimenting with it. I’m new here, but experienced in the field, and I can’t see myself using javascript and jquery to customize the framework (let alone simple client scripts) :sweat_smile: So can’t wait for the typescript + vue rewrite!

Not sure what would that mean for Frappe desk Page that have been build using lots of extra js libraries and css components? What would the impact be there? Need to redo everything using Vue? At the moment frappe-ui and Vue were not part of the frappe desk at all. Is that what is changing?