Dealer.agent.xml

最新推荐文章于 2022-03-21 10:12:05 发布
原创 最新推荐文章于 2022-03-21 10:12:05 发布 · 169 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#XML #Access #UP

本文介绍了一个基于JADE平台实现的21点游戏智能体系统。该系统详细展示了如何通过智能体之间的交互来模拟真实世界的21点游戏流程，包括玩家加入游戏、下注、发牌等过程。
<!--
<H3>The blackjack dealer controls the game.</H3>

The dealer registers itself at the DirectoryFacilitator
and waits for player agents to join the table.
-->
<agent xmlns="http://jadex.sourceforge.net/jadex"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://jadex.sourceforge.net/jadex
http://jadex.sourceforge.net/jadex-0.96.xsd"
name="Dealer"
package="jadex.examples.blackjack.dealer">

<imports>
<import>jadex.examples.blackjack.*</import>
<import>jadex.examples.blackjack.gui.*</import>
<import>jadex.runtime.*</import>
<import>jadex.planlib.*</import>
<import>jadex.util.*</import>
<import>jadex.adapter.fipa.*</import>
<import>java.util.logging.*</import>
<import>java.util.*</import>
</imports>

<capabilities>
<!-- this capability provides easy access to "out-of-the-box"-plans
allowing - for example - to register at the DF. -->
<capability name="dfcap" file="jadex.planlib.DF"/>
</capabilities>

<!--
These are the dealers beliefs. None of these beliefs should be edited in the ADF
because all beliefs are initialised by the plans during the game or have
expedient start-up values (like the three beliefs below).
-->
<beliefs>
<!-- The card set used to play the game. -->
<belief name="cardset" class="CardSet" />

<!-- The number of seconds to wait for answers from players. -->
<belief name="playerwaitmillis" class="long">
<fact>(Integer)$propertybase.getProperty("standard.timeout")</fact>
</belief>

<!-- The number of seconds to wait before drawing a card.
Can be adjusted in the GUI. -->
<belief name="stepdelay" class="int">
<fact>1</fact>
</belief>

<!-- When set to true, each step in the game must be manually
issued in the GUI. -->
<belief name="singleStepMode" class="boolean">
<fact>false</fact>
</belief>

<!-- The self representation of the dealer. -->
<belief name="myself" class="Dealer">
<fact>new Dealer()</fact>
</belief>

<!-- The players. -->
<beliefset name="players" class="Player"/>

<!-- The history of played games. -->
<belief name="statistics" class="GameStatistics">
<fact>new GameStatistics()</fact>
</belief>

<belief name="gamestate" class="GameState">
<fact>new GameState($beliefbase.myself, null)</fact>
</belief>

<belief name="gui" class="DealerFrame"/>

<!--
It's possible that a few different manager (possibly from remote Players)
want to track their players during the game, therefor a beliefset containing
all manager-AIDs is needed.
-->
<beliefset name="tracker" class="AgentIdentifier"/>

</beliefs>

<!--
The dealer has only one initial goal: registering a
dealing-service at the DF and renew this registration
every 10 seconds.
-->
<goals>
<!-- Main goal to play a game. -->
<performgoal name="play_game" exclude="never" retrydelay="3000">
<contextcondition>
$beliefbase.players.length > 0
</contextcondition>
</performgoal>

<!-- Goal to play with a single player (in the context of a larger game). -->
<performgoal name="play_with_player">
<parameter name="player" class="Player"/>
</performgoal>

<!-- Used for registering the dealer at the df. -->
<achievegoalref name="df_register">
<concrete ref="dfcap.df_register"/>
</achievegoalref>
<!-- Used for deregistering the dealer at the df. -->
<achievegoalref name="df_deregister">
<concrete ref="dfcap.df_deregister"/>
</achievegoalref>
</goals>

<!--
These are all the plans, the dealer will execute during a game.
There is one plan for every major task. Have a look into the
plan-classes to get a detailed insight in whats going on there.
-->
<plans>
<!-- Register a player. -->
<plan name="register_plan">
<body class="DealerRegisterPlayerPlan" />
<!-- <body>new DealerRegisterPlayerPlan()</body>-->
<trigger>
<messageevent ref="request_join" />
</trigger>
</plan>

<!-- Play a game. -->
<plan name="play_game_plan">
<body class="DealerGameRoundMasterPlan" />
<!-- <body>new DealerGameRoundMasterPlan()</body> -->
<trigger>
<goal ref="play_game"/>
</trigger>
</plan>

<!-- Play a game with a single player. -->
<plan name="play_with_player_plan">
<parameter name="player" class="Player">
<goalmapping ref="play_with_player.player"/>
</parameter>
<body class="DealerGameRoundPlayerPlan" />
<!-- <body>new DealerGameRoundPlayerPlan()</body>-->
<trigger>
<goal ref="play_with_player"/>
</trigger>
<!-- <contextcondition>
$beliefbase.getBeliefSet("players").containsFact($plan.player)
&& !$plan.player.getState().equals(Player.STATE_IDLE)
</contextcondition>-->
<contextcondition>
$beliefbase.getBeliefSet("players").containsFact($plan.player)
&& !$plan.player.getState().equals(Player.STATE_IDLE)
</contextcondition>
</plan>

<plan name="propagate_game_state_plan">
<body class="PropagateGameStatePlan" />
<!-- <body>new PropagateGameStatePlan()</body> -->
<trigger>
<beliefchange ref="myself"/>
<beliefsetchange ref="players"/>
</trigger>
<!-- not possible because game must always be updated. -->
<!--<precondition>$beliefbase.players.length>0</precondition>-->
</plan>
</plans>

<!-- events -->
<events>

<!-- Event to trigger a step. -->
<internalevent name="step"/>

<!-- player messages -->
<!-- Player request to join the game. -->
<messageevent name="request_join" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REQUEST</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestJoin.class</value>
</parameter>
</messageevent>

<!-- A player wants to draw another card. -->
<messageevent name="request_draw" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REQUEST</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestDraw.class</value>
</parameter>
</messageevent>

<!-- A player makes a bet. -->
<messageevent name="request_bet" direction="send" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REQUEST</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<!--<parameter name="reply-with" class="String" direction="inout">
<value>SFipa.createUniqueId($scope.getAgentName())</value>
</parameter>-->
<parameter name="conversation-id" class="String" direction="inout">
<value>SFipa.createUniqueId($scope.getAgentName())</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestBet.class</value>
</parameter>
</messageevent>


<messageevent name="refuse_bet" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REFUSE</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestBet.class</value>
</parameter>
</messageevent>

<!-- A player has finished its game (i.e. doesn't want to draw any more cards). -->
<messageevent name="request_finished" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REQUEST</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestFinished.class</value>
</parameter>
</messageevent>

<!-- todo: manager messages -->

<!-- The manager is shutting down the BlackJack application. -->
<messageevent name="inform_shutdown" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.INFORM</value>
</parameter>
<parameter name="content-start" class="String" direction="fixed">
<value>"manager:shutDown"</value>
</parameter>
</messageevent>
<!-- The manager registers as tracker on game settings. -->
<messageevent name="query_tracking" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.QUERY_REF</value>
</parameter>
<parameter name="content-start" class="String" direction="fixed">
<value>"manager:registerAsTracker"</value>
</parameter>
</messageevent>

<!-- sent messages -->

<!-- inform a player about a the game result -->
<messageevent name="inform_action_done" direction="send_receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.INFORM</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>Done.class</value>
</parameter>
</messageevent>

<!-- inform a player about a the game result -->
<messageevent name="refuse_action" direction="send" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REFUSE</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
</messageevent>

<!-- inform tracker about playing players -->
<messageevent name="inform_tracker" direction="send" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.INFORM</value>
</parameter>
<parameter name="content" class="String" direction="in" />
</messageevent>

<messageevent name="inform_game_state" direction="send" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.INFORM</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="conversation-id" class="String" direction="inout">
<value>SFipa.createUniqueId($scope.getAgentName())</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>GameState.class</value>
</parameter>
</messageevent>

</events>

<expressions>

<!-- The player that gets the next card (if any). -->
<expression name="turnplayer">
select one Player $p from $beliefbase.players
where $p.getState().equals(Player.STATE_PLAYING)
order by $p.getCards().length
</expression>

<!-- Check if it is the dealer's turn. -->
<condition name="dealers_turn">
// The dealer may draw its initial card when all players have two cards.
$beliefbase.myself.getCards().length==0 &&
(select one Player $p from $beliefbase.players
where !$p.getState().equals(Player.STATE_IDLE) && $p.getCards().length!=2)
== null

// The dealer may draw more cards, when all players are either idle or finished.
|| (select one Player $p from $beliefbase.players
where !$p.getState().equals(Player.STATE_IDLE) && !$p.getState().equals(Player.STATE_FINISHED))
== null
</condition>

<!-- Check if it is the $player's turn. -->
<condition name="players_turn">
// All players must be idle, playing, or finished.
(select one Player $p from $beliefbase.players
where !$p.getState().equals(Player.STATE_IDLE)
&& !$p.getState().equals(Player.STATE_PLAYING)
&& !$p.getState().equals(Player.STATE_FINISHED))
== null

// And this player must be the first with the least number of cards.
// Hack !!! Assume "any" selects players in order.
&& (select one Player $p from $beliefbase.players
where $p.getState().equals(Player.STATE_PLAYING)
&& $p.getCards().length<=$player.getCards().length
order by $p.getCards().length)
== $player
<parameter name="$player" class="Player"/>
</condition>

<!-- Check if the dealer has drawn its first card. -->
<condition name="dealer_card">
$beliefbase.myself.getCards().length==1
</condition>

<!-- Check if the dealer has finished drawing cards. -->
<condition name="dealer_finished">
$beliefbase.myself.getState().equals(Player.STATE_FINISHED)
|| $beliefbase.myself.getState().equals(Player.STATE_IDLE)
</condition>

</expressions>

<properties>
<!-- logging-properties, needed to debug the application.
Start the Jadex-Logging-Agent to see whats going on behind the scenes -->
<!--<property name="logging.level">Level.INFO</property>-->
</properties>

<configurations>
<configuration name="default">
<beliefs>
<initialbelief ref="gui">
<fact>new DealerFrame($beliefbase.myself, $agent.getExternalAccess())</fact>
</initialbelief>
</beliefs>
<goals>
<!-- Register the dealer at the df on startup. -->
<initialgoal ref="df_register">
<!-- The services to register. -->
<parameter ref="description">
<value>
<!-- This is the agent-description for the dealer. With this description
the dealers is registered at the directory facilitator.
Note, that the dealer only offers one service, that is 'dealing'
(see service description below). -->
SFipa.createAgentDescription(null,
SFipa.createServiceDescription("dealing", "blackjack", "University of Hamburg"))
</value>
</parameter>
</initialgoal>
<initialgoal ref="play_game"/>
<endgoal ref="df_deregister"/>
</goals>
</configuration>
</configurations>

</agent>
经销商管理系统架构设计方案（附 Java版本和Python版本源代码详解）
AI天才研究院
06-25 1174
随着市场竞争的日益激烈，企业对经销商的管理越来越重视。传统的经销商管理方式效率低下，信息滞后，难以适应现代企业的发展需求。为了提高经销商管理效率，降低运营成本，越来越多的企业开始采用信息化的手段来管理经销商，而经销商管理系统应运而生。经销商管理系统（Dealer Management System，DMS）是帮助企业管理经销商网络的软件系统。它可以帮助企业实现对经销商信息、产品信息、订单信息、库存信息、售后服务等方面的全面管理，提高企业对经销商网络的掌控能力，提升企业运营效率和市场竞争力。
Linux环境安装FastDFS及整合Nginx遇到的bug及解决方法
01-09
问题1： ERROR – file: storage_ip_changed_dealer.c, line: 163, connect to tracker server xx.xx.xx.xx:22122 fail, errno: 4, error info: Interrupted system call 或ERROR – file: storage_ip_changed_...
Proxy 和 Agent 区别
热门推荐
木木
05-25 1万+
<br />Agent 代理 通常指与用户接口的客户端程序<br />Proxy 代理 接收用户请求并将请求发给服务器,然后接收服务器回应并返回给用户 实际上Proxy的功能就是代替用户访问服务器,用户被隐藏.
游戏服务端究竟解决了什么问题？
wubaohu1314的博客
09-13 601
https://www.fgba.net/sitemap.xml
springboot的maven多模块项目架构微服务搭建——依赖方式的多模块演化为微服务项目...
zuixiaoyao_001的博客
12-03 5125
在上一篇依赖方式多模块的基础上对项目进行改造。主要改造user-service项目，service要配置mapper。mybatis及数据库相关的东西，后面的接口消费方user就不再需要了 注意：以下代码是在不同场所的机器上写的，数据库什么的会有不同，结构也会有不同，最终的代码会以其中一个传递到本人git上，这里记录的是本人总结的一些思路什么的，稍微修改配置，配置一致，就可以运行的 代码...
mysql服务异常中止_数据库服务异常停止分析
weixin_39612554的博客
01-27 1288
sqlserver数据库服务异常停止分析背景2019年11月13日早上9:37分钟，我们的运维监控系统告警提示某项目数据库服务1433端口无法访问，我们赶紧登陆服务器查看详情，发现数据库服务以及数据库agent服务都已停止，重新手工启动对应的服务恢复生产。接下来我们就需赶紧分析引起这个问题的原因以及如何去修复；服务器环境情况如下：Microsoft SQL Server 2017 (RTM-CU1...
企业微信url及生成授权链接
wewewe14的博客
09-13 1万+
企业微信第三方开发课程 14-18 一、简介 这里主要分为四部分，验证 url 有效性、完成用户的测试安装、获取生成预授权码、生成授权安装链接。这几部就可以完成第三方有用的回调和安装，这也是后续功能开发的基础。 二、Get 请求验证 URL 有效性 1.为什么要搭建回调服务 在集成企业微信与内部系统时，搭建一个回调服务可以获取到用户通过企业微信发送给应用的消息： 自定义丰富的服务行为。比如，用户向应用发消息时，识别消息关键词，回复不同的消息内容； 用户点击应用菜单时，转化为指令，执行自动化任务。 可以及时
linux7下nenux3.14的maven私服搭建和配置使用
zuixiaoyao_001的博客
10-27 2992
&#13; 　　为什么用私服，各种帖子很多，话不多说，直接奉上本博主的搭建过程。 　　一、环境准备：确保jdk和maven安装完成 　　二、下载nenux；地址：https://www.sonatype.com/download-oss-sonatype?hsCtaTracking=920dd7b5-7ef3-47fe-9600-10fecad8aa32%7Cf59d5f1...
java List<Map<String,Object>
weixin_30535913的博客
01-03 164
xml <select id="selectShopList" resultType="java.util.HashMap"> SELECT p.PARTY_NAME partyName, c.CUSTOMER_NAME customerName, s.SHOP_ID shopId, s.SHOP_NAME shopNam...
SpringBoot实现小程序微信支付（超级详细）
03-21 1万+
SpringBoot微信支付开发
js怎么断言scope.row.dealer.short_name一定有值
10-19
上述代码首先检查`scope.row`, `scope.row.dealer`, 和 `scope.row.dealer.short_name`是否存在并非`undefined`。如果发现短名存在，就继续；若不存在，`assert`抛出异常，我们可以捕获这个异常并在控制台输出错误...
org.apache.kyuubi.KyuubiSQLException: Error operating ExecuteStatement: org.apache.spark.sql.catalyst.parser.ParseException: mismatched input 'AS' expecting {<EOF>, ';'}(line 412, pos 28) == SQL == CREATE TABLE orca01_dr_data.ads_rpt_fsm_sfm_kpi_funnel_dmo_t_1218 stored as parquet with dealership_full as ( select distinct dealer_id ,region_code ,dealer_short_name ,dealer_short_name_en ,region_bmw_sale ,region_mini_sale ,region_moto_sale ,region_bmw_sale_en ,region_mini_sale_en ,region_moto_sale_en ,small_region_bmw_sale_en ,small_region_mini_sale_en ,small_region_moto_sale_en ,dealer_investor_name_en ,organization_id ,investor_id from cdl.cdl_dim_com_dmx_dealership_full_t where pday='20251124' ), emp_delear as ( select distinct emp.company_id ,emp.id ,emp.emp_name ,dealer.dealer_id ,dealer.organization_id ,dealer.region_bmw_sale_en ,dealer.region_mini_sale_en ,dealer.region_moto_sale_en ,dealer.small_region_bmw_sale_en ,dealer.small_region_mini_sale_en ,dealer.small_region_moto_sale_en ,dealer.investor_id from dwc.dwc_dim_com_dmo2_t_employee_full_t as emp left join dealership_full as dealer on emp.company_id=dealer.organization_id where emp.pday='20251124' ) ,funnel_base as ( select month_id ,brand_code ,series_code ,eseries_code ,dim_geo_type ,dim_geo_code ,dim_geo_name_cn ,dim_geo_name_en ,data_agg_type ,source_type ,leads_vol ,leads_vol_lm ,leads_vol_ly ,leads_vol_mom ,leads_vol_yoy ,leads_oppty_conv_rate ,leads_oppty_conv_rate_mom ,leads_oppty_conv_rate_yoy ,oppty_vol ,oppty_vol_lm这个报错啥意思
最新发布
11-25
ON emp.company_id = dealer.organization_id WHERE emp.pday = '20251124' ), funnel_base AS ( SELECT month_id, brand_code, series_code, eseries_code, dim_geo_type, dim_geo_code, dim_geo_name_cn...
with orders as ( select orders.order_id --订单id ,orders.brand_code_ssc --订单品牌 ,orders.series_code_ssc --订单车系 ,orders.eseries_code_ssc --订单车型 ,orders.model_code_ssc ,orders.create_date --订单创建时间 ,orders.first_confirm_date --订单首次确认时间 ,orders.handover_date --订单交车时间 ,orders.so_no --订单号 ,orders.dealer_id order_dealer_id --订单经销商id ,dealer.dealership_name_cn ,dealer.province_name_zh --省份名称（中文） ,dealer.city_name_zh --城市名称（中文） ,dealer.region_name_zh --所属区域（中文） ,dealer.investor_name_zh --集团名中文 ,dealer.sales_bmw_small_area_name_zh --BMW销售小区中文全称 ,orders.spark_id --订单sparkid ,orders.drawer_id --订单开票人id ,orders.drawer_mobile_phone_number --订单开票人手机号 ,orders.drawer_customer_mobile --订单开票人客档手机号 ,orders.customer_mobile --客档手机号 ,orders.oppty_spark_id --订单机会spark id ,orders.oppty_customer_number --机会客档手机号 ,orders.vin_17 --订单vin17 from dwc.dwc_fact_sal_ncs_order_sales_t orders left join cdl.cdl_dim_com_ssc_dealership_full_t dealer on dealer.pday = '{$fday}' and orders.dealer_id = dealer.nsc_no where orders.pday = '{$pday}' and orders.so_status = '14041007' --已交车 handover_intake_flag='Y' and orders.business_type = '14031001' --订单销售类型：一般销售 --and orders.handover_cancel_flag='N' --订单未取消(退车订单也算) and orders.sale_type = '20141003' --普通零售 and orders.brand_code_ssc = 'BMW' and to_date(orders.handover_date) = from_unixtime(unix_timestamp('{$pday}', 'yyyyMMdd'), 'yyyy-MM-dd') --当天交车数据 --and to_date(orders.handover_date) >= '2025-07-01' --(刷数使用) CPS将与2025-07-01正式生效 )这啥意思
10-29
3. **`JOIN` 操作**：通过 `JOIN` 关键字将 `orders` 表和 `dealers` 表关联起来，关联条件是 `o.dealer_id = d.dealer_id`，即订单表中的经销商 ID 等于经销商表中的经销商 ID。 4. **`WHERE` 子句**：用于筛选符合...
zotero与word集成
图灵门徒
09-11 917
Manually Installing the Zotero Word Plugin for Windows To install the plugin by hand, first download the plugin: * Install the Word Plugin for Windows for Zotero 2.0 Once the plugi...
society of mind
图灵门徒
08-08 773
To appear in the journal Computing and Informatics. Examining the Society of Mind Push Singh 28 October 2003 push@mit.edu Media Lab Massachusetts Institute of Technology 20 Ames Street C...
booktrading / common
图灵门徒
03-29 553
&lt;html&gt;&lt;head&gt;&lt;title&gt; jadex.examples.booktrading.common &lt;/title&gt;&lt;/head&gt;&lt;body&gt; This package contains classes used by buyer and seller agents of thebooktrading scenar...
Snowball分词
图灵门徒
08-22 496
using System; using Lucene.Net.Analysis; using Lucene.Net.Analysis.Standard; using SF.Snowball.Ext; using System.Collections.Generic; using System.Collections; using OpenNLP.Tools.PosTagger; ...
losing in the process
图灵门徒
08-10 388
Losing the Productin the Processew researchers would dare dispute that the process movement has done wonders toimprove the teaching of writing.Emig’s The Composing Processes of TwelfthGraders and othe...
chapter 19 1/4
图灵门徒
08-10 374
Chapter 19The Process Approach to Writing Instruction Examining Its EffectivenessRuie J.Pritchard and Ronald L. HoneycuttOur goal in this chapter is to reviewand research on the writing pro...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值