New submission from Mark Roseman: Certain policy decisions should be in one place in the code (DRY).
These could be based on preferences or environment (should we be using ttk?), which operating system we're using (what hand cursor looks best?) or even the version of the operating system we're running (do we need to include a sizegrip?), etc. Similarly, there are some small utilities that should be available in many places (e.g. what events to bind to for context menu clicks, setting a dialog to modal appearance) that don't necessarily fit elsewhere. I've attached ui.py which will be a starting place for these sorts of things. ---------- components: IDLE files: ui.py messages: 250143 nosy: kbk, markroseman, roger.serwy, terry.reedy priority: normal severity: normal status: open title: IDLE - centralize ui policies and small utilities type: enhancement versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file40398/ui.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25020> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
