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

Add detailed section per client #40

Closed
bascht opened this issue Feb 16, 2017 · 14 comments
Closed

Add detailed section per client #40

bascht opened this issue Feb 16, 2017 · 14 comments

Comments

@bascht
Copy link
Owner

bascht commented Feb 16, 2017

I think there is way more info than we can cover at the moment (see #38). So – having a small section per client (maybe even with installation help / packaging status) below the table would be really nice.

@dreamflasher
Copy link
Contributor

Then let's add my proposal here: I think the release date would be very valuable information to add to this section.

@bascht bascht mentioned this issue May 8, 2017
@mimi89999
Copy link
Contributor

@bascht I think there should be multiple cases like: WIP, 1:1, MUC, File shareing and every would have like 25% and based on that, you would calculate the %.

@bascht
Copy link
Owner Author

bascht commented Aug 21, 2017

@mimi89999 The longer I think about the % the more I think we should go back to the old system of "sort by features". Having a single number is really nice (especially if it's 100%) but it can be quite misleading like @uchchishta attested over at #70.

Suggestion

(once we have detailed info per client)

We add checkbox filters on top of the table with say 5 distinct feature flags ("Experimental", "1:1", "MUC", "Encrypted File transfer") and by clicking those boxes the list of clients get's smaller and smaller (Ending up with Conversations as the only client once all boxes are ticked. 😬).

wdyt?

@mimi89999
Copy link
Contributor

mimi89999 commented Aug 22, 2017

@bascht I think the % can stay if:

  1. It is calculated based on those 5 features
  2. Feature list is accessible when going over with the cursor or clicking on it

Ending up with Conversations as the only client once all boxes are ticked.

Conversations and Gajim.

@bascht
Copy link
Owner Author

bascht commented Aug 22, 2017

Feature list is accessible when going over with the cursor or clicking on it

this introduces another interaction layer. If those are just green / red / gray boxes in a row, everything is visible immediately. I'm not emotionally attached to the percentage. 😬

@subpub
Copy link

subpub commented Aug 22, 2017

Can you put a 💯 next to a client if it supports all the three if you go with the filterable table?
Also n/a in a field, if a client doesn't do a thing at all

@bascht
Copy link
Owner Author

bascht commented Sep 4, 2017

@uchchishta I think that wouldn't even be necessary if we have columns for all features, no?

@ReneVolution
Copy link
Collaborator

Heyo, I have started to work on this. To find out if this kindof matches your expectations, please check the PR #85.

@lstrtstr
Copy link

+features:

  • single_chat: true
  • group_chat: true
  • encrypted_files: true

Thanks!
Two more features that should be listed, IMO, are Message Carbons and Message Archive Management. These seem to be important features for "full functionality" to many people.

@lstrtstr
Copy link

Oh, and probably not only "true" and "false," but also "via plugin" would make a lot of sense.

@dreamflasher
Copy link
Contributor

I think true/false is sufficient, if supported by a plug-in it's supported no need to overcomplicate things.
Yet, I still believe the release date should be included in the client information.

@bascht
Copy link
Owner Author

bascht commented Jan 21, 2018

Sorry for the radio silence in the last few months. I'll try to get this back on track in February. 😺

bascht added a commit that referenced this issue Feb 10, 2018
This PR will add a new section below the main table that adds a addressable
anchor for every client. Individual details like OS support or plugin /
licensing details can be added down there without cluttering the main table.

Refs #40
Refs #35
bascht added a commit that referenced this issue Apr 9, 2018
This PR will add a new section below the main table that adds a addressable
anchor for every client. Individual details like OS support or plugin /
licensing details can be added down there without cluttering the main table.

Refs #40
Refs #35
@bascht bascht closed this as completed Apr 9, 2018
@lstrtstr
Copy link

Was this closed on purpose? In my opinion, it would still be useful to indicate the status of group chat, MAM, carbons etc., or is this something you don't want for a reason?

@bascht
Copy link
Owner Author

bascht commented May 2, 2018

@lstrtstr Yes. I want to keep the maintenance effort for omemo.top at a manageable level. Wikipedia / etc. might be a better place for this, think e.g. https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_clients#XMPP-related_features

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

No branches or pull requests

6 participants