Closed ai closed 8 years ago
Did you get any feedback yet?
@andywer Yes, and i will change logo, because all dont understand what is this
@ai @andywer Maybe Gothic-Diablo style ?
@Gaserd :D strage look.
@Gaserd Haha :'D
@ai @andywer I think we leave our current icon 👍 And in future we have make new icon for this plugin, because I dont have idea for icon
@Gaserd Seems fair. But can we make it monochrome? ;)
PS: We can collect ideas here: https://github.com/andywer/postcss-debug/issues/12
@andywer you could insert PostCSS logo in white color ?
@ai @andywer added small fix in mobile UI
@Gaserd it is hard to understand that click on file block change plugin list. They looks like similar links. People will ask: “why nothing changed after I clicked on file block”
@ai Okay.
@Gaserd You are doing great work here! I wasn't sure if anyone really uses a debugging utility on their phone, but... It will be pretty cool for demoing!
We should put the inspector with some sample code in gh-pages
so people can try it out without installing it and it will even be usable when they try it on their iPhone :)
@andywer Thanks and you are right!
@andywer are you life ?
@Gaserd Hey! Sorry for the delay. On one hand I have have been very busy the past days, on the other hand I guess I planned too much for the next release.
Here is the current roadmap:
I should probably cut it down in favor of releasing soon.
@andywer Awesome! I can you help ?
@Gaserd I wish I could share some work on this, but I think this kind of refactoring requires too much insight into the code.
@andywer okay :)
@Gaserd I just recognized we still need a solution to prevent accidentally clicking the plugin documentation link when you want to expand a snapshot. This happens to me permanently when using the latest (not yet released) UI.
@andywer are you live ? :)
Hey @Gaserd. Yes, I am, but I was on holidays last week ;)
There are currently still two issues left:
Sorry for the long delay!
@andywer Ow! Maybe I help you with CSS yet you write nice core code ? Push (commit) master branch and go write nice code :)
@Gaserd Not sure if I got you right... Do you mean you can clean up the CSS? The problem is that I want to fix stuff before merging to master, since the master branch should always remain "clean(ish)".
And... we still have to come up with a solution for
Usability: Plugin help link will now often be accidentally clicked (#10 (comment))
Because that will annoy users a lot, I think.
@andywer Yeah, I sure can clean CSS. I think about this problem:
Plugin help link will now often be accidentally clicked (#10 (comment))
I start today clean CSS in develop branch.
@ai @andywer
Plugin help link will now often be accidentally clicked (#10 (comment))
I think we can make so
Looks good 😊
@Gaserd Yeah, I like it to :)
@ai @andywer Yeah! Congrats!
Just published version 0.4.0 with the updated UI. Will close this issue ☀️
Thanks @Gaserd!
Out current UX is nice, but we need better visual design:
We could always try Material design, its visual langauge pretty nice and better then nothing (but custom visual design will be nicer).
With better visual design this tool will look more professional.