drawLine使用AWT(drawLine using AWT)

 这里有三件事需要考虑： 
 
 
 
 数据的性质是什么：设置或文档 - 或者每个的一些？ 
 
 
 是按用户还是按机器安装应用程序？ 
 
 
 设置数据是否应该与用户一起漫游？ 
 
 
 有时很难确定数据的性质。 为简单起见，将数据分为两类：设置和文档。 它们通常存储在不同的地方，如The New Old Thing博客中所讨论的 
 
 
 
 “我的文档”和“应用程序数据”之间最重要的区别是“我的文档”是用户存储文件的位置，而“应用程序数据”是程序存储文件的位置。 
 
 
 如果每台计算机都安装了该应用程序，则“app installer”对用户数据没有任何影响。 （否则，那么用户的数据是什么？）用户使用应用程序（设置）时应由用户创建用户数据，或者用户通过应用程序（文档）创建用户数据。 现在，当用户第一次启动应用程序时，它可以为用户提供管理每用户数据的方法，以便用户可以在卸载应用程序之后或在用户决定不再使用它之后进行清理。 
 
 手段可以是应用程序使用UninstallString创建的用户ARP条目，该条目运行复制到用户的AppData文件夹的内容。 或者，它可以是用户执行相同的快捷方式。 或者，如果您需要用户不触发的内容，则用户运行注册表项以启动检测应用程序是否已卸载的实用程序（这可能是一个挑战）。 
 
 如果按用户安装应用程序，那么“app install”可以删除应用程序，设置和文档，但应该只删除应用程序。 
 
 文档是用户的，但根据应用程序，如果用户无意再次运行应用程序，则文档可能毫无价值。 你应该离开他们或者问他们。 
 
 至于设置，正如您所指出的，如果用户将来运行任何版本的应用程序，它们将非常有用。 应用程序应该能够升级或忽略新版本或旧版本的设置。 
 
 有关应用数据的更多观看，请参阅此其他New Old Thing 帖子 。 
 
 
 那么，回答你的问题： 
 
 
 
 两者，取决于文件是什么。 
 
 
 设置：可能（但如果每个用户安装了应用程序，则无法）。 文件：没有。 
 
 
 通常，应用程序应该创建应用程序数据，但如果您希望用户知道其文档的“所有用户”位置，则会出现例外情况。 
 
 
 
 只有设计应用程序和安装程序才能产生最佳的用户体验。 

There are three things to consider here:
 
 
 
What is the nature of the data: settings or documents—or some of each?
 
 
Is the app installed per user or per machine?
 
 
Should settings data roam with the user or not?
 
 
Sometimes it is hard to determine the nature of the data. For simplicity, divide the data into two categories: settings and documents. They are typically stored in different places as discussed in the The New Old Thing blog
 
 
 
The most important difference between My Documents and Application Data is that My Documents is where users store their files, whereas Application Data is where programs store their files.
 
 
If the app is installed per machine then the "app installer" can have nothing to with user data. (If otherwise, then which users' data?) User data should be created by the app when the user uses the app (settings) or by the user through the app (documents). Now, when a user starts the app the first time, it can provide a means for the user to manage the per user data so the user can clean up after the app is uninstalled or after that user decides to not use it anymore. 
 
The means could be a user ARP entry that the app creates with an UninstallString that runs something it copies to the user's AppData folder. Or, it could be a user shortcut to do the same. Or, if you want something the user doesn't trigger, a user Run registry entry to launch a utility that detects if the app has been uninstalled (which could be a challenge). 
 
If the app is installed per user then the "app install" could remove the app, settings and documents but should only remove the app. 
 
Documents are the user's but depending on the app, if a user has no intention of running the app again, the documents might be worthless. You should either leave them or ask. 
 
As for settings, as you point out, they would be useful if the user runs any version of the app in the future. An app should be able to upgrade or ignore settings for a newer or older version. 
 
See this other New Old Thing post for more views on app data. 
 
 
So, to answer your questions:
 
 
 
Both, depending on what the files are.
 
 
Settings: maybe (but can't if the app installed per user). Documents: No.
 
 
Usually the app should create app data, but an exception would be if you want users to know of an "all users" location for their documents.
 
 
 
Only designing the app and installer together produce the best user experience.