-
Notifications
You must be signed in to change notification settings - Fork 17
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
New UI and searched results #46
Comments
The part of, what to di when nothing is searched is being covered by another contributor so you dont have tk worry about that |
working on UI :) |
Hey @Rudresh-pandey is this a critical work, and if I proceed with #41, will it be breaking changes to your work? |
Yes let me do the changes first . |
Sure. Let me know once you're done, and I'll proceed. |
bhai , hum Ui improve kar diye h lekin ab ek do orr merge ho gaya ab kaise PR bheje |
Iguess you have to sync your fork Or i think make a new branch and push the changes to that branch and then create a pr I do no know exactly what we have to do. |
Did you fix it? I wont merge anything from now till i merge your pr |
It is being taken care by @Substancia at #60 |
bro wo tho tab show hoga jab user pahle se emoji's ko pahle se copy kiya ho |
Now see the website. Now make a pr with ur cool design. |
I will start working on this from tomorrow , So now you can merge others code's , But from tomorrow plz try not to merge otherwise it may create merge conflicts. Probably this will take 1 day of workGreat work everyone :) |
Okay i wont merge anycode in this repo tmrw until your pr is made and merged |
There shouldn't be any merge conflicts if we are periodically syncing our fork with the upstream (or original repo). Technically blocking other PRs isn't ideal and goes against the concept of Git, but since we don't have many critical works running in parallel right now, I guess this is doable. My point is, please periodically sync your fork with the original repo to avoid merge conflicts, so other devs won't have their work blocked. Cheerio! |
@Rudresh-pandey now please sync the repo and then start working on it |
phone view wala code kidhr hai? desktop wala pe changes kiye tho mobile view wala change ho ja raha h uska code kaha hai? |
What do you mean by the phone code? I do not know where it is because i havent seen the project for 10month It must be in some css file |
ok |
@aditya-singh9 bro laptop ka screen mai thik dikh raha h , sample1_kekfinder.mp4Lekin responsive nhi ho raha sample1_kekfinderM.mp4Responsive hone ka code node modules mai hai usse kasie karte hai mujhe nhi pata i guess iss issue ko close karke dusra method dhundna hoga wo sticky wala issue ko solve karne ke leye #64 ya koi orr responsive code pe kaam kar sakta hai agar tho . |
One way to tackle this is creating responsiveness using CSS media queries. You can define a screen width which differentiates different devices, and style the container accordingly for each screen. As for mobile view, maybe we can stick with old design of having emojis below? In which case the sticky section issue will be needed to be addressed. |
Yes iguess in the mobile view, we should stick to the older design |
Yes IMO, media queries will be the best. |
Where do you see the code in node modules? |
yes mobile view will have the older design but when i changed the code for newUI (only for desktop view) it also changes the mobile view . |
These are certain default styles coming from certain packages, and are overridden by the css files that we define, don't have to worry about them IF you're writing the styles that we need (just pretend that the default media queries don't exist and start writing). TL;DR: write your own media queries for responsiveness and these styles from node modules will disappear. |
ok thanks :) |
Have a look :-sample2_KekFinder.mp4This will solve some issues :
thanks - |
Good job @Rudresh-pandey. "2 . The issue of the sticky search bar and multiple select feature(msf) - in desktop view . Tbh I'd prefer as a user to have the selected emojis section visible at all times, including when we scroll down, for the ease of keeping track what all emojis I've selected so far. This way, I can also keep track of misclicks and wrong emojis and immediately delete the wrong emojis from the selection. In which case, the sticky situation has to be taken care of as well. Otherwise, the UI looks good. What does @aditya-singh9 think? |
Yes we have to keep track of emoji's . Working on it :) |
I really appreciate his work and i really like the ui too. And for the stickness, i am not sure, what should we do. |
Can i merge the current code then we should have a discussion on how to solve the stickyness issue |
Hi, the UI of KekFinder now looks odd to me , the searched items in a row are now only two and there is another feature of copying multiple emoji's which is great but now we have scroll more to find our desired emoji.
Current View :
After adding the above feature ---
**This has also some issue like overlaping of emoji's and multiple select features. which had already been noticed **
.
.
.
I would like to propose new UI to our project :
Light Theme :
Dark Theme :
And another suggestion on what to show when nothing is searched -- Rather than creating favourite section or showing all the emoji's , We can show all the previously copied emoji's to the user so that we don't have to bother about the number of emoji's to be displayed.
I am giving the link to the Figma design , feel free to make changes and present your idea
https://www.figma.com/file/MLuUOQ38c7UC3Qh7dT0ekc/kekFinder?node-id=5%3A31
:)
The text was updated successfully, but these errors were encountered: