Skip to content
This repository has been archived by the owner on Apr 9, 2021. It is now read-only.

Added queue position and approx wait time. #402 #404

Open
wants to merge 18 commits into
base: dev
Choose a base branch
from

Conversation

SuhanKoh
Copy link
Contributor

No description provided.

@Shredder121
Copy link
Collaborator

IIRC embeds didn't look as nice.
Or was it decided to do that?
(Might have missed it)

@Abi45x
Copy link
Contributor

Abi45x commented Nov 27, 2017

We decided against embeds because they don't look as nice as the current queue

@SuhanKoh
Copy link
Contributor Author

I have screenshots here, #402

@Shredder121
Copy link
Collaborator

Ok I see napster said it's okay

@SuhanKoh
Copy link
Contributor Author

Is there another way to display long message without using embeds? The issue here is once I added queue position and wait timer, the message gets too long :/

@Shredder121
Copy link
Collaborator

Without embeds there is more potential screen real estate (on desktop clients*)
embeds only grow as big as they do, so yeah..

@schnapster
Copy link
Collaborator

Embeds use a smaller font.

@schnapster
Copy link
Collaborator

Hi, can you provide screenshots please?

@SuhanKoh
Copy link
Contributor Author

screen shot 2017-12-17 at 9 24 48 pm

screen shot 2017-12-17 at 9 25 15 pm

screen shot 2017-12-17 at 9 25 40 pm

@SuhanKoh
Copy link
Contributor Author

Squeezed to smallest possible on a macosx.
screen shot 2017-12-17 at 9 30 13 pm

Copy link
Owner

@freyacodes freyacodes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FredBoat shouldn't use embeds where it isn't useful. Not all users see them and it is inconsistent with our other messages.

@schnapster
Copy link
Collaborator

FredBoat shouldn't use embeds where it isn't useful. Not all users see them and it is inconsistent with our other messages.

I'd like to hear your counterproposal on displaying a lot of information without bloating the messages.

@freyacodes
Copy link
Owner

I'd like to hear your counterproposal on displaying a lot of information without bloating the messages.

With a normal message, possibly less verbose than the current one

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Jan 2, 2018

Should I concat the music name to maybe to x characters and replace it with "..." ?

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Jan 2, 2018

How does this look?

@schnapster
Copy link
Collaborator

@Frederikam 👀

@freyacodes
Copy link
Owner

Instead of commas I would put linebreaks

@schnapster
Copy link
Collaborator

schnapster commented Jan 8, 2018

I think there seem to be equivalent but shorter replacements for most strings:
"has been seletected" -> "selected"
"position in queue" -> "position", or maybe just "queued"
"approximate wait time" -> "~ wait time", or maybe "playing in"

The last "minute" is completely wrong..can probably be replaced by single letter notation (h, m, s). We might have methods for that in TextUtils already.

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Jan 9, 2018

@Frederikam I think if I follow what napstr suggested, we don't need a line break. I will put up screenshots soon^tm.

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Jan 9, 2018

@napstr I looked at TextUtils, is this the method you're referring to? TextUtils#formatTime

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Jan 9, 2018

Any suggestion on how to put line break?

Maybe something like this?

Song selected #2 ~ Now playing
    HELLO! Songs Jukebox | Akhil Akkineni, Kalyani Priyadarshan | Vikram K Kumar | Anup Rubens (29:49) 

Song selected #1 ~ queued: #2, playing in: 29:49
    Adele - Hello (06:07)

test

@freyacodes
Copy link
Owner

You're right, that actually looks better

I haven't reviewed the code, but I think Napster wanted to do that

@schnapster
Copy link
Collaborator

I like the song name on the second line too.

@Nanabell
Copy link
Collaborator

Nanabell commented Jan 9, 2018

I have a question. How are Livestreams handled here ?

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Jan 10, 2018

@Nanabell It will now only print once for livestream. Seems like the one in production will print twice.
This PR will only change the formatting of the search/selection result.
livestream test

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Jan 10, 2018

Screenshot for the current change:
two lines

@schnapster
Copy link
Collaborator

Would be nice to find a way to incorporate them. Like, usually we show the name of the playlist and the amount of songs on it, instead of the songname and it's length.

@schnapster
Copy link
Collaborator

Is this waiting on further review? Or is the code still WIP since the last one?

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Feb 11, 2018

I have updated the code, sorry for the wait.
In this commit, I have made some assumption, so please let me know if this is ok.

  • When playing from playlist, and hastebin. I've set a max 5 queue messages, then print the counter, which is same as before.

test

@SuhanKoh
Copy link
Contributor Author

Screenshot for split
splittest

@schnapster
Copy link
Collaborator

Let's reduce it to 3 songs and a clue that more have been added like a line of

...
between the details and the total count at the bottom?

@Frederikam needs to okay this.

@SuhanKoh
Copy link
Contributor Author

@Frederikam @napstr Let me know if this is appropriate. I added it because in the production, it usually reply to playlist with "Added 49 tracks. Found too many tracks to display." due to the > 800 characters check.

splittest

@freyacodes
Copy link
Owner

Sorry for the very late response. I haven't followed the conversation, so can you give me a summary of what changed? Is this the only thing that was changed?
image

@Shredder121
Copy link
Collaborator

For trackLoaded it's also using the new format, so maybe also make a screenshot with loading a single track?
Then we can decide if it's what we would distribute to the masses.
Since I agree having a compact list of tracks, but I'd like to be sure the format if right for single tracks as well.

Does it also use the new format with searches? Just wondering.
(Also sorry for hijacking the review Fred 👀 you can continue)

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Feb 27, 2018

@Shredder121

I loaded the same song to show how it looks like loading single track with empty queue and non-empty queue.
Song selected via search will also use the format. Minus the "Found and added x songs..." message.

singleload

@SuhanKoh
Copy link
Contributor Author

SuhanKoh commented Feb 27, 2018

@Frederikam What was changed last time you reviewed was performing the commands below will also use the new printout, with queue and x time to play. And removed embeds and use the text format instead.

  • as a youtube playlist
  • as a spotify playlist
  • as a hastebin link
  • via ;;split

@SuhanKoh
Copy link
Contributor Author

@Frederikam I think I have made all your request changes.

@freyacodes
Copy link
Owner

Unfortunately I don't feel like I have time to review this anytime soon, but at any rate, you should probably resolve those merge conflicts.

@schnapster
Copy link
Collaborator

Whats the point in solving merge conflicts over and over when the bottleneck is that there are no clear guidelines to the UI/UX of this?

@schnapster schnapster added the UX label Mar 15, 2018
@freyacodes
Copy link
Owner

@napstr I don't believe I have as strong opinions about UX as you think I do. If you want you can review and merge this. As mentioned I haven't really followed the conversation.

@freyacodes freyacodes dismissed their stale review March 15, 2018 14:57

Out of date

selectSuccess=Song **\#{0}** has been selected\: **{1}** ({2})
selectSuccess=Song selected {0}
selectSuccessPartNowPlaying=Now playing
selectSuccessPartQueueWaitTime=Queued: {0}, playing in: {1}.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though it may make more sense to say "Queued as #{0}"

@schnapster
Copy link
Collaborator

I don't want to review or manage anything UI/UX related.

* dev: (178 commits)
  Convert to reactive web app
  Replace tomcat with undertow, remove unused jpa dependency
  Replace Spark API with Spring servlet based API
  Replace a few static calls to Launcher with injected dependencies
  Make YoutubeAPI a Component
  Make PlayerLimiter a Component
  Fix bot admins not recognized in private messages
  Add monocrome svg
  Resolve a few warnings and typos
  Snakeyaml plz
  Use gradle's new junit support
  Bump gradle to v4.6
  Bump dependencies
  Remove obsolete tunnel configuration
  Turn off ehcache overflow to disk
  Adjust quarterdeck backend naming
  Backend has its own repository
  Handle uncaught errors more user friendly
  Refactor Sentry into Configuration, add mdc tags to it
  Add logs volume for backend service
  ...

# Conflicts:
#	FredBoat/src/main/java/fredboat/audio/queue/AudioLoader.java
#	FredBoat/src/main/java/fredboat/command/music/control/SelectCommand.java
#	FredBoat/src/main/java/fredboat/util/TextUtils.java
Copy link
Collaborator

@Shredder121 Shredder121 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it looks fine, we can polish later if need be.

NOTE: I am not quite content with patching i18n'd strings together, will have to look and see if it generates problems for translators/output to users.

@SuhanKoh
Copy link
Contributor Author

I don't think there are interest in merging this pr, so I will go ahead and close it

@SuhanKoh SuhanKoh closed this Jul 29, 2018
@freyacodes
Copy link
Owner

@SuhanKoh the problem is that the sentinel branch is blocking this PR. Much of this code would probably need to be changed, and I might do that migration once we deploy the next major version of FredBoat.

This PR may not be merged, but I am keeping it open just so I won't forget.

@freyacodes freyacodes reopened this Jul 30, 2018
@freyacodes freyacodes added the stalled-pr Candidate for closure label Feb 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stalled-pr Candidate for closure UX
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants