3 ms·
Uh, the point is to provide feedback about the builds, why provide feedback for something you're not using or even have installed?
by pedrocx486 7y ago
Uh, the point is to provide feedback about the builds, why provide feedback for something you're not using or even have installed?
- duxup 7y agoThe web article seems to invite feedback.
- coldtea 7y agoBecause the build is not (and should not be) necessary to provide feedback for new visual widgets. You can see their design and provide feedback directly from the screenshots. If I wanted to provide feedback for how they work, I could download the build too. But there's plenty of feedback where just the screenshot of the new design is enough...
- WorldMaker 7y agoI know we're getting dangerously close to "Ceci n'est pas une pipe" post-modernism art theory land here, but a screenshot of a widget isn't the widget, and how they look in a screenshot is still bereft of other context. It's not unreasonable to ask that even "purely visual/aesthetic" feedback deal with the widgets in the direct context of running in a browser, and used inside web forms.
- duxup 7y agoTo be more specific I was thinking of that button. It looks "pressed in". That seems like the opposite of every button. Maybe the context would help, but that would raise all sorts of other questions IMO.
- WorldMaker 7y agoI think that's actually supposed to be the :hover and/or :focused state (as most of the screenshots of the other controls intentionally are), which is why that specific one especially seems to tell me it needs more context.
- appleflaxen 7y agoBecause you just spent time creating a blog post explaining the changes, presumably to an audience who might not be using your application but you want to entice.