Version 16 Release Plan

[avc]

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

[TurkerTunali]

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

[MrKovalski]

adds fuzzy search and adds serbian translation

[MrKovalski]

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.

[rmehta]

@Joshua_Restivo

Is the June 1 date for beta no longer valid? Or is the beta somewhere other than the obvious (ie., I don’t see a version-16 branch in github). I know we can pull develop but a fixed release target would be ideal for bug hunting/reporting purposes.

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.

[petn]

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?

[MrKovalski]

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

[peterg]

@rmehta

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.

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.

[peterg]

@MrKovalski

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

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.

[anupd]

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

@rmehta

The goal is to release an amazing version 16 and set a very high bar.

This is very important and a great decision.

[ahassoun]

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

[Peer]

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.

[mohamed-ameer]

like literally

[federico_calvo]

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

[dahaka]

@peterg

@rmehta

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.

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.

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) So can’t wait for the typescript + vue rewrite!

[f_deryckel]

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?

[peterg]

Vue calls itself an “incremental” framework. You can add it to an existing page, give it control of only a tiny part, and leave everything else about the page working exactly the way it was before. It is designed from the start to play nicely with other libraries.

I have no idea what’s planned for future versions of Frappe beyond what’s been shared, but I can’t think of any technical reason for the addition of Vue/Frappe-UI to break anything that’s already existing without them.

[ahassoun]

Does the addition of Vue/Frappe-UI means the removal of dependency on Bootstrap 4? Do you know if is it getting removed, bumped to Bootstrap 5 or will remain untouched?

[SmoothPlay]

Amén to that