modify the mobile UI for WIMP

[uday-kalyan-s]

discussions

evident bugs

• the fixed and small size of search bar causes an overflow of text. especially the search bar my PR fixes this by increasing the width to 80%.
  However i believe a varying size input may be better for smaller names (see "Arun Ghosh") keeping a min if 45% and a max of 90%
• large prof names ("Arun Kumar Samantaray") pushes the dept to the far right making a huge gap
  splitting this such that 20% of the space goes to the dept code might fix the issue
• huge margin in the timetable on right side

suggestions

• small doodle art.
  this is hardly even visible but removing it might make the page seem really dull and text-ish. I honestly don't know how to accommodate for it.
• dark mode(i could move this to a new issue as it is irrespective of the Layout but I am keeping this here for now)

tasks

• fix search bar
• fix prof name display
• fix table margin

---

Also I would love to take up the issue myself. I will make a proper PR for it soon

requesting for disc @Prasanthi-Peram @Dami-18

[Dami-18]

Initially the project was made keeping by minimal frontend and not being focused on design and responsiveness. So frontend needs some changes as you mentioned

[Dami-18]

As for the layout and design, you will need to try out some things and then see which is better. So you can go ahead with your proposed changes and try some things out like maybe changing margins, padding, responsive font sizes, etc.

[Dami-18]

@harshkhandeparkar what are your opinions on this?

[Dami-18]

cc: @rohan-b-84

[harshkhandeparkar]

Ah I missed this issue. I commented on the PR first.

@uday-kalyan-s if you have any proposed solution, you can send screenshots and we can discuss here or on Slack #projects.

[uday-kalyan-s]

@uday-kalyan-s if you have any proposed solution, you can send screenshots and we can discuss here or on Slack #projects.

well my issue mostly revolved around fixing the bugs that were observed on Firefox. now that we realised it's a bigger issue on chrome, I might have to modify the issue again. But like you mentioned in slack, idk how to debug it exactly. I'm not sure about the difference taken in chrome and Firefox here. ig we can discuss it in slack?

[harshkhandeparkar]

@uday-kalyan-s if you have any proposed solution, you can send screenshots and we can discuss here or on Slack #projects.

well my issue mostly revolved around fixing the bugs that were observed on Firefox. now that we realised it's a bigger issue on chrome, I might have to modify the issue again. But like you mentioned in slack, idk how to debug it exactly. I'm not sure about the difference taken in chrome and Firefox here. ig we can discuss it in slack?

We can resolve the Chrome issue separately. Let's discuss that on Slack. For now, you can work with devtools responsive mode or on Firefox mobile.