Far worse really. If you want an all in one solution, there's already VLC.
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Nov 24 2021
That's a bit like saying, "Make France, Germany, the UK, Spain, Italy, and Switzerland into a single country." :)
Nov 23 2021
Jul 21 2021
Apr 24 2021
Apr 19 2021
@shadowfax That would be a good idea but be prepared for quite some work.
Hey @mgallien, I'm interested in picking this up. Do you think it would be a good start into this project ?
Apr 2 2021
Mar 10 2021
Yes, our awkward playlist support is simply a bug (or more precisely, the lack of a feature). It's not an intentional design choice. See https://bugs.kde.org/show_bug.cgi?id=406477
Mar 7 2021
Hey, not sure if this would be the right place to say this, just my 0.02$ of feedback on the playlist stuff. Most people I know listen to music through playlists, with most of my friends having around 5 of them. One of the things I miss from other music players is having such playlists readily available on the side bar, such as in rhythmbox, spotify, itunes, etc. I'm not sure how the playlist sidebar came to be, as I can't see it in the mockups, but it seems to assume that when a user wants to listen to a playlist they will load it from a playlist file and into the queue. In my eyes, this has a few implications when it comes to user experience:
- It has a steep learning curve: it takes a bit of time to wrap your head around the logic of loading playlists instead of playing them. Loading files is also not a very user-friendly way of listening to a playlist.
- It mixes the concept of queue and playlist: while it's an interesting idea, the two concepts aren't totally compatible. Let's say, for example, that I have loaded a playlist to the queue and i have made some modifications to the queue (let's say that i have removed some songs that I wasn't in the mood for). Now imagine that i wanted to add a song to one of my playlists: because the queue is where you edit the playlists, I would have to clear everything in that queue, load the fresh playlist, add the song, save the playlist and then remake the queue that I made earlier. As you can see, it interrupts playback and can be confusing if you don't understand the logic behind it.
- It clutters the UI: while it is normal for professional software to use multiple panels to give access to more functionality at once, in my opinion a music player doesn't have to cater to the power-users, instead aiming to be as intuitive and simple to use as possible. Unless you make playlists for a living, I'm sure that most users would rather have ease of use than direct access to all of the features.
Therefore, I propose that playlist list be implemented in the left sidebar, for quick access. I see that a lot of people here are very fond of the playlist sidebar, but listing the playlists on the side would make it a less essential part of the UI and it could be moved to an entry on the left sidebar, like rhythmbox does. This way we could keep the same flexibility when editing the queue, with the only inconvenience being that it wouldn't be always visible.
I don't want this to sound like one of those "I want this because x application does it this way", but I feel like the design patterns that the users are used to conflict with Elisa's current implementation. Huge thanks for all you work!
Dec 24 2020
Dec 14 2020
We can just adjust current design
We can remove the big color in top
And combine the art cover with the tools bar
And make media buttons much bigger
Combine current with the best from the mockups
Dec 1 2020
Nov 20 2020
Nov 17 2020
Oct 28 2020
...Thus underscoring the need for a "KXMLGui for QML apps".
the api which plasmoids use to notify "apply needed" is kinda weird.
the "final product" must be not in Kirigami, but somewhere it can depend from KConfig (and better, KconfigXT so KConfigSkeletonItem and what not)
Oct 20 2020
Oct 16 2020
Oct 14 2020
https://invent.kde.org/multimedia/elisa/-/merge_requests/178 will include the implementation of this task.
Oct 13 2020
I can help with design, sure. Reaching out to VDG would be good too.
Oct 12 2020
@fbaumanis Sorry for the late answer.
Oct 11 2020
I assume that a tab should be added in the left sidebar (see attached screenshot). Is that the desired result?
Sep 28 2020
@ngraham The removal of the unrelated posts is https://invent.kde.org/websites/elisa-kde-org/-/merge_requests/4 and I just merged it.
Looks like that's fixed now. Closing!
Thanks everyone @ognarb @nikunjgoyal @mgallien @ngraham for helping through the course. Happy to see this work live.
Great work everyone! It's gorgeous!
Thanks a lot for launching the site 😍😍😍.
Also thanks a lot @ognarb for sponsoring us 🔥🔥🔥.
Also, the website is now live https://elisa.kde.org. Paul wanted to do a small review of it before we can announce it to the whole world on social media :D I already mentioned it a bit in https://carlschwan.eu/2020/09/28/what-is-cooking-on-kde-website.html
In T12726#241343, @mgallien wrote:@ognarb The current list looks good except maybe @nikunjgoyal and @deprov who created the site are out of the list. Is this usual for websites ?
It is handled a bit differently for code and I understand that a website may have different rules but it seems a bit weird to me.
@ognarb The current list looks good except maybe @nikunjgoyal and @deprov who created the site are out of the list. Is this usual for websites ?
Sep 27 2020
In T12726#241307, @mgallien wrote:It is perfect. I am really grateful to everybody for such a nice website.
Should I move some blog posts about Elisa on this site ? As it is the current entries should be removed or they will lead to some confusion.
It is perfect. I am really grateful to everybody for such a nice website.
From my side, the website is now perfect :) @mgallien are you ok to deploy it and who should get commit access to it other than you?
Sep 25 2020
Hi @nikunjgoyal and @deprov,
Sep 24 2020
Sep 23 2020
@mgallien it's alright :) Hope we're able to finish up with a great website for elisa :)
Sep 22 2020
@nikunjgoyal Thanks a lot and I am very sorry to have missed you in my first comment.
@deprov and @nikunjgoyal: nice work :D I will try to review and maybe send a few MR to your repo tomorrow
@deprov Thanks a lot !
Sep 21 2020
In T8176#240879, @ngraham wrote:I'm working on porting MetaDataView and ContextView to Kirigami.FormLayout right now BTW.
I'm working on porting MetaDataView and ContextView to Kirigami.FormLayout right now BTW.
This is done now!
Let's use another phab task to track improvements, so the current status is clear. :)
The bug report is closed, and this is working much better now.
Indeed, this was already implemented. :) If you're looking for ideas, there are a few more on the workboard, and here are a few more I think would be useful:
is this issue currently open as I can see the feature is already added in ELISA
Sep 20 2020
Thanks everybody for this initiative. Even though I did some web dev at my work, I really feel incompetent on this.
That will be really cool to have a website to promote Elisa and help its users find information about its usage.
Hugo is also fine :) You can find some layout files here: https://invent.kde.org/websites/kde-org-announcements-releases :)
@ognarb is it alright if we do this in hugo or does it have to be in jekyll?
Sep 19 2020
yes @nikunjgoyal we can work together. I will contact you regarding the proceedings.
hey anubhav , I'm also interested in this . Would you like to work together on this?
We use jekyll for creating the websites and have a theme ready. See https://community.kde.org/KDE.org/Jekyll for a tutorial to how to use it.
I would like to work on this but I have some doubts.
Sep 3 2020
Jul 13 2020
That's probably fine. It's something we needed to do eventually anyway. Submit the MR and we'll take a look. Thanks again!
Jul 12 2020
It is a real Kirigami drawer.
But in order to use this, I changed ElisaMainWindow.qml from a standard Qt ApplicationWindow to a Kirigami.ApplicationWindow.
That might have side effects that I am not aware of :/
Jul 11 2020
That looks fantastic! Are you using real Kirigami components or just emulating the style?
I'm having a look at this if everyone is ok.
I started following the kirigami drawer idea using the states browsingViewsNoPlaylist and browsingViews defined in ContentView.qml.
When in the browsingViews state, keep the current layout.
When in browsingViewsNoPlaylist state, currently the playlist disappears and is no longer visible, I juste added a drawer that is enabled only in this state.
I made a quick video to show what it currently looks like (attachment).
If this direction is ok for everyone, I will continue working on this.
Jul 9 2020
Jul 8 2020
ok, sure. I'll post it there
Hi, thanks for your patch, but new patchs go to https://invent.kde.org/multimedia/elisa and phabricator only host tasks now.
Jul 7 2020
In T7674#234906, @metamehta wrote:Hi! I'd like to contribute to this job if it is still open. I'll make changes on the qml side.
Hi! I'd like to contribute to this job if it is still open. I'll work on making the required changes to implement this feature.
Done with that merge request. Thanks!
Jul 6 2020
Thanks,
done at https://invent.kde.org/multimedia/elisa/-/merge_requests/131
That looks great! Feel free to submit it as a merge request!
Hi there, I would like to take this task, if possible.
Jun 28 2020
Jun 20 2020
Jun 11 2020
Hello, would this redesign still include the cover art view? I'm asking since it doesn't show up in the mockups.