Review of "V-Shell (Vertical Workspaces)" version 46.0 (54)

Details Page Preview

Customize your GNOME Shell UX to fit your workflow, whether you like horizontally or vertically stacked workspaces. Originally Vertical Workspaces. Dear users, the reliability and stability of this extension is my priority, but V-Shell is an extension to default GNOME Shell and cannot be compatible with all available extensions. If you encounter any problem, first check for conflicts with other extensions and then open an issue on the Github page linked below. V-Shell includes many workarounds to survive conflicts and work with Dash to Dock / Ubuntu Dock extensions and other popular extensions, but issues may occur. The patched Dash to Dock for V-Shell is already available in my GitHub repository. Any feedback is greatly appreciated! V-Shell features: - vertical or horizontal orientation of workspaces - customize the overview layout, dimensions and contents - alternative overview modes with static workspace preview that reduces unnecessary movement on the screen - 4 predefined profiles with different layout and behavior that can be overwritten by your settings - wallpaper background with adjustable blur effect in the overview - dash icon size, content, icon click and scroll behavior - app grid dimensions, icon size, contents and behavior - active icons in the folder preview - close workspace button on workspace thumbnail - main panel position and visibility - hot corner/edge position and behavior - notifications, OSD and workspace switcher popup position - custom window attention handler behavior - improved app search provider with custom icon size - static background in the workspace switcher animation outside of the overview - independent workspace switching for each monitor (workaround) - workspace switcher popup appears even when switching workspace with a gesture - workspace isolated Dash - fixes (works around) several upstream bugs (known and reported) - modular structure of the V-Shell allows you to disable modules that you don't need or conflict with other extension that you like better for the task

Extension Homepage
https://github.com/G-dH/vertical-workspaces

No comments.

Diff Against

Files

Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.

All Versions

Version Status
46.0.1 (57) Active
46.0 (56) Active
46.0 (55) Rejected
46.0 (54) Rejected
44.11 (53) Active
45.3 (52) Active
45.3 (51) Inactive
44.11 (50) Inactive
44.11 (49) Inactive
45.3 (48) Inactive
45.3 (47) Rejected
45.3 (46) Rejected
45.3 (45) Inactive
44.11 (44) Inactive
45.2 (43) Inactive
44.10 (42) Inactive
45.1 (41) Inactive
45.1 (40) Inactive
45.1 (39) Inactive
45.1 (38) Rejected
37 Active
36 Inactive
35 Inactive
34 Rejected
33 Rejected
32 Rejected
31 Rejected
30 Inactive
29 Inactive
28 Inactive
27 Inactive
26 Inactive
25 Inactive
24 Rejected
23 Active
22 Inactive
21 Inactive
20 Rejected
19 Rejected
18 Inactive
17 Inactive
16 Inactive
15 Inactive
14 Inactive
13 Inactive
12 Inactive
11 Inactive
10 Inactive
9 Inactive
8 Inactive
7 Inactive
6 Inactive
5 Inactive
4 Inactive
3 Inactive
2 Inactive
1 Rejected

Previous Reviews on this Version

JustPerfection rejected
1. Timeout should be removed on destroy (line 281 `lib/search.js`): [EGO Review Guidelines: Timeout](https://gjs.guide/extensions/review-guidelines/review-guidelines.html#remove-main-loop-sources) 2. This package is 46 only. What's the reason for version check for barrier and style class name? For example in: - line 130 `lib/layout.js` - line 41 `lib/dash.js` - line 37 lib/appDisplay.js` 3. What's the reason for still including that while the comment says not allowed on ego (line 463 `extension.js`)?
GdH posted a review
1. Overlooked, copied from Shell 2. This package is 46 this time, but the code is 45+ 3. Forgot to remove before uploading to ego. Thanks.