Commit 41f87ea1 authored by Daniel Brötzmann's avatar Daniel Brötzmann
Browse files

Post: Fix some issues in Workspace Preview

parent 003c4e74
Pipeline #8153 passed with stage
in 1 minute and 44 seconds
......@@ -31,7 +31,7 @@ Gajim v1.4 will introduce a new concept: **workspaces**. Previously, all tabs we
A workspace is a collection of group chats and private chats, organized client-side. For the moment, this is a non-standard, Gajim-specific feature, but standardization efforts are explained in the **Areas for improvement** section.
We introduced a new fixed-width sidebar on the left of the window which allows to navigate your workspaces and accounts (**workspace list**). After clicking any workspace, the **chat list** will be displayed in the sidebar. This chat list, to the right of the **workspace list**, provides navigation for chats (both group chats and private chats) within the current workspace. The currently focused workspace has a colored bar indicating it's the current context.
We introduced a new sidebar on the left of the window which allows to navigate your workspaces and accounts. After clicking any workspace, the **chat list** will be displayed in the sidebar. This chat list, to the right of the **workspace list**, provides navigation for chats (both group chats and private chats) within the current workspace. The currently focused workspace has a colored bar indicating it's the current context.
Below the workspace list, the sidebar lists your accounts. Clicking an account will display a page containing the **contact list**, your avatar, a status selector, and a list of pending notifications. Contacts in the contact list are organized by _roster_ groups, as was already the case in previous versions.
......@@ -39,7 +39,7 @@ Below the workspace list, the sidebar lists your accounts. Clicking an account w
Each account is attributed a specific color, in addition to its avatar. This color is reused in the **chat list**, alongside the tab's avatar so you can see instantly which account of yours is used in a specific chat. When a given chat/account doesn't have an avatar defined, one is generated from the first character of its displayed name.
{{< figure src="/img/news/workspaces-preview-2.png" caption="Gajim’s with multiple accounts">}}
{{< figure src="/img/news/workspaces-preview-2.png" caption="Gajim with multiple accounts">}}
When a notification is received within a certain workspace, an indicator with the number of unread messages will be shown on the workspace icon and on the chat.
......@@ -55,12 +55,12 @@ Within a given workspace, chats can be **pinned**. These stay in place at the to
There's a lot of upcoming major changes in the next Gajim v1.4 release, so stay tuned to the blog for further information. In the meantime, you can test the new interface by running Gajim from sources using just a few commands. **This feature is not published in nightly releases yet because it's still unstable, so do not use it as a daily-driver yet.**
**Important:** Note that you have to start Gajim with a test profile using `gajim -p testprofile` or `launch.py -p testprofile` in order to preserve your current profile. Migrating back is not possible.
**Important:** Note that you have to start Gajim with a test profile using `gajim -s -p testprofile` or `launch.py -s -p testprofile` in order to preserve your current profile. Migrating back is not possible.
- `git clone https://dev.gajim.org/gajim/gajim && gajim` to download Gajim's source into a `gajim` folder and moving there
- `git checkout mainwindow` to browse the development branch with the new UI
- `pip install .` to install Gajim's development version and all dependencies to your python environment, then `gajim -p testprofile` to start
- alternatively, `./launch.py -p testprofile` to start Gajim without installing it, in which case dependencies should be manually setup first (for example [On Ubuntu](https://dev.gajim.org/gajim/gajim/-/wikis/development/Ubuntu-Development-Setup))
* `git clone https://dev.gajim.org/gajim/gajim && cd gajim` to download Gajim's source into a `gajim` folder and moving there
* `git checkout mainwindow` to browse the development branch with the new UI
* `pip install .` to install Gajim's development version and all dependencies to your python environment, then `gajim -s -p testprofile` to start
* alternatively, `./launch.py -s -p testprofile` to start Gajim without installing it, in which case dependencies should be manually setup first (for example [On Ubuntu](https://dev.gajim.org/gajim/gajim/-/wikis/development/Ubuntu-Development-Setup))
Feedback is welcome in any form, whether on [our issue tracker](https://dev.gajim.org/gajim/gajim/-/issues), in our community chat [gajim@conference.gajim.org](xmpp:gajim@conference.gajim.org?join), or as a blog post on your own website. The main tracking issue for this new user interface is [#10628](https://dev.gajim.org/gajim/gajim/-/issues/10628).
......@@ -70,7 +70,7 @@ In this section, we explain the shortcomings of the current implementation of th
### Accessibility
Activity notifications account context rely on user-supplied colors. However, for accessibility concerns (color-blindness), we would be interested to support other graphical patterns instead of colors. For example, dots and dashes and other visual patterns that are common in graphs and tables. However, unless we get more contributions, it's unlikely this feature will be released in v1.4.
Account context relies on user-supplied colors. However, for accessibility concerns (color-blindness), we would be interested to support other graphical patterns instead of colors. For example, dots and dashes and other visual patterns that are common in graphs and tables. However, unless we get more contributions, it's unlikely this feature will be released in v1.4.
### Internationalization
......@@ -90,7 +90,7 @@ Only your imagination and contributions to the Gajim project are the limit for t
Currently, pinned tabs in the **chat list** cannot be reordered in the way that workspaces can be in the **workspace list**. Would this be useful for you?
Moreover, Gajim's new workspaces UI currently features a 2-level representation like Mattermost, where any chat only has a single ancestor workspace. The account roster is an exception, because features a 3rd-level nesting in order to fit roster groups, where each entry is part of a group, which is part of the account workspace context. Maybe workspaces could benefit from this approach in order to represent 3-level hierarchies akin Discord/Element interface.
Moreover, Gajim's new workspaces UI currently features a 2-level representation like Mattermost, where any chat only has a single ancestor workspace. The account roster is an exception, because it features a 3rd-level nesting in order to fit roster groups, where each entry is part of a group, which is part of the account workspace context. Maybe workspaces could benefit from this approach in order to represent 3-level hierarchies akin Discord/Element interface.
Also, a chat can currently only be featured in a single workspace, for the sake of simplicity. That's a fine assumption as long as workspaces are managed by a single user for their needs, but would not play well with sharing workspaces with other users, in which case a chat may appear more than once in the workspace tree.
......@@ -102,6 +102,6 @@ Sharing a workspace with several users, similar to Matrix "spaces" or Discord "s
While there is not yet a specification for such hierarchical organization of chats in the XMPP ecosystem, there was an [XMPP Online Sprint](https://wiki.xmpp.org/web/Sprints/2020_November_Online) last winter studying Discord's user experience in order to benefit the Jabber/XMPP ecosystem.
More recently, some people have started to gather thoughts that should lead to a specification. There is [a work-in-progress document](https://md.roflcopter.fr/xmpp-spaces) (a [pad](https://en.wikipedia.org/wiki/Collaborative_real-time_editor)) which anyone can edit with feedback, and a [spaces@joinjabber.org](xmpp:spaces@joinjabber.org?join) chatroom has been setup to discuss this issue in a cross-project manner. Your ideas and contributions are more than welcome, even if you're not familiar with the Jabber/XMPP ecosystem. Feedback on how a new specification could be made interoperable with other decentralized networks is very welcome.
More recently, some people have started to gather thoughts that should lead to a specification. There is [a work-in-progress document](https://md.roflcopter.fr/xmpp-spaces) (a [pad](https://en.wikipedia.org/wiki/Collaborative_real-time_editor)) which anyone can edit with feedback, and a [spaces@joinjabber.org](xmpp:spaces@joinjabber.org?join) group chat has been setup to discuss this issue in a cross-project manner. Your ideas and contributions are more than welcome, even if you're not familiar with the Jabber/XMPP ecosystem. Feedback on how a new specification could be made interoperable with other decentralized networks is very welcome.
[![Gajim](https://conference.gajim.org:5281/muc_badge/gajim@conference.gajim.org)](xmpp:gajim@conference.gajim.org?join)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment