Goals for w2ui 2.0

[vitmalina]

Road to 2.0

Browsers continue to evolve and JS development practices change. More things are possible now and some patterns have become standards. I feel that w2ui need to reflect these changes

Here are things to consider for 2.0. It is open for discussion and please add your comments/features as you like.

1. Drop support for legacy browsers.
   Only evergreen browsers (Google Chrome, MS Edge, Firefox, Opera) + latest Safari will be supported. MS IE and all of its versions will not be supported.

2. Move to flex grids, especially in w2grid but preferably in all components
   Tabs have already been rewritten with flex grid.

3. Consider using arrow functions in places where it makes sense.
   It will drop support for legacy browsers and currently not possible due to other dependencies, notably gulp.

4. Consider other new JS features and practices, for example write code w/o ;
   I like clean code. Might consider moving to classes.

5. Move to gulp, drop grunt
   Might consider other packagers, but so far I am not impressed with any gulp has been my task runner of choice and with version 4 it has become very flexible and easy to extend and control the process.

6. More explicit integration with kickstart possibly rename in w2ui-starter
   See (https://github.com/vitmalina/w2ui-starter)

7. Consider dropping jQuery as a dependency
   Possibly just use modern version of it for evergreen browsers.

8. Rewrite overlays as they were source of issues
   Overlays, menus, tooltips - all needs updates

9. Updated Look and Feel for the components for the modern web

10. Better support for ARIA and general accessibility.

New name for the project

I am looking for a better name for the project. Something less techy and more beautiful. Originally w2ui meant Web 2.0 UI, in other words, I wanted to express the idea that the library is not for content-heavy websites, but for data-driven and desktop-like applications where users are actively interacting with the app and not just reading it. At that time web 2.0 expressed that idea, but not any longer.

For me desktop-like applications are apps that allow more complex user interactions in contrast to content-heavy websites. Historically, many some activities were only possible as fat-client app, browsers could not handle those type of tasks, for example, apps like MS Office, Photoshop, Video Editing apps, etc. However, browsers are now capable to handle these tasks as computers became beefier.

In the name I want to express

• it is a UI library
• it is for heavy apps, not for content websites
• it aims for modern look/feel

Bug fixes and 1.5

There will be a new branch w2ui-1.5 for bug fixes, etc for the older version of w2ui. Only bug fixes (and they seem to be not very frequent theses days) will be implemented that. This branch will never be merged to master.

[gdans]

I am very happy that you will continue this project.
Thanks !

[haitham911]

I am very happy that you will continue this project.but please add LTR support its very important

[Mirsof]

Great, currently in my company we are using it in an intranet app with a lot of data at the same time => Asp.net + Bootstrap+ W2UI

Some names :
FormsComponents.js
FastUIKIT.js
WebUIForms.js
DDriveUI.js
DriveForms.js
UXWUI

[vitmalina]

Out of this list, I like FastUI. But it still does not carry across the message that it is for rich UX applications.

I don't think the forms is a valid part of the name as forms is a small part of w2ui

What about going something unrelated, like a fruit or a berry, or a tree. (not sure)? May be a place or some natural park?

[boumboum]

What about dataUI?

[mpf82]

Name suggestions:

• solidUI
• rockUI (because rocks are solid and heavy - and the lib just rocks 🤟)

---

Dang, maybe I should google first and then post suggestions - both names are already in use 😒

https://github.com/solid/solid-ui
https://github.com/rock-ui/rock-ui

[AndrewMylesHammond]

Appreciate this may sound like a flippant joining of what others have suggested, but would

rich-ui

work ?

Perhaps a little brief, but it is the richness of the interface that distinguishes it for me.

[mpf82]

Concerning your considerations:

1. I totally agree. I'd say, targeting browsers that fully support ES6 should be enough: https://caniuse.com/?search=ES6

2. flex grids 👍

3. agreed, by now everyone who writes JS should be familiar with arrow functions

4. Please, please, please do not write code w/o semicolons. Please do never rely on ASI.
   https://stackoverflow.com/questions/444080/
   https://flaviocopes.com/javascript-automatic-semicolon-insertion/

5. -

6. Personally, I've never used kickstart

7. Would dropping JQuery not make things like namespaced event handlers hard to implement in vanilla JS?
   e.g.: .on('mousedown.w2color', function (event) {

8. - 10. 👍

---

Suggestions:

1. Consider to use ESLint for clean, uniforn, consistent code.

We, as a company, decided to use ESLint with slightly modified AirBnB rules after reading through your contribution requirements

It's not hard to set up and really helped us to enforce consistent JS code in all our projects.

ESLint in combination with VSCode can format and (for large parts) fix most of the rule violations automatically when you save your file.

If you include a .eslintrc.js in the project (dunno if root or in the source dir would be better) then most contributors could use that to make their contributions follow those same rules and you would not have to worry about inconsistencies.

If you want, I'll be glad to show you what our formatted code looks like and which ESLint rules we're using.

2. Consider to use babel to generate backwards compatible code.

That way, you can use arrow functions, classes and pretty much all ES6 features you want in the sources, while you still have the option to create a ES5 compatible version of the library.

[vitmalina]

4. Semicolons..... )) Well, your second article was interesting. I have been not using semicolons for a year now in all my new projects. Frankly, I find code much cleaner w/o them and I like the look. I do use semicolons, but only when they are needed, which is rare. Yes, there are edge cases, but I did not encounter any issues this past year. I have requested my team mates to do the same (they are younger people, just few years out of college) and we like it. Plus, I think it is a definite trend in Node community. Did you have any negative experience with them in your coding (or team) personally. Why such strong reaction?
5. "-" what does it mean, you do not agree with it. Gulp 4 is much superior to Grunt or Gulp 3. One thing I like in particular is now I can write my custom gulp modules right there in the code and I can control when task is complete and setup serious of tasks which do not start before previous ends - which is huge.
6. I use kickstart everywhere for lazy loading and routing. I like that it is very simple. However, I am open to switch to js modules (last I checked, they were not ready yet). Though still routing is a need. I can give you a demo on kickstart, but I think I moved it to its own repository https://github.com/vitmalina/w2ui-starter

Also, I just thought of a new thing, what about to switch to class instead of classical objects. I do like the new syntax. ))

From you list

• ESLint is good. Like it.
• Bable - not sure if it is needed if we target ever-green browsers. But anyone can babble the code to try to use for older browsers ))

[mpf82]

4. Actually, no, we did not have bad experiences due to the lack of semicolons yet. But I'm really afraid of the edge cases. We've set our ESLint rules to automatically add semicolons when the file is saved, so currently there are no "missing" semicolons in our code base. But it's just a matter of setting the ESLint rule /*eslint semi: ["error", "never"]*/ and all (unecessary) semicolons get automatically removed from the code. See: https://eslint.org/docs/rules/semi (one more reason to us ESLint).
   Actually, you might be right, the code does look cleaner w/o semicolons, I'll ask my colleagues if we should switch.

5. No, sorry, it only meant that I have no opinion about it, because we haven't set up JS tests for our files yet and so we've got very little experience when it comes to gulp or grunt. Currently we've only got Python unit tests and we're only running Selenium tests for our application as a whole. Unit tests for individual JS files are still on our list.

[ceedriic]

I think this is fantastic news.

One remark about the two things you consider (pt 4 and 7):

• Please, yes, get rid of JQuery. Each time I've to debug some complicated issues in our application which uses w2ui and the debugger jumps into JQuery code, it becomes impossible to follow what is going on.

• Please, yes, let's move to classes. it makes large codebase so much easier to understand and follow.

Note: I just did that last year with one of our JS application (removing JQuery and moving the codebase to classes). The resulting code is much easier to understand, work with and debug than before.

[vitmalina]

jQuery selector engine is amazing. No question about it. I use it in my other project and I cannot do w/o it. However, in w2ui, the use of jQuery is minimal. So, I will probably use jQuery in all my projects, but for w2ui purposes, we might get rid of it. ))

[maucrvlh]

I am very happy that this project is alive and growing up! Thanks, @vitmalina and all the contributors.

As a suggestion, I think adopting typescript would be a good ideia, allowing us to write code in a more readable way and compatible with good project patterns like SOLID.

[vitmalina]

Not sue that we need TypeScript, however, anyone who was to use w2ui in a TypeScript project will have no issues ))

[martin-pabst]

I agree with maucrvlh: I love w2ui, but if it would be written in typescript (or at least if it would provide a typings-file) it would be a great improvement as IDEs like VSC would give us much better code completion and many bugs could be eliminated at compile time.

[mpf82]

@martin-pabst / @maucrvlh I've recently flagged a typescript related issue as "Feature Request" and "Help Wanted": #862

The issue already includes a link to typescript 2.3 definitions for w2ui 1.4.3

[vinhpt2]

1. postgREST .org is a great OData for Postgres database. It is nice if w2ui support postgREST for remote datasource (for Grid, Form...).
2. real Tab not only Tabstrip
3. Modern style w2slidebar
4. Multi-level dropdown menu
5. Collapsible group of Form
6. add span property of Field that allow field span multi-column (now need html design to do this)
7. support Image Field
8. new Tree control
9. new List control
10. new Dialog (modal and modaless) control that allow show multi-dialog at a time (Popup messy to use as dialog)
11. new Toast-like (notification) control
12. new Pivot-grid
13. add .box property (domNode) for every items (part) of control (this allow developer easy to change item domNode at runtime)
14. Build class for every items of control so developer can easy to manipulate with them (It important in the projects that need generate control and items at runtime)
15. Auto control's name (id) manage. Developer hard to ensure name (is) is unique we can get the name after call construction.
16. About the name w2ui I think should not change. It is the famous one now!
    Any way thanks @vitmalina for great w2ui!

[mpf82]

Great suggestions. I've also suggested pivot tables in a personal email to Vitali.

One of your suggestions (Collapsible group of Form) is already implemented in the current master: field.html.groupCollapsable

But it seems a bit buggy with lists that have icons:

And what do you mean by support Image Field?
You can easily create a preview for a field of type file:

And if that's not what you want, you could just write your own custom w2field type.

Here's an example of a custom field I've created (it's an icon picker with preview):

[vitmalina]

Thanks for suggestions.

1. w2ui is client side only. If you fell like it create w2ui-postgres for server side implementation
2. possibly
3. sure
4. already there
5. already there
6. already there
7. there is field type HTML and you can implement images there too
8. sidebar can be a fully functional tree (see examples)
9. not sure what you mean ))
10. See Window component #283 - suggest w2poup.message
11. not sure
12. need examples
13. not sure
14. not sure (architecture is different, all objects are in w2ui and can be accessed and manipulated)
15. name is already unique
16. ))

[vinhpt2]

Thanks for suggestions.

1. w2ui is client side only. If you fell like it create w2ui-postgres for server side implementation

• postREST (not postgres db) is REST API allow read-write data to postgres database. It follow OData standard that use GraphQL syntax and OPTIONS, GET, HEAD, POST, PATCH, and DELETE http query. For example now w2ui use in-house search structure to query data (that the server-side must follow), if replace (or add more) w2ui's search structure that meet OData standard, w2ui will can be working with other OData supported server-side (postREST is one of OData server-side)

2. possibly
3. sure
4. already there

• I mean multi-overlay of menu like this https://bootstrap-menu.com/demos/multilevel.html

5. already there
6. already there

• I quite miss please show me how to span a field multi-column in w2form by construction only (not in html). By the way please add default value for field in construction (not in html)

7. there is field type HTML and you can implement images there too
8. sidebar can be a fully functional tree (see examples)

• Yes sidebar can use as tree, please add support checkbox to check the node like this https://ant.design/components/tree/

9. not sure what you mean ))

• I mean the control can view data like Window Explorer (large icon mode) right panel. (can do in w2layout that support table-layout or more type of layout)

10. See Window component #283 - suggest w2poup.message
11. not sure
12. need examples

• This is a good example: https://www.webdatarocks.com/demos/javascript-pivot-table-demo/

13. not sure
14. not sure (architecture is different, all objects are in w2ui and can be accessed and manipulated)

• Please have a way for example how to change the image (or change state) of button in the w2tool when user click it.

15. name is already unique
16. ))

[vitmalina]

• PostRest - if you with to do it, try in a different branch and submit a PR. There is already a choice how data can be transferred, see dataType in http://w2ui.com/web/docs/1.5/w2utils.settings
• inside of a menu item define items: [...] and it will be nested. it is not covered by documentation, but it is there. see http://w2ui.com/web/demos/#!utils/utils-5, click Show Menu
• demo page for forms got update, see what's new http://w2ui.com/web/demos/#!forms/forms/10
• checkboxes in trees, I implemented something like that. Will share code, here is screenshot

- grid view cards is not very hard to implement by itself, it might or might not be coming as part of grid. - as for pivot tables, if someone can implement it, it would be cool. I fail to see what it is.

[Rimokas]

Good news! :)

I agree with vinhpt2, that W2UI already is NAME, so why it change? What is wrong with that ? In mine opinion it must be easy to do some changes in your w2ui.com page - redirect to jQuery based 1,5 version or redirect to new 2.0 version. Angular in versions from the first - it diffs very, but in names they leaved the same "Angular". Or better to rename old 1.5 version to w2uiJQ - as jquery based ...

[mpf82]

Suggestion: use popper as the foundation for the new w2overlay.

It's light weight (3 kB) and MIT.

I know you do not like dependecies, but why re-invent the square wheel?

The compiled w2ui.js could come with popper already included, so no inconvinience for the w2ui users.

[ceedriic]

Good idea.
Popper is already the only dependency of bootstrap 5, for example.

[vitmalina]

Likely. I think it deserves a closer look. Popovers were a source of grief for me in w2ui. So, if this component works - it would be awesome. Will evaluate.

[akg83]

1. As for a new name, I'd say those of us that have utilized W2UI in projects, already know it by it's name, I can understand the need to keep with the current trend, where every library seem to have a really "cool" name - because some developers seem to be leaning towards "cool" sounds buzz words, if it was me I'd stick to the W2UI name. but as for if I'd really have to come up with a name - I'd just look into all other library names out there (about a million of them) and check which buzzword or term is still "free" for grabs :-)

2. Other than modernizing of the source code, do you have any plans for enhanced functionality of the existing components? or adding other components? Have you considered the possibility of adding a built-in localization feature to the core components?

@vitmalina A very strong point, which I hope will be addressed, is backward-compatibility for the major components such as Grid, Toolbar and Sidebar.

I can confirm that I know of at least a handful of companies, that are using w2ui for many of their internal tools and have built pretty sophisticated UI combinations using it, and if the new 2.0 Release will force people to invest many hours into re-writing code that is already pretty complicated and is running in production, it will make little sense to upgrade, and might push people to migrate to other libraries - which will be a shame, since w2ui is a great little library which have almost everything you need, and nothing you don't need :-)

IMHO the ideal situation is to have the basic formatting of most components to have backward-compatibility, but since that might be too much work, i'd say at least the most major components such as Grid, Toolbar, Sidebar and Tabs needs to retain backward-compatibility, at least for the first release of 2.0

Just my 2 cents

[vitmalina]

1. :)
2. Localization is already built in (http://w2ui.com/web/docs/1.5/w2utils.locale). I do not think there will be more components, but feature-wise, yes, new features/improvements will be coming. There were already many done, but documentation is not always up to date (. We keep notes in top of source code what is new and not yet fully documentation.

Backward compatibility is a goal, but not 100%, meaning that API and syntax definition will be nearly the same. I think it hinders development if all previous use-cases must be supported. There will unlikely be breaking changes, but testing must be done with version update.

I completely agree with your 2 cents )). Updating to new version should not be a headache. But also,

[akg83]

Thank you for your reply, yes I also believe that since your library has became pretty popular for some users, which I believe would love to keep the library up to date, will be very happy if the update process will not be painful (sure, it can not be 100% compatible, but I'd say - if the common components and their basic functionalities will have a 100% backward-compatibility that would be sweet, and then by the next 2.1 , 2.2, 2.x releases .. slowly phase out certain things and refactor them into a newer architecture, if it can be described like that) :-)

One feature which could be cool, and correct me if I am wrong and it is already possible :-) is to be able to inter-connect components so they have a common communication channel, for an example: combing a layout, a grid list, and a form, in such a way that information and events could flow to and from the grid list and the form and etc.. pretty much overall make the independent components being able to get integrated to one another with some sort of common interface which will allow the easier creation of the more complex combinations

[jchlagrand]

I would like to suggest integration of w2ui.form and w2ui.grid.
Never understood why w2ui.form is limited to one record and interfaces differently with the server.

[vitmalina]

What kind of integration you propose? How can I form be editing more then one record? If you want editable grid - then this feature is available in grid. What do you mean interface with the server is different. It is similar. Possibly, I do not understand what you mean. )

[akg83]

@vitmalina I think he/she maybe tried to suggest something like a grid > record functionality, so a grid component could be configured in such a way that when you click a record, a side pane is being opened, and your selected row will be displayed as a "record". I know it is possible to create using a combination of layout, grid and form components.. but maybe he meant to make it possible to be a core grid feature so using a certain configuration of the grid component this would be automatically integrated (e.g. config a grid components with some flag e.g. "recordView: true") ? maybe I am wrong.
but like you, I do not understand how a form can display more than one record at the same time?

[jchlagrand]

Editable grid, of course, but with a cell that contains all form elements of the same form column number. A record(/datasheet)View flag would strip the fancy form formatting I guess. I believe 'continous form' would be the property in msAccess to either scroll all forms using the scrollbar or display a single record/form and use navigation buttons.

[vitmalina]

http://w2ui.com/demos/#!combo/combo-3 - editable grid
http://w2ui.com/demos/#!combo/combo-2 - grid -> edit record

I do not have a clear picture in mind how it could be done in a generic way so that it could be part of the grid. Perhaps, if one could create a demo, it might be helpful.

[mirannda]

First, I would like to congratulate @vitmalina and the contributing members for their magnificent work.

Well, I like the approach that http://kube7.imperavi.com
there are, I have studied several others and so far there is nothing like W2ui and Kube.

Okay, others have a few more components and offer some extra functionality, but with simplicity and focus, there isn't.

Well, I'm not the owner of the truth, but that's my opinion.

[vitmalina]

Did you see this? https://github.com/vitmalina/w2ui-starter

[mirannda]

Yes, I saw it, I thought it was really cool, it even has a certain approximation of what I mentioned.

Thanks!

[akg83]

@vitmalina

1. Not sure if this is feasible, but how about a more integral support for themes ? doesn't have to be something too elaborate, but some way to centrally modify the color scheme, icons etc ? I have already seen the dark theme, but it looks incomplete.

2. This is a big one - how about offering optional functionality to connect certain components (e.g. grid, form.. ) using websockets (or something similar) so whenever updates are committed on the server, the components will automatically react to the changes.

[vitmalina]

1. Yes, there is a dark theme, but frankly, I did not look at it for years (. Some work on this regard would probably be nice. Not sure. In my projects, I found that I create custom theme tailored for each specific project by just overwriting some css classes. Seems to work well for me.
2. There is already way to extend w2ui objects (http://w2ui.com/web/docs/1.5/utils, find w2obj). I use it occasionally. Not fully happy about it. Possibly class ... extend would be a better way. Need to consider.

[akg83]

1. This was also how I did it a few times, created a special file where I used to overwrite colors, padding, margins etc.. to fit the interface for the project- after the long and tiresome fiddling was done it worked great :-) however it was cumbersome and IMHO isn't really a maintainable approach.
   I'd suggest that re-engineering the library to accept modern best practices for theming might be far fetched or at this point less of a priority, but maybe just improving the possibility for creating new themes, with at least the ability to change the color scheme and the icons, using some kind of a generic format (repeatable), so have a common "interface" to new themes, for an example a "themes" folder where inside there would be a subfolder for each theme, and say each theme folder will consist of two files, one for defining the color scheme and the other for icons - then for configuring the UI for a specific theme, as a parameter of some type of a Top-Under component such as "Application", for an example.
2. Extending the objects is great, however I was talking about adding (at list for the major components) a native feature of being able to connect it to an end-point and have the component listen for changes and auto update the view when any new changes are available (for an example: Having a cloud-based phone book in a grid component, and one of the contacts that are listed were modified, imagine the grid registering on that change and auto updating) - this could also be implemented as a separate w2ui component that could then connect specific object to such event listener (e.g. a "DataWatcher" component), I could offer my contribution help if it would be made possible.

just throwing some ideas :-)

[mirannda]

As a suggestion:

1. w2ui-layout to w2ui-admin
2. add notification system with: websocket, sse ...
3. customization of themes
4. incorporate w2ui-chart and w2ui-listview (load-on-demand)
5. w2ui-treegrid (with on-demand loading)

[alexrjs]

What about these names:
dezianUi - Dezain = design in japanese
sekkaiUI - Sekkei plan, layout in japanese
sakUi - Sakui idea, conception, motif, intention in japanese

I used https://www.wordhippo.com/ and japanese, since english, german, french, already overused... Maybe you find someting in japanese words ;-)

[gitgitwhat]

Love w2ui and really looking forward to 2.0.

Some suggestions:

-Implement basic charts and graphs. This would be huge.

-Easier i18n support.

-Personally I like the look and feel of the current elements. It's clean and tight unlike other UI frameworks. The image posted above is hideous so please don't go that direction. But making it a bit easier to modify the overall theme would be nice.

I'm not that clever with naming but here are some thoughts.

RenderUI (.js)
BaseUI (.js)
wAppUI (.js)

[ahmedoashery]

Maybe:
Qui , Q-ui or QuickUi
as quick ui , and they are first 3 letters of the word itself

FastUi - is amazing too 👍🏻

please consider adding RTL support
Thanks , it’s a great ui library

[ika]

I like the idea of dropping jQuery as a dependency, but I would still need the jQuery Ajax support, which I use a lot. As far as a name goes, we already have "Angular" so why not something like "CornerStone".

[H-Lo]

Hi!
On my local machine I created some additional functions for w2ui 1.5 Grid - handling keys PgUp, PgDn, Home & End.
Should I create pull request or just leave it as it is?
With PgDn & End autoload is also triggered and I thing user experience could be called "ok".
BR,
Hrvoje

[vitmalina]

Please create a pull request.

[vitmalina]

As for name, yes, we decided to keep it

[H-Lo]

I'm using 1.5-rc1 for my project and all customizations are made on this one. Now that I downloaded version 1.5 I can see there are thousands of differences comparing to rc1.
So I cannot just copy from one to another but I have to see exactly what changed and where to inject my code to handle additional keys. It could take some time and now I wonder about version 2.0 - are there any ideas when it can be made?

[mpf82]

@H-Lo you can already download w2ui 2.0 from the master's /dist folder: https://github.com/vitmalina/w2ui/tree/master/dist

There's also a migration help: #2015

The only breaking change is probably w2grid no longer sends "get" as a default command, and "delete" / "save" have been moved from "cmd" to "action"., other than that, w2ui 1.5 should be mostly compatible with w2ui 1.5rc1

[H-Lo]

@mpf82 Hi! It's not that I don't know how to migrate but I did some changes to my local version in order to use PgUp, PgDn, Home and End keys and that part of code should be applied to new versions and provided as pull request. That part is tricky because there are thousands of changes in code, at diff level not mentioning functionality. As I had to change some existing code a bit, first I have to analyze those new versions and see is it possible to apply my code and if it is possible, then find the right spot to apply it. The pull request for 1.5 RC1 would be really easy because that would be just few changes, but RC1 is outdated and that would be forcing someone else to propagate my changes to newer versions. And I'm aware it wouldn't be nice thing from me :)

[H-Lo]

Hi @vitmalina , it's me again :) This time I have an idea about new feature that might be not too complex.
In some cases header of a table is redundant meaning the table is placed the way it is already clear what it displays.
So it would be great if configuration parameter "header" could take false as a value not displaying text "false" as a header but to remove the whole header leaving more space for rows.
As you can see it's not a crucial feature but it could help.

[mpf82]

Are you looking for grid.show.header? http://w2ui.com/web/demos/#/grid/3

[H-Lo]

Are you looking for grid.show.header? http://w2ui.com/web/demos/#/grid/3

Yes! Thank you!

[mcjp518]

v4ui,"v"is your name."4" is "for"

[ooo4321]

maybe combo field - group , with 3 param array ? something like :

[gpetrov]

@vitmalina I see great progress with w2ui 2.0 and its conversion to es6 but no signs of any jquery removal while this was one of the primary goals.

Is jquery dependency removal still on the roadmap? It is a very important goal for the future.

Also I still see a lot of size calculations and manual resize with timeouts in the code - this really should be addressed and all the CSS styling should be modernized and take advantage of flex grid and even css grid, to provide smoothest responsive UI, without any manual css recalculations. This is also very important for the future of w2ui.

[vitmalina]

Oh, perhaps, my friend, you are not looking in the right branch. See what checked in into branch tooltip. I started with classes that are basic and I feel jQuery can be removed from there first, which is w2utils, w2tag, w2overlay and w2popup. Also, w2tag and w2overlay (or tooltip) needed to be refactored as it organically grown and has a lot of repeating code (w2tag and w2overlay can be merged) and it would be nice to have it es6 way. It is definitely underway, I hope it will be done within 3-5 months. If you have some spare cycles, you can help, as there is a plan how to do it now. Basically, I created a tiny library that would replace jQuery as far as DOM manipulation and events are concerned, see https://github.com/vitmalina/mquery (give me a star :) ).

You are right on the point with CSS and size calculations, I cannot agree more. This work is underway too. Most of classes (except w2grid and w2form) are already using flex grid and table less designs. Those two I mentioned would be last to go, I suppose, as grid has many many man points where it can be modernized.

You seem like a smart guy, find me in telegram https://t.me/vitmalina, let's chat.

[gpetrov]

Thanks Vitali, will connect.

Your jQuery replacer wrapper looks great! Maybe you should call it w2query btw :) there are thousands mquery projects available...

Also for positioning specially for tooltips and such, you might want to use something like: https://floating-ui.com/ and not the heavy duty isMoved that you now have for checking constantly if something has gone. Which is very heavy and forces redraw.

Also ideally - the resize() w2ui api functions shouldn't be needed any more - everything should resize itself automatically in the dom with css.

[vitmalina]

Oh, I did not know there were so many mQueries, but looking at them they seem not to be dom manipulation libraries.

As for floating UI - looks interesting, will analyze. As for isMoved - agree, a better solution would be cool. I have been thinking that I can listen to dom mutation events. Then no timeout needed. Will check it out, thanks for the great idea.

As for resize - agree too. Need to evaluation how it could be removed

[vitmalina]

Just a follow up. Tooltip has been refactored completely. No longer has isMoved, but used dom observer if anchor changed, resize observer is used if tooltip size change, which is a nice and very clean solution.

[ac-73]

What about HeAL UI (Heavy App - Light UI)?

[vfp3786]

I hope the second version from w2ui is support the Arabic language, such as the direction from right to left.
please ..

[vitmalina]

It should already be supported

[vfp3786]

not working rtl

[Mimu1988]

Hello @vitmalina,

Love w2ui and using it in some of my projects.
I would like to suggest a feature i implemented myself in my local w2grid sources so that the user can search directly in the columns.

Supported search types currently are Text, DropDown and Checkbox.

Thanks,
Michael

[vfp3786]

Hello @vitmalina,
Support Right-To-Left Like This Picture

[foxpcteam]

@vitmalina Hi, any plan to see RTL Support in V2.0?

[mundizzle]

Consider using Vite instead of Grunt/Gulp

[vitmalina]

Thanks for the suggestion, but gulp is sufficient, as all it does it minify and bundle.

[H-Lo]

@vitmalina
This time I don't have any request, but just to say W2UI is a great thing and I enjoy using it. Thanks for your time and effort!

[vstiebe]

Congratulations on the great library!

1. Yes! For legacy you can pin a tag or branch "last tag/branch for legacy browsers".

2. If it is open to voting, my vote is for using classes and to keep using explicit semicolons. Letting the compiler decides when to end a statement isn't future proof. And some weird cases arises: https://javascript.plainenglish.io/javascript-how-line-breaks-and-missing-semicolons-can-break-your-code-58e031e7f235

3. I like the actual look and feel because it is more system oriented and less web oriented and also because it is compact. Modern look and feel like primeng or bootstrap are very pretty and good for tablets or web forms. But for a "desktop web application" the actual look and feel is great.

[vitmalina]

1. There is a branch for 1.5 version, it plays a role of a legacy branch
2. Have been writing without semicolon for more than a year now. No problem. The only thing is when a new line starts with ( which could be considered as a function call. But once you know this, life is easy. I do like the clean code without it. It just looks cleaner.
3. Agree, but I think we need a dark theme too :) and and updated initial template with left side icon bar (https://github.com/vitmalina/w2ui-starter-es6)

[H-Lo]

Re 2) - it can work but definitely my vote goes to semicolon - those few bytes won't change file size radically.

[Kreijstal]

maybe consider CI Jobs, which can help with things such as gulp for every commit, separate the source code with the distribution code, the distribution code could be made available in github releases and/or npm and wouldnt be distributed on the repository

[Kreijstal]

Have you heard about https://github.com/storybookjs/storybook you could add your library as a story in storybrook
https://storybook.js.org/showcase/projects and no you dont need react or a framework to do it.