Dev talk:Ref/Outdated/Proposals/Usability Project
Panels
BTW, the problem with tablet users reorganizing the panels should be minor, as the active area for dragging is pretty small (the widgets that looks like a resize control) and most of the header is about collapse now. If people click randomly to have such issues, lots of other things will break earlier. (Side note: maybe that widget should change to something that implies move, instead of common resize diagonal lines/dots. Same issue for the corner areas in all views, if just not remove them, as they overlap other controls, have no hint about purpose or avaliable keys, and frame menu makes them redundant). Gsrb3d 02:26, 22 January 2012 (CET)
Panel header has a bigger text than other things but it looks more related to the thing above than the ones below. The horizontal line helps notice they are separate things, but the blank space between title and contents works againts that. Maybe it should be removed (down to normal spacing), it will for sure reduce scrolling a bit. Gsrb3d 21:07, 23 January 2012 (CET)
Toolbar
Last operator workflow
Last operator workflow is strange. For some things it acts more like current operator, you activate some cmd, type things and commit. And when working as last operator, if you want to do something with total control, you have to do something random without feedback, then the panel contents appear. Compare add torus vs grab. No idea how/where to put that, other than it is a convoluted interface, and maybe could require some core changes so semantics are standard (select item - action, vs action - select item). Or from another point of view, some cmds are pretty rigid without operator panel or invoking the popup by hand (add torus) while others can work rather good if not 100% without it (grab). Gsrb3d 01:54, 22 January 2012 (CET)
- Another issue: when undoing/redoing, it seems to be unavaliable. Half designed/implemented concept or luckly a solvable bug? Gsrb3d 22:41, 30 January 2012 (CET)
Relations
OOPS
Should not OOPS allow editing relations? Instead of being just a view, it should allow changing those things that it could control. Gsrb3d 00:37, 22 January 2012 (CET)
- added to the page, feel free to add this stuff in the page your self :) --mindronest 00:39, 22 January 2012 (CET)
Page approach
small suggestion: a lot of the framework is in the form problem-solution: while that is true in some specific cases, in general, there are trade-offs: the solutions solve some problem, but result in some side effect. I think an honest appraisal would have : problem-solution-tradeoffs
this would allow: honest appraisal of the solution, and is a non-combative way to discuss, since most (every?) solution will probably have some trade off.
