I have to say the idea for maintaining a design system is really clever
I've been planning how the mb server will be revamped. I was initially planning to slowly make the changes to the mb server we have and make progress. However, I have realised that would take a while since we have to make the web interface mobile first this time.
I decided to make it on the go since my major focus right now is towards getting the new design live.
s/mobile first/mobile friendly :)
In short, I started a new react project to make it convenient for me to firstly get my thoughts straight and even connect with the community
Hi lucifer !
So yeah, I have hosted the app at musicbrainz-web.web.app
Right now, only the header and the footer have been added
I am still exploring stuff and looking to make the changes here firstly, get everyone's feedback, and then quickly push these designs to our main project
Plus we need to restart the docker everytime we need to see the changes on the mb server. Overall I would say that from development point of view, mb server is way better but from a design perspective, where we need to checkout every detail precisely, directly jumping to the mb server for that makes less sense
Hopefully, in some time we can have the app live on the link complete (the home page) I shared and over the course of time, we can finalize that first.
If anyone has any suggestions regarding this thinking, I would be happy to communicate. Have a great day ahead!
hello lucifer, when it comes to music recommendation, the user recommends the music to his/her followers. And this is stored in the DB and is retrieved again while rendering the feed of his/her followers. So when trying to implement deletion of recommendation event from the feed, we cannot straight up delete the entry, since other users might have not deleted the same event.
so for this what should be done?
Do you have anything in mind? Or do you want me to come up with a solution for this and then discuss with you
riksucks: letting the user that made a recommendation to delete it should be sufficient for now methinks.
allowing other users to hide those events from feed is a different feature imo.
ohh okay, so the followers won't delete it, but the one who made the recommendation will, I see
>allowing other users to hide is different
I see, I kind of misunderstood the purpose, the ticket makes more sense now. Thank you
>so the followers won't delete it, but the one who made the recommendation will
Also, idk if its an issue only I am having, but the LB frontend locally won't talk with the backend APIs properly. It would always say how the auth token is invalid. So I am resorting to curl and postman to test things out. Is this some common issue or does it seem to only affect me here?
there's a setting in config.py file to set whether the app should connect to LB prod or your local version.
ahh I see, I should have checked there, sorry for the trouble
this should hopefully cover everything needed to set up the dev env. if you find something missing, we should add it there
due to some reason, the wrong version of mbdata was installed in indexer on bono. strange, running reindex now.
peterhil has quit
prabaaaaal joined the channel
lucifer: oh yeah, I got that locally at first too
Are you running a full one now?
reosarevok: yes. full reindex.
Guess that'll take a while :D
place/event/intrument completed so far. yup indeed.
Do we have a good way to check it worked fine?
I guess "no errors" is a good start, but I mean, that they actually look like they should as well
i think we could run it in test.mb and see make some chagnes there observe if they show up in search
Toasty joined the channel
Toasty has quit
krishan has quit
krishan joined the channel
if you get your invoice in in the next 5 minutes, I'll pay it.
otherwise #vacation for the rest of the day
ruaok I started work on 30th September, right😃
I'll let you enjoy your #vacations 💯
ruaok runs off for the day
lucifer: how is that going? :)
reosarevok: i had gone away for a bit. didn't get the chance to trigger reindex for all entities. started reindexing all now.
akshaaatt[m]: I for one think it's a good idea to work on a mockup like this and being able to host it and get feedback!
In my experience it's easier to seek feedback fewer times but on designs that are well advanced, rather than more regular feedback every time something changes in the mockup. (it's easier to integrate a few waves of feedback than continuous feedback)
yes indeed. also, as much as it pains me to say this. it's much easier to see how the mockup if it's made like it will look on the screen, preliminary paper scetches are god for ideas, but bad for getting "how does this mockup look2 type feedback
for exmple, I need full colour to be able to ake judgement
But I found the paper sketches really helpful for myself
absolutely. it's a very good idea
i do those myelf
I really think that coming up with a design is really hard. I never used to think about this until 2-3 years back because it comes naturally to me. But when I explored recently, people have a designated job for this!
trying to think about how f.ex. instrument families evolved to
to me the most important thing is that edit screns don't change *too* much
and that good ideas/scripts get implemented as well
like batch adding aliases, expand/collaps releases script of bitmap's
having front cover art iamges more palces
more data aobut releases more places
having "edit" links more palces
it'd be really cool if I could go directly to the "edit" screen in a search result for example
and making this more mobile friendly. essentially changing the screen-soze wil make things still logical
while at the same time utilising desktop's wide screen space better