Frontmatter
| id | 1386 |
| title | Refactor draggable.toolbar.DragZone into draggable.container.DragZone |
| state | Closed |
| labels | enhancement |
| assignees | tobiu |
| createdAt | Nov 4, 2020, 9:44 PM |
| updatedAt | Nov 4, 2020, 10:12 PM |
| githubUrl | https://github.com/neomjs/neo/issues/1386 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Nov 4, 2020, 10:12 PM |
Refactor draggable.toolbar.DragZone into draggable.container.DragZone
tobiu assigned to @tobiu on Nov 4, 2020, 9:44 PM
tobiu
Nov 4, 2020, 10:12 PM
Just hit the "rollback" button, was almost done.
while the idea is indeed good for containers, this would affect all other subclasses which extend container.
a sortable dialog would feel weird.
draggable for a dialog means, that you can drag it. for a toolbar this means that you can drag the toolbar items. so there is a conflict.
Closing this ticket, but will open a new one to create an example of a container using the toolbar.SortZone.
tobiu closed this issue on Nov 4, 2020, 10:12 PM
tobiu cross-referenced by #1389 on Nov 4, 2020, 10:13 PM
then we can use this feature for all (flexbox layout based) containers in general.
the same goes for draggable.toolbar.SortZone.