Feature Request: Additional Clarification on "Simple Example" in "introduction.txt"
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 45/100
- Issue 類型
- 文件
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 技術堆疊
- python
研究方向
開啟 introduction.txt，並搭配其中的兩個視窗範例閱讀第 2.1 節。檢查文字目前如何描述 200 x 200 視窗和大小不同的 Hello World 視窗；當文件說明了相關的大小行為和預設值，且沒有讓這些範例缺乏解釋時，文件工作就完成了。
由索引模型根據 Issue 內容生成。
描述
I hope this isn't too pedantic as a request, but just reading section 2.1 of the guide from the top, the first statement claims, "This program will create an empty 200 x 200 pixel window."
A graphical representation of such a window is then included.
The page then provides a 9-line program by way of an example, in source code, then follows to "explain each line of the example."
However, nowhere on this page does the text return to the subject of "200 x 200 pixel" sizing. It seems reasonable for the initial declarative statement to explain what is about to happen, but there is nothing in the sample code which defines such a size and it is therefore implied that Python's "Gtk.Window()" method, or perhaps "win.show_all()", must somehow default to these dimensions unless explicitly told otherwise.
If you're going to have a "simple example", can I respectfully request/suggest that the explanatory text be expanded just enough to tell the reader where the window dimensions come from.
I appreciate that this might come across as pedantry, but syntax is critical in programming, so in the early stages of introducing a language or framework, I would suggest that all defaults and assumptions need to be discussed.
This is all the more relevant given the second example on the Introduction Page (the ubiquitous "Hello World" application with the "Click Here" button. Miraculously, the rendered window has changed size. Yet again, there is nothing in the code to suggest window size or why this might be different from the first example. The two examples imply that if you deploy a random, empty window, then it will default to a size of 200x200 pixels, but if you deploy a window that contains an object (your second example uses a button), then the window will automatically size itself to the dimensions of the rendered contents.
None of which is explained.
Even if you want to direct your reader to set this aside, please don't leave hanging threads at the start...
Thank you
- 主要語言
- Python
- 星號
- 392
- 分支
- 157
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
我們還沒有檢查這個專案的環境設定檔。先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
sebp/PyGObject-Tutorial 的其他 Issue
-
難度 5/5 一週以上 新手友好度 20/100
sebp/PyGObject-Tutorial#229 ·
-
難度 3/5 1-2 天 新手友好度 35/100
sebp/PyGObject-Tutorial#219 ·
-
難度 2/5 1-3 小時 新手友好度 45/100
sebp/PyGObject-Tutorial#218 ·
-
難度 4/5 3-5 天 新手友好度 35/100
sebp/PyGObject-Tutorial#214 ·
-
難度 2/5 1-3 小時 新手友好度 52/100
sebp/PyGObject-Tutorial#210 ·
查看 sebp/PyGObject-Tutorial 的全部 Issue
相似的 Issue
-
bug server
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
sportsdataverse/sportsdataverse-py#641 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
googleapis/google-cloud-python#18532 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆