Skip to content
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

Make the app fully responsive #64

Open
AdrianBZG opened this issue Feb 13, 2020 · 22 comments
Open

Make the app fully responsive #64

AdrianBZG opened this issue Feb 13, 2020 · 22 comments

Comments

@AdrianBZG
Copy link
Member

AdrianBZG commented Feb 13, 2020

It would be ideal to make the app fully responsive, especially header, menu, footer, etc.

@dmahajan980
Copy link

Hi @AdrianBZG! Thanks for opening up this issue. Since I had a few ideas regarding the app's and its components' responsiveness, I am very much interested in working upon this issue.

@AdrianBZG
Copy link
Member Author

AdrianBZG commented Feb 13, 2020

@dmahajan980 Sure. We ought to discuss the ideas you have in this issue, so that we can come to a proposal before actually coding it 😄

@lazycipher
Copy link

@AdrianBZG, I propose to use Material Design! I really love this way of designing web pages!

@dmahajan980
Copy link

dmahajan980 commented Feb 14, 2020

@AdrianBZG, for the app's responsiveness, I intend to fix the its main body (other than navbar, side-nav and footer) first. Currently, we have the following (major) responsiveness issues related to it:

  1. Graph and Pie-chart squeeze in mobile view or on devices with significantly lower device widths

    mobile

    What we can do here is to stack the pie chart and the graph one above the other so that both don't shrink or squeeze.

  2. Buttons occupy multiple rows even though it could be placed in one line.

    options+hover

    I plan on slightly rearranging the buttons in one or two rows and towards the centre.

  3. Part of the table hides if table width is more than browser viewport.

    tables

    We can make the table horizontally scrollable below a certain device width so that important pieces of information contained by the table doesn't hide out.

I would be happy to get your feedback on this. If there's anything that can improved or added to this, please do let me know.

@HaseebAhmad23
Copy link

Is this issue solved or not?
I want to work on it.

@GraceChiamaka
Copy link

@AdrianBZG I'm an outreachy applicant, Can I work on this issue?

@komecodes
Copy link

Hello, I would love to give this a go, can it be assigned to me please? @AdrianBZG

@yochannah
Copy link
Member

Hey folks! this is probably an issue best tackled by one person at a time! ❤️ @dmahajan980 - are you still working on this? If not, we'll reassign it to the first person who is still able to work on it :)

@dmahajan980
Copy link

Hi @yochannah! Sorry, I am a bit busy nowadays and so I don't think I'll be able to work on it anytime soon. You can assign this to @HaseebAhmad23, but I think that if somebody solves issue #73 then this issue will be automatically fixed.

@yochannah
Copy link
Member

thansk @dmahajan980 !

@HaseebAhmad23 - I've assigned this to you 🚀

@PrastutiUpadhaya
Copy link

Hi, I would also love to work on this issue!

@HaseebAhmad23
Copy link

thansk @dmahajan980 !

@HaseebAhmad23 - I've assigned this to you 🚀

Thanks @yochannah !

@NinaLoeterman
Copy link

I'm happy to work on this issue if it opens up again! (Outreachy applicant for may 2020)

@muskangupta-iitr
Copy link

muskangupta-iitr commented Mar 12, 2020

Greetings.
This issue has not been worked upon for some time now and I am quite interested in working on this issue. Can I be please assigned this to so that I can start working on it? @AdrianBZG @yochannah

@dmahajan980
Copy link

dmahajan980 commented Mar 12, 2020

Hello everyone!
Lovely to see so many people willing to fox this issue. However, this issue has been currently assigned to @HaseebAhmad23. I would request you all to look for some other issues and probably, this one will be assigned to the next person who requested to work on this issue if in case @HaseebAhmad23 couldn't work on it.

@AdrianBZG
Copy link
Member Author

Hi, I'm going to re-assign this issue (following our contribution guidelines). I'm happy to hear about your individual plans to take on this issue. Please discuss by email ar989 (at) cam.ac.uk.

Thanks.

@HaseebAhmad23
Copy link

HaseebAhmad23 commented Mar 18, 2020 via email

@lape15
Copy link

lape15 commented Mar 18, 2020

Hi, Can i get a chance to work on this. It's tough out there looking for projects to work on

@lape15
Copy link

lape15 commented Mar 18, 2020

i would go with @dmahajan980 approach

@Emuohwo
Copy link

Emuohwo commented Mar 19, 2020

@AdrianBZG @yochannah I would like to work on this issue when there's need for it to be reassigned. Please reassign it to me when necessary

@guptadiksha307
Copy link

Hi, I'm Diksha, an outreachy applicant. After looking at this issue, I found that the issues told by @dmahajan980 are mostly solved except that table part. I would like to work on this issue. Can I take up this issue?

@GraceChiamaka
Copy link

Hello @AdrianBZG @yochannah I would like to work on this issue.
I've sent an email detailing how I plan to solve this issue

AdrianBZG pushed a commit that referenced this issue Sep 3, 2020
Constraint tags were not being displayed. Now if a constraint has been
updated, it will display a tag (with a number if multiple exist).

If the tag is applied to the next query, it will be green. Otherwise it
will be yellow to indicate that the constraint has items present but not
applied.

Squashed commits:

* Show if constraint items have been applied or updated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests