On Fri, May 7, 2010 at 9:03 AM, Mossman, Paul (Paul) <[email protected]> wrote: >> One other thing should be >> realized as well: while simplification is a good thing and >> makes everyones lives easier, how much is too much? How much >> do things get watered down before they become so basic that >> monkeys banging on keyboards can make the system work. > > Speaking as a monkey who bangs on a keyboard, I want a system basic enough > that I can make it work. :) > > Seriously though, if we make the system easier to use, more people will > deploy it. That will benefit us all. > > I hope we can find the right balance between simplicity and advanced > capabilities.
Can you imagine trying propose lists of hundreds of settings and your decision about the relevance of each and trying to get peer review. And then manage this process for every new setting over time? I'm confident we can come up with a better solution, and i do agree this needs to addressed. Let's keep discussing because removing settings reverses what was the primary goal of the system. >> My opinion is don't take anything out, but consider >> reorganizing the configuration and just throw all the >> "unnecessary" stuff under an advanced area. > > That is an option. But it comes back to this layout-to-config mapping > challenge. Hopefully we can find a way to get the simplified layout we need, > without breaking the existing config mapping. Settings are organized by how they lay down in the config files, not necessarily how the user thinks of them or deals with them. This is clearly advantageous the developer and not to the user and time for a rethink. This seems like a limitation of a single-hierarchy system when multiple are needed. Tagging comes to mind, where each setting have have a set of tags that allow different grouping, that in turn allow different views. <setting name='demux' tag='audio advanced qos'> Then, you can leverage tag clouds to help organize for more topic based use cases. "As an admin, I want to review and adjust all the QOS related settings" To solve your original goal, maybe tag-based is the default navigation and users have to go out of there way to navigate the raw list in it's original hierarchical structure. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
