I think that the discussion shows that the configuration modules are on the inconsistent and confusing side of life.
I have thought about the problem a little too, and I believe that defining coarse guidelines is a strong way to unify and create consistency between the configuration modules. Such a guideline already exist, such as the requirement for the configuration dialogs to fit a certain screen resolution. Other guidelines could be that the look section provides only access to settings that are cosmetic in nature. Or that any theming should register with the theme selector for modification at a central location(I'm looking at you shelf styles) really I want per widget theme:\ The names that exist are likely built from the understanding of the person who created the module. And as such already have a depth of understanding and correctness to them (however confusing to the rest of us). Changing them to anything without creating an understanding or guideline will just create the same situation for other people. And over time when modules evolve without guidelines the names become ambiguous again for different reasons. But perhaps I'm over thinking it I had started looking into the configuration dialogs as they seem like a good candidate for less experienced people like myself to help out. I am still a very green programmer for now. but I'm working on it :) I know raster's probably thinking to himself "Show me the patches!" like jerry maguire styles... :D ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
