I agree with Sam. But it needs to be trivial for apps to pick up the latest changes too. This could be easily solved with Bower. Each app could “lock in” to particular versions of the components they’re using. Then to get latest, the apps only need to have their version numbers bumped in bower.json.
-Justin > On Oct 28, 2015, at 4:49 PM, Sam Foster <[email protected]> wrote: > > > > On Wed, Oct 28, 2015 at 11:52 AM, Patryk Adamczyk <[email protected] > <mailto:[email protected]>> wrote: > > So there is also another part to this, and that would to have it sit in a > live styleguide. > Imagine if the components can be in github and a single change in github > would instantly update: > + master and every FXOS app > + style guide website > > That would be amazing! > > It would really echo the ideas of focus and dynamic efficiency. > > > I don't think this is either practical or desirable. To have a single change > cause ripples across all FxOS apps would be really really difficult to > manage. Talk about strange magic from a distance! Plus we are moving away > from a monolithic "Gaia app". *I do agree we need a simple opt-in way to buy > into consistent look and feel and control interactions*. And a way to pick up > bug fixes or updates from shared components without simultaneously breaking > unrelated stuff - see Jim's note about font-size changes. But I would like to > steer us away from the notion of a one-size-fits-all UI toolkit. It always > ends in tears. Apologies if I'm over simplifying or mis-characterizing here, > I just want to offer the counter-argument. > > /Sam
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
