Open mamayuan opened 9 months ago
Thank you for your response. Our decision to omit certain terms from the developer's guide was based on the assumption that our readers, being developers, would already be familiar with these concepts. If we do add terms such as activity diagram
, sequence diagram
, GUI
, JavaFx UI framework
, JSON
, interface, package
, we would have to even more terms such as Activity bar
, Class
, Abstract
, it is unclear where to stop.
Team chose [response.Rejected
]
Reason for disagreement: I disagree with the team's rationale for omitting certain terms from the developer's guide. While it's understood that the guide is intended for developers who might be familiar with these concepts, the inclusion of comprehensive examples in other parts of the guide suggests a thorough approach to explanation and clarity. Given that 'UI' has been included as a glossary term, it sets a precedent for including terms of similar complexity. It is unreasonable to keep 'UI' while leaving out so many other terms. Therefore, terms like 'GUI', 'JavaFx UI framework', and others I proposed should also be considered for inclusion. The argument that it is unclear where to stop adding terms seems more like a matter of convenience than a well-founded limitation, especially considering the detailed nature of the rest of the guide.
Currently, only three terms are explained while![image.png](https://raw.githubusercontent.com/mamayuan/pe/main/files/22bd9da1-964b-4718-b650-1993fd859264.png)
UI
is one of the three. Then terms such as 'activity diagram,
sequence diagram,
GUI,
JavaFx UI framework,
JSON,
interface,
package` should also be documented for better clarification