Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Window component #283

Closed
mokry opened this issue Oct 17, 2013 · 4 comments
Closed

Window component #283

mokry opened this issue Oct 17, 2013 · 4 comments

Comments

@mokry
Copy link

mokry commented Oct 17, 2013

Hi,
I would suggest to make component based od Popup, but more like windows.
Sth like windows in dhtmlx (http://docs.dhtmlx.com/doku.php?id=dhtmlxwindows:toc)

@vitmalina
Copy link
Owner

Appreciate your suggestion. IMHO multi window is a bad UI decision. It works good if you are writing multi application environment, such as a desktop, but it does not work good for a single application. I think a better UI solution is paneled layout. I think problem with multi window are:

  1. Messy navigation. If you have 10 windows opened and you want to switch from a window to a window it requires (a) precise mouse movement to click the right one or (b) hitting variable number of times on ctrl+tab to get the window (c) stop and use your brain cells to think where in the menu is the list of all opened windows. All of these activities require user to think about UI not about his project.
  2. Messy resize. If user has to resize the window (beyond clicking on max button). It requires (a) moving mouse to a precise position to grab the corner to resize (b) thinking about how much do I need to resize to and tying to make a decision and (c) once resize, you might now need to grab the window and move it upward.
  3. Messy environment. If you want two windows on the screen positioned next to each other you need (a) move first window (b) resize it (c) find second window (d) move it to proper place (e) resize it. This is too much for a user to do.

So, as you see, multi window UI creates usability issues. You are welcome to write out your arguments.

@mokry
Copy link
Author

mokry commented Oct 18, 2013

I think that yours argument are convincing, and maybe using a paneled layout is good solution and I'm using it for now.
But I think that in w2ui should be any component which one could open more than only one Popup. Why?
In my applications I really often have to choose repeatedly nested elements for ex. in forms. Then I must open Popup for select option (or my dictionary class field). When Popup is shown there is another select or dictionary field which one could open next Popup. And believe me, It's not bad designed. It's really much data (over 10,000,000 records) which one are connected and related.

Ps. Sorry for my English. It's not quite good ;)

@datanotion
Copy link

Good evening @vitmalina! I agree with you 100%, however sometimes the design is out of our control, and the customer requirements drive the need. Right now I have a client who requested an order management system and they want to be able to see multiple orders on the screen at the same time, in movable, minimizable windows. I offered a paneled type approach (like you suggested) but they want it "like their old system, because that is what they are used to". :)

I haven't gotten to the MDI interface yet, but it sounds like I had better try and see what @mokry is talking about. I might have to use a different library just for the MDI, but that is fine.

If it wasn't for the clients, programming would be so much easier!

By the way, I love W2UI so far!

@vitmalina
Copy link
Owner

Well, I guess I will need to make a decision on this one. I stick with one popup at a time option. Well, if you must have multi, there are other plugins for it already and I do not want to reinvent a wheel. Also, as of current master, you can create multiple overlays at the same time, you just need to give it a name.

Thanks for discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants