Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1399610CC1 for ; Tue, 3 Dec 2013 01:12:52 +0000 (UTC) Received: (qmail 76477 invoked by uid 500); 3 Dec 2013 01:12:51 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 76449 invoked by uid 500); 3 Dec 2013 01:12:51 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 76432 invoked by uid 99); 3 Dec 2013 01:12:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Dec 2013 01:12:51 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FRT_ADOBE2,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.220.178] (HELO mail-vc0-f178.google.com) (209.85.220.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Dec 2013 01:12:45 +0000 Received: by mail-vc0-f178.google.com with SMTP id lh4so8948905vcb.23 for ; Mon, 02 Dec 2013 17:12:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=aaIA2uF+6+tNhrD/rWRdQ8No4VtORjG5QziPTncMEqQ=; b=CIBh/vUGC1QS4WsufH/JVNPrLV2FAZIofRBNWcgtDhOZp+r2Jos6xD0RjV6ZEPJmWx DYE1N6iIoQYvGKWWHLnbNUTxz27W8IAXpgO0RiSIAk9i8Z3PaF47Q5S0eQYwqeF5m4NA rdoRyW98Gb/7fnsX+CFZpqY9IWt+r5dhjCSBOltWgGeWubo6OfJyWSSEMxzFyxctkrXG BQaOWCXPblTLva+J0BPmCrNMT91CRYVRKTiBQo9v6Zzm5IucXdByf/nLv4TAGmPlTsqI X8iPwO2oT9gChHncZF9JzAA/JPMGseDF6NS8wT+yiHThV0znuujm1gceu4YwFItCUDBm IlTg== X-Gm-Message-State: ALoCoQnEVmu6qAsXpr4BWS7+0hLLSEfwGAc0PIDpa06cMJyHmqYblOhMs87QYAeReGwYw977onbe MIME-Version: 1.0 X-Received: by 10.221.19.5 with SMTP id qi5mr53328467vcb.15.1386033143404; Mon, 02 Dec 2013 17:12:23 -0800 (PST) Received: by 10.58.144.194 with HTTP; Mon, 2 Dec 2013 17:12:23 -0800 (PST) X-Originating-IP: [173.10.39.57] In-Reply-To: <149F8129B58B2D418508E63117D9C541B2231CB184@nambx05.corp.adobe.com> References: <149F8129B58B2D418508E63117D9C541B2231CB184@nambx05.corp.adobe.com> Date: Mon, 2 Dec 2013 20:12:23 -0500 Message-ID: Subject: Re: MXML spec (was: RE: Donation News) From: Nicholas Kwiatkowski To: dev@flex.apache.org Content-Type: multipart/alternative; boundary=001a11337b3e28f12e04ec96fdaa X-Virus-Checked: Checked by ClamAV on apache.org --001a11337b3e28f12e04ec96fdaa Content-Type: text/plain; charset=ISO-8859-1 They usually prefer txt, but if it has any markup, then RTF. -Nick On Mon, Dec 2, 2013 at 6:15 PM, Gordon Smith wrote: > The MXML spec is a Microsoft Word document. Can we put such documents in > an Apache repo? If not, do we want the spec to live in the repo in some > other format? Or in our wiki? Or on a non-wiki web page? > > - Gordon > > -----Original Message----- > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash > Muppirala > Sent: Monday, December 02, 2013 11:39 AM > To: dev@flex.apache.org > Subject: Re: Donation News > > On Mon, Dec 2, 2013 at 10:51 AM, Gordon Smith wrote: > > > The spec I wrote is for MXML 2006 and MXML 2009 (with various sections > > remaining incomplete) and it also contains proposals for a new dialect > > to fix various inconsistencies. It doesn't cover MXMLG/FXG, but I > > think Adobe had a spec for that and maybe Alex could arrange for it to > > be donated as well. > > > > > Thanks for the info, Gordon. I have been asking for the MXMLG/FXG spec > for a while now. So, if that is something that could be donated, it will > be of a big help for the FlexJS project. > > Alex, my intention is to write an XSLT translator to make MXMLG/FXG and > SVG to seamlessly work together. I have the beginnings of such an XSLT > available here [1] and a basic example here[2] > > But if we have a programatic spec for FXG available, I can plug it in into > a tool like Altova MapForce [3] to automatically generate an XSLT for FXG > <-> SVG conversion. This would speed up things a lot and makes visual > fidelity matching between Flash and HTML5 apps that much closer. > > Thanks, > Om > > > [1] > > https://github.com/apache/flex-asjs/blob/develop/fxg2svg/transform/transform.xslt > [2] http://people.apache.org/~bigosmallm/fxg2svg/svg.html > [3] http://www.altova.com/mapforce.html > > > > - Gordon > > > > -----Original Message----- > > From: Alex Harui [mailto:aharui@adobe.com] > > Sent: Thursday, November 28, 2013 12:00 AM > > To: dev@flex.apache.org > > Subject: Re: Donation News > > > > > > > > On 11/27/13 11:55 PM, "OmPrakash Muppirala" > wrote: > > > > >Alex, > > > > > >What a great news, right in time for Thanksgiving! Thanks for > > >getting this through. > > It isn't "through" yet. It just means that I've pulled out all the > > un-donatable stuff I could find and now it is time for Adobe Legal and > > others to review it. > > > > > >What format is the MXML spec in? > > MS Word. > > >Does it include MXMLG/FXG? > > Not sure. Gordon wrote it. > > > > -Alex > > > > > --001a11337b3e28f12e04ec96fdaa--