Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 7266 invoked from network); 5 Sep 2010 10:02:52 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Sep 2010 10:02:52 -0000 Received: (qmail 66470 invoked by uid 500); 5 Sep 2010 10:02:52 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 65899 invoked by uid 500); 5 Sep 2010 10:02:49 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 65891 invoked by uid 99); 5 Sep 2010 10:02:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Sep 2010 10:02:48 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ustbcoder@gmail.com designates 209.85.212.43 as permitted sender) Received: from [209.85.212.43] (HELO mail-vw0-f43.google.com) (209.85.212.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Sep 2010 10:02:43 +0000 Received: by vws8 with SMTP id 8so2889227vws.30 for ; Sun, 05 Sep 2010 03:02:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=NMNLfbub+rmM1uSc0TcHjXslYg9TOqjQF2lkDMXUEVM=; b=U4cpbuWJa5JLhpAko8lIuUNr/lW5HpfdLNSbUY15/heO75+iTQtdIN0IUXMPZMvhpf VVKYyfFZZmPugtoYo1Zc7S8L6fgGAHi7VM+uMC6p8oYEDZvgCCUxdqOTpp3bdfbnJg8J MD7trmByB8dyLjnoyJTEyupgwW1sszL5Bd2G0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=LmSEr5QxdKCqb3Nnxl6Mr/YnsVlunf1sWXbX4nMiEEDXONs8eRf6ncnYOdV4p5Mh+g Gso8dV30tq7L2MZHsxLR37Z7Yq2+B5g05TeahbInq5KHroO4mbYaFYFbYqzEvlWcTMkp PHzdDOFvwPwMCgQ+zvR14prdnI7UER6saiNEQ= MIME-Version: 1.0 Received: by 10.220.61.7 with SMTP id r7mr1296872vch.147.1283680942434; Sun, 05 Sep 2010 03:02:22 -0700 (PDT) Received: by 10.220.103.16 with HTTP; Sun, 5 Sep 2010 03:02:22 -0700 (PDT) In-Reply-To: References: <3EE16EF73EB5A040A3F18F5599CCC3830155FD3CA708@EXMBXVS4B.campus.mcgill.ca> <4C5EABA8.8020704@cs.mcgill.ca> <4C5F5860.4030007@cs.mcgill.ca> <4C5F7845.8000200@cs.mcgill.ca> Date: Sun, 5 Sep 2010 18:02:22 +0800 Message-ID: Subject: Re: [scxml-eclipse] User Feedback From: Xun Long Gui To: Commons Developers List , jbeard4@cs.mcgill.ca Content-Type: multipart/alternative; boundary=e0cb4e887d1f942a1d048f804236 --e0cb4e887d1f942a1d048f804236 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Yeah, I will add this part, but i think it will take me a while, i will graduate this winter, these days, i was working for my graduate pater, so may be you should wait for a while, sorry for that :-( 2010/9/5 Jacob Beard > Hi Long, > > I just wanted to follow up quickly and find out the current status on the > issues that were raised here. Specifically, is it possible to add > executable > content to transitions in scxml-eclipse? > > Please let me know. Thanks, > > Jake > > 2010/8/8 Jacob Beard > > > Hi Long, > > > > I should mention that I had missed this part of the specification as > > well, and I only recently discovered it while trying to determine how > > best to express static reactions with SCXML. I'm currently updating > > scxml-js to support this. > > > > Jake > > > > On 10-08-08 10:12 PM, Xun Long Gui wrote: > > > Hi Jake, > > > Thanks for your reply. It seems that we should re-define transition E= MF > > data > > > model for this tool, rebuild the tool from the base. I will read SCXM= L > > > transition specification carefully and carry on the rebuild job > > > > > > =D4=DA 2010=C4=EA8=D4=C29=C8=D5 =C9=CF=CE=E79:22=A3=ACJacob Beard =D0=B4=B5=C0=A3=BA > > > > > > > > >> Hi, Long, > > >> > > >> Replies below: > > >> > > >> On 10-08-08 09:06 PM, Xun Long Gui wrote: > > >> > > >>> I do not think we can create a transition without a target, target = is > a > > >>> necessary element for a transition. > > >>> > > >>> > > >> The spec says that the target attribute on transition is not require= d. > > >> In that case, I think the semantics are similar to a Static Reaction= , > as > > >> defined in the paper describing the Rhapsody semantics of statechart= s. > > >> From the spec: > > >> > > >> The identifier(s) of the state or parallel region to transition to. = If > > >> it is omitted, the transition will not cause a change in the state > > >> configuration when it is executed. The executable content contained = in > > >> the transition will still be executed, so the transition will functi= on > > >> as a simple event handler. If the target is present and equal to the > > >> state containing the transition element, the transition will cause t= he > > >> state machine to leave and then re-enter this state. > > >> > > >> From: http://www.w3.org/TR/scxml/#transition > > >> > > >>> To feature 1 and 3 in Chris's commends, we can achieve them, not a > big > > >>> thing. What do you mean about "showstoppers" bug ? > > >>> > > >>> > > >> What I mean is that I think these things are critical to usability. > > >> > > >> Jake > > >> > > >> > > >> --------------------------------------------------------------------= - > > >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > > >> For additional commands, e-mail: dev-help@commons.apache.org > > >> > > >> > > >> > > > > > > > > > --=20 Best Regards Gui Xun Long (=B9=F0=D1=B5=C1=FA) --e0cb4e887d1f942a1d048f804236--