On 10/07/15 16:07, Tomasz Bursztyka wrote: > Hi Slava, > >> connman is a piece of middleware, its >> job is to provide the functionality and leave it to UI designers to >> decide what to show, what not to show and how to present it to the user. > > That's a debate on its own. > > Actually, I don't think UI designers should be the only responsible > for what to expose on the UI. > It then creates a top-to-bottom dependency, without a proper > understanding of the lower layers, > which tend to generate more problem with time (from maintaining the > API to properly architecture > the service etc...). >
Like many other things, it's a trade-off. Allowing UI designers to blindly produce functional requirements may be a pain from the middleware developer's prospective. On the other hand, letting developers define their own UI would most likely result in something chaotic and visually disturbing like your beloved Android UI (which I'm not actually familiar with but I trust you that it's horrible). Both parties have to talk to each other but someone has to take care of the general consistency across the entire UI platform and it's clearly the job of UI designers. Regarding connman, it's positioned as portable middleware component for Linux-based systems. As such, it can't possibly make any assumptions about the UI. The platform may have no UI at all. Regards, -Slava > Tomasz > _______________________________________________ > connman mailing list > [email protected] > https://lists.connman.net/mailman/listinfo/connman > _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
