在清单5 中查看此代码。
You can see this code in Listing 4.
您可在清单4中查看代码。
This Seaside task handles the shopping cart checkout. You'll see this code.
这个Seaside任务处理购物车结帐。
You’ll see this code used again and again in the examples I give you on 15 Days of jQuery.
在我的《15天jQuery入门教程》中你将一次又一次在例子中看到这段初始化代码。
You can see how this is all drawn together in the code archive.
您可以在代码归档 中看到如何将这些内容整合在一起。
You can see from this code that APF depends on the four parameters discussed above.
可以从这段代码中看到，APF依赖于上面讨论的这四个参数。
In this code you see the asynchronous version of your interface being called.
在这段代码中，您看到了被调用接口的异步版本。
As you can see, this code directly manipulates styles, which is not good, as that job should be left to CSS.
如您所见，这个代码直接操作样式，这不太好，因为这种工作应该留给CSS完成。
To get a better understanding of this, see the sample code given in Listing 2.
为了更好地理解这一点，请参见清单2中给出的示例代码。
In Listing 12, you should see some similar code, yet this code has logic for mapping a list of test cases.
在清单12中，您将看到一些非常类似的代码，不过这些代码的逻辑是用来映射一个测试用例列表的。
You may be testing this code to see the results of this effort firsthand.
您可以测试这段代码以直接查看这次尝试的结果。
Because of this, you can see the SQL statements as the code adds this new entry to the filesystem.
鉴于此，当代码将此新条目添加到文件系统中时，您可以看到sql语句。
You can run code with this switch to see how much work will be necessary to port code to 3.0.
你可以使用该开关来运行代码，来看看要将代码移植到3.0需要做多少工作。
You can see this when you run the code in listing 2.
你运行清单2的代码就会看到这一点。
You can see from this chart that the initial code import occurred in early 1999.
从这个图表中可以看出，代码最初是在1999年初导入的。
When you first run this code, you'll see a screen similar to Figure 1.
第一次运行这段代码时，您会看到类似于图1的屏幕。
Now that we saw how to define a namespace for the code within a file, let's see how to leverage this namespaced code within an application.
现在我们已经了解了如何在一个文件中定义代码的名称空间，接下来让我们看看如何在应用程序中利用这个使用名称空间的代码。
You are doing it this way to see how your code is visualized as an UML model.
你要用这种方法来搞清楚你的代码是如何可视化为uml模型的。
As you can see, this is very similar to the code in Listing 3.
如您所见，这段代码与清单3中的代码十分相似。
You can also download this code; see Resources.
您也可以下载该代码；参阅参考资料。
Use this basic script (see the code archive) to keep track of several characters and NPCs.
使用此基本脚本(请参阅代码归档)跟踪几个角色和NPC。
This time, you will see a code for the Hindi language.
这次，您将看到针对印地语的代码。
You can download all the relevant code for this and previous columns; see the sidebar, Getting the code.
您可以下载有关这篇文章以及以前专栏文章的所有相关代码；请参阅副栏获取代码。
For links to this code along with more information, see Resources.
代码的链接和更多信息参见参考资料。
Instead of spending time explaining how to convert this file into styled HTML, it is left as an exercise for you to see how this code takes the XML file and generates HTML.
我们不再浪费时间解释如何将该文件转化成HTML，作为一个练习，读者可以自己了解下面的代码如何使用XML文件并生成HTML。
You'll see this type of code flow later in the article when you use the TestCaller class to define a customized test suite.
在本文后面使用Test Caller类定义定制的测试套件时，您会看到这种代码。
Because we are using the document literal non-wrapped binding style instead of the document literal wrapped binding style typically used in Integration Developer, we see this unexpected code.
由于我们使用的是文档文字非封装式绑定风格而非IntegrationDeveloper中常用的文档文字封装式绑定风格，我们看到的不是预期的代码。
This properties file (see code Listing 1) should contain two key value pairs
该属性文件（参见代码清单1 的代码）应该包含两个关键的值对
As you can see from this code, the ContentProvider class expects an array of org.eclipse.wst.server.core.IServer elements to be set as an input.
如您从此代码中看到的，contentprovider类期望将一列org . eclipse . wst . server . core . IServer要素设置为输入。
Next, we check the result code to see if this event relates to a successful query.
接下来，检查结果代码，看看这个事件是否与成功的查询有关。
应用推荐