This project is in a trial period, be cautious while contributing. Setup can still change before being approved as a libre project.
Zen

Translation

(macOS users, remember that as noted in :doc:`Tutorial 3 <tutorial-3>`, for the tutorial we recommend running ``briefcase package`` with the ``--adhoc-sign`` flag to avoid the complexity of setting up a code signing identity and keep the tutorial as simple as possible.)
131/2700 · 270

Sign in to save the translation.

English Chinese (Simplified) Actions
However, if you run ``briefcase run``, the dialog box won't appear.
但是，如果运行``briefcase run``，对话框就不会出现。
Why is this? Well, ``briefcase dev`` operates by running your code in place - it tries to produce as realistic runtime environment for your code as possible, but it doesn't provide or use any of the platform infrastructure for wrapping your code as an application. Part of the process of packaging your app involves copying your code *into* the application bundle - and at the moment, your application still has the old code in it.
为什么会这样？简易开发包 "通过就地运行您的代码来运行--它试图为您的代码提供尽可能逼真的运行环境，但并不提供或使用任何平台基础架构来将您的代码包装成应用程序。打包应用程序的部分过程包括将代码复制到应用程序捆绑包中，目前，您的应用程序中仍有旧代码。
So - we need to tell briefcase to update your app, copying in the new version of the code. We *could* do this by deleting the old platform directory and starting from scratch. However, Briefcase provides an easier way - you can update the code for your existing bundled application:
因此，我们需要告诉公文包更新应用程序，复制新版本的代码。我们可以删除旧的平台目录，然后从头开始。不过，Briefcase 提供了一种更简单的方法--您可以更新现有捆绑应用程序的代码：
If Briefcase can't find the scaffolded template, it will automatically invoke ``create`` to generate a fresh scaffold.
如果 Briefcase 找不到脚手架模板，它会自动调用 ``create`` 生成一个新的脚手架。
Now that we've updated the installer code, we can then run ``briefcase build`` to re-compile the app, ``briefcase run`` to run the updated app, and ``briefcase package`` to repackage the application for distribution.
更新了安装程序代码后，我们就可以运行 ``briefcase build`` 来重新编译应用程序，运行 ``briefcase run`` 来运行更新后的应用程序，并运行 ``briefcase package`` 来重新打包应用程序以便分发。
(macOS users, remember that as noted in :doc:`Tutorial 3 <tutorial-3>`, for the tutorial we recommend running ``briefcase package`` with the ``--adhoc-sign`` flag to avoid the complexity of setting up a code signing identity and keep the tutorial as simple as possible.)
(macOS 用户请记住，正如 :doc:`Tutorial 3<tutorial-3>` 中所述，我们建议在运行 ``briefcase package`` 时使用 ``--adhoc-sign`` 标志，以避免设置代码签名身份的复杂性，并使教程尽可能简单）。
Update and run in one step
更新和运行一步到位
If you're rapidly iterating code changes, you'll likely want to make a code change, update the application, and immediately re-run your application. For most purposes, developer mode (``briefcase dev``) will be the easiest way to do this sort of rapid iteration; however, if you're testing something about how your application runs as a native binary, or hunting a bug that only manifests when your application is in packaged form, you may need to use repeated calls to ``briefcase run``. To simplify the process of updating and running the bundled app, Briefcase has a shortcut to support this usage pattern - the ``-u`` (or ``--update``) option on the ``run`` command.
如果要快速迭代代码更改，很可能需要更改代码、更新应用程序并立即重新运行应用程序。对于大多数情况来说，开发人员模式 (``briefcase dev``) 是进行这种快速迭代的最简单方法；但是，如果您要测试应用程序作为本地二进制文件运行的方式，或查找一个只有在应用程序打包时才会出现的错误，您可能需要反复调用 ``briefcase run``。为了简化更新和运行打包应用程序的过程，Briefcase 提供了支持这种使用模式的快捷方式 - ``run``命令上的 ``-u``（或 ``--update``）选项。
Let's try making another change. You may have noticed that if you don't type a name in the text input box, the dialog will say "Hello, ". Let's modify the ``say_hello`` function again to handle this edge case.
让我们尝试做另一个改动。您可能已经注意到，如果您不在文本输入框中输入姓名，对话框就会显示 "Hello, "。 让我们再次修改 ``say_hello`` 函数，以处理这种边缘情况。
At the top of the file, between the imports and the ``class HelloWorld`` definition, add a utility method to generate an appropriate greeting depending on the value of the name that has been provided::
在文件顶部，在导入和 "类 HelloWorld "定义之间，添加一个实用程序方法，以根据所提供的名称值生成适当的问候语：：
Then, modify the ``say_hello`` callback to use this new utility method::
然后，修改 ``say_hello`` 回调，以使用这个新的实用程序方法：：

Loading…

User avatar None

String added in the repository

  1. BeeWare
  2. Tutorial
  3. Tutorial 4
  4. Chinese (Simplified)
(macOS users, remember that as noted in :doc:`Tutorial 3 <tutorial-3>`, for the tutorial we recommend running ``briefcase package`` with the ``--adhoc-sign`` flag to avoid the complexity of setting up a code signing identity and keep the tutorial as simple as possible.)
(macOS 用户请记住，正如 :doc:`Tutorial 3<tutorial-3>` 中所述，我们建议在运行 ``briefcase package`` 时使用 ``--adhoc-sign`` 标志，以避免设置代码签名身份的复杂性，并使教程尽可能简单）。
4 months ago
Browse all string changes

Things to check

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English Chinese (Simplified)
No related strings found in the glossary.

String information

Flags
rst-text
Source string location
../../tutorial/tutorial-4.rst:126 • 2013bac3f9464f479195b31a11bcd4c9
String age
4 months ago
Last updated
10 days ago
Source string age
4 months ago
Translation file
docs/locales/zh_CN/LC_MESSAGES/tutorial/tutorial-4.po, string 20