Just had a good chat with Darrin about it makes the most sense for
engineers to work with the Loop design assets, and particularly about
the differences between the desktop client and the link-clicker code.
Here's my summary, feedback is welcome:
For desktop code:
* Consider the design mockups at
<https://people.mozilla.org/~dhenein/labs/loop-mvp-spec/#call-incoming>
to be UX mockups: about general layout and interaction flow. That said,
don't hold too tightly to exact box models etc: feel empowered to inject
good engineering practices, use common sense, and ask others (especially
Darrin or RT) for clarification.
* Consider the visual mockups linked to from
<https://bugzilla.mozilla.org/show_bug.cgi?id=1016087> and the assets in
the zip file there as the general source of CSS, measurements, and
appearance.
Again, we should feel empowered to inject good engineering practices,
use common sense, and ask others for clarification when it's not obvious
how to reconcile both the above sources with the existing code practices.
For link-clicker code:
* Consider the spec at
<https://people.mozilla.org/~dhenein/labs/loop-link-spec/#call-start> to
be effectively both UX and visual mockups. Treat the CSS/HTML as
more-or-less visual spec. In particular, we probably want to grab
fonts, colors, and visual layout more or less directly from there. That
said, we shouldn't hold things like box model structure, units, and
other implementation details as gospel.
I'm still looking into SVG asset possibilities.
Dan
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
