lorenzogotuned added the comment: Ok Upendra. Nice summary.
In the next days: - Explain each *top task* (install, unistall, update) and in detail the way the underlying pip commands work (underline mandatory and optional parameters, requests performed to servers, filesystem storage and anything involved) - Map your natural explanation into different *page views* (each page view conrainig well defined UI components and structures) - Design and *sketch* each page (upload image files. I saw you had started doing it in the previous issue; make them much more explicative, name or assign a number to each view and UI component) - Simplify and optimize each task flow and page (get familiar and be precise with the vocabulary needed to describe the UI) - write at least one user case for command (install: user search the xyz string in a package in the input box, user clicks on a item in the ywz panel, the user clicks the abc button, etc) in the shape of ordered lists or better flow charts. This will complete the first design iteration. After receiving feedback and adjusting the sketches, I think we can dive into tkinter to find the right objects/patterns to start coding. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27051> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
