-
Notifications
You must be signed in to change notification settings - Fork 5
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
Redesign InspectorFloret record list #179
Comments
Hey @Shukuyen, thanks for your proposal. First let me maybe explain the thought that went into the current layout a little. All left aligned elements are regarding the request and all right aligned elements are giving you information about the response. This is one distinction that we would lose with your proposal.
I like that you grouped the smallest elements in one line. What do you think about changing the order? Method, Time, Status-Code?
I like that, though I like the old colors better. Did you change them on purpose? Also: The status code tag now feels a little too tight. Maybe increase the height there?
Yes, I like this as well.
Absolutely! Good idea. Maybe there is even more possibility to improve there. Table-section containing the hour and the minute and only the seconds in the cell? Just a first idea.
I am not super sure about this one. Is it really necessary to have all this information on that page here? I mean, all the details are just one tap away there.
Oh, that answers my question from above ;) Maybe we can find a middle ground there. |
Understood. I based the redesign loosely on the network part of the Firefox web inspector, because I really like the information density and grouping there. Imho it is not really necessary to keep request and response separated, at least for me it doesn't help answer the questions "What request is this and how did it go". Is this different for you?
Tried it but I don't like it. Moving the splash of color from the status code to the right leads to a lot of text clumped together on the left side, which makes it hard to quickly grasp the necessary information.
I think it looks less clunky this way. It doesn't need to be really big due to the background color and that's how I saw and liked this tag style in other products. But we can of course try to adjust it.
This could work. I would like to do it in step two, because I am not sure it makes it more clear when we pull information out of the cell and you then have to search it in different places.
Yes, not really happy about this myself ... Should it even be on the first page then? I introduced the line breaks because the content type is combined with the error message. The error message looks like it is only useful when displayed in full. Not sure about this.
Sure :D The original color were too blunt for me and I always liked the Bootstrap colors (which are the ones I am using here). Feel free to propose a palette, as something like colors is really subjective. I myself like matte colors more (like they are used for example in Material Design). |
Hey @Shukuyen, I just wanted to sum up our last discussion about this topic.
After getting used to your new proposal it became more and more clear, that my initial intentions there didn't have a huge effect. I am super fine with keeping it as is.
You are right there. Let's keep it as you proposed.
I tweaked it a tiny bit. See my counter-proposal below.
Absolutely.
We discussed this together and figured that even the content type isn't really necessary to show on the first level. See my counter-proposal below.
I am curious to hear your thoughts. |
I like green, blue and gray. My red appealed more to me, but I can live with yours. Can you please give me the color codes?
I don't really notice the change, so it's good :-) By how much did you increase the height?
I am not really sure about the attributed URL yet. I will try it out with my font and font sizes and also have one alternative I want to try. Do you like it better than the version before? |
Tried it and it doesn't look good. Looking forward to test yours. |
Absolutely: red: #D22E0E (slightly tweaked)
tag height: 20pts |
I think the record list in the InspectorFloret could be improved a little in regards to structure and legibility. This could be done by grouping elements in a different way (status code and request method should go together imho) and balancing the weight of the elements by more accentuated colors and font sizes.
Please have a look at this prototype:
What is proposed here:
I would also have liked to put the content type between request method and date time, but there wasn't enough room, so I had to put it in a third row (which I am not that happy about).
What do you think, is this an improvement? Any feedback on how to make it better?
Screenshot of the current design for comparison:
The text was updated successfully, but these errors were encountered: