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 1AB81EDC8 for ; Wed, 6 Mar 2013 19:08:50 +0000 (UTC) Received: (qmail 37752 invoked by uid 500); 6 Mar 2013 19:08:49 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 37614 invoked by uid 500); 6 Mar 2013 19:08:49 -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 37606 invoked by uid 99); 6 Mar 2013 19:08:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 19:08:49 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.223.177] (HELO mail-ie0-f177.google.com) (209.85.223.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 19:08:43 +0000 Received: by mail-ie0-f177.google.com with SMTP id 16so10021291iea.36 for ; Wed, 06 Mar 2013 11:08:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=v87ZeSYEUYO6/BvSJqNi4tkuNVGBXhyFiHDLQK6a7AY=; b=lz9l8sZAzqeXFThmOnCBNhbsblwD4v0LyPKIJNcj5+RKnwBl0iDaQnFtl35j9S6qRN dh2UOKUTqK4NC+zc2ehhHD1XMlJkZI8+qEL4kmKmTbBqni3rLvKI18xo3Ei0iVUHePo4 3lkSx0djo5GZ+QoPKrXNs8OT9celLHuNLu7jcQGnp7y1arH+XAXqgLQSQZ+cZZP0eKI9 r1xmuVpV0/bVVOsfPOJal5YnlJJu00A95G79QIf88W9C236pOd4cG5/7V6Y7JckIYqT+ zWw3hqGUy2Bgx3HBcXZAbiESIX2IKTRMqf8gNRsEwCCiz4F1c1cl32cX2qY4L6YV6Cji 7LWg== MIME-Version: 1.0 X-Received: by 10.50.88.199 with SMTP id bi7mr11916383igb.70.1362596903048; Wed, 06 Mar 2013 11:08:23 -0800 (PST) Received: by 10.64.226.131 with HTTP; Wed, 6 Mar 2013 11:08:22 -0800 (PST) In-Reply-To: <20130306140103.18354npg2tbr93sf@franklin.liquidweb.com> References: <20130306133020.13622fks0ccbivjw@franklin.liquidweb.com> <20130306134932.46054rofrgugt9z0@franklin.liquidweb.com> <20130306135428.36024gqbqaahiaxw@franklin.liquidweb.com> <20130306140103.18354npg2tbr93sf@franklin.liquidweb.com> Date: Wed, 6 Mar 2013 20:08:22 +0100 Message-ID: Subject: Re: [FalconJx] MXML output - FlexJS From: Erik de Bruin To: "dev@flex.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkovr6zjrsccYrDt/psbbCbfO0QWv6Ec5V8d9mvgAs9PJzu9pXfd19Mr5lzNvW+UqiFiwk0 X-Virus-Checked: Checked by ClamAV on apache.org Stepping through the current FlexJS MXML with "my" parser, I am confidant that I can create the needed data structures using the setup that is currently in the code. If I'm somehow mistaken, we'll know soon enough. EdB On Wed, Mar 6, 2013 at 8:01 PM, Michael Schmalle wrote: > No, > > I said there is a huge curve to what you are about to try and produce with > data structures. I'm asking have you thought about how your are going to > create them... ? > > His data structures are pretty freaking abstract and you can't just loop > through the DOM and create them. > > > Mike > > Quoting Erik de Bruin : > >> Mike, >> >> Aren't we crossing streams now? My efforts are aimed at creating >> FlexJS output and my code is close to making that happen. If I >> understand your last correctly, you are suggesting a different >> approach? >> >> EdB >> >> >> >> On Wed, Mar 6, 2013 at 7:54 PM, Michael Schmalle >> wrote: >>> >>> Alex, >>> >>> Did you happen to read Gordon's comments on >>> >>> https://cwiki.apache.org/confluence/display/FLEX/MXML+Data+Spec >>> >>> At the end of Jan? >>> >>> I'm seriously thinking about giving an initial impl for FalconJx right >>> now >>> and your data structures. >>> >>> I just found the 1400 line prototype emitter/walker I made a month ago >>> dealing with this and your FragmentList. >>> >>> Since I'm all about getting this boat shoved off, I can afford a couple >>> days >>> trying to get what I started working abit. >>> >>> Mike >>> >>> >>> >>> Quoting Michael Schmalle : >>> >>>> Hmm. >>>> >>>> I understand what you are saying but that is what the walker is for >>>> because most output is never going to translate to the existing >>>> structure of >>>> what will be output as the case with FlexJS and it's data structures. In >>>> AS >>>> we have a 1 to 1 relationship with the AST to source code. >>>> >>>> I see this as duplicate work considering in MXML you are basically >>>> cherry >>>> picking what you need and creating an internal model based on the data >>>> parsed which then you will loop through and create the js class. >>>> >>>> But, that is just the way I see it. :) >>>> >>>> Mike >>>> >>>> >>>> Quoting Erik de Bruin : >>>> >>>>> Mike, >>>>> >>>>> The idea is to create the same "input == output" tests for MXML as you >>>>> did for AS, to check if the emitters are handling all input correctly. >>>>> Inheriting from those verifiably 'correct' MXML emitters I will create >>>>> JS output, both for FlexJS and VanillaSDK (initially, but others might >>>>> be added later), similar to how we do both AMD and 'goog' JS output >>>>> from extending the AS emitter class. MXML in my view is a second input >>>>> type, next to AS. >>>>> >>>>> EdB >>>>> >>>>> >>>>> >>>>> On Wed, Mar 6, 2013 at 7:30 PM, Michael Schmalle >>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> Erik, >>>>>> >>>>>> I'm just looking at some of the things you have been working on. >>>>>> >>>>>> I'm a bit confused... My understanding was the MXML emitters needed to >>>>>> produce relevant AS code of FlexJS IE Alex's data structures. >>>>>> >>>>>> Am I missing something obvious here that was discussed between you and >>>>>> Alex? >>>>>> >>>>>> When I created the base walker and emitter I never had intentions of >>>>>> producing MXML source code from the MXML AST DOM. >>>>>> >>>>>> Mike >>>>>> >>>>>> -- >>>>>> Michael Schmalle - Teoti Graphix, LLC >>>>>> http://www.teotigraphix.com >>>>>> http://blog.teotigraphix.com >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ix Multimedia Software >>>>> >>>>> Jan Luykenstraat 27 >>>>> 3521 VB Utrecht >>>>> >>>>> T. 06-51952295 >>>>> I. www.ixsoftware.nl >>>>> >>>> >>>> -- >>>> Michael Schmalle - Teoti Graphix, LLC >>>> http://www.teotigraphix.com >>>> http://blog.teotigraphix.com >>>> >>>> >>> >>> -- >>> Michael Schmalle - Teoti Graphix, LLC >>> http://www.teotigraphix.com >>> http://blog.teotigraphix.com >>> >> >> >> >> -- >> Ix Multimedia Software >> >> Jan Luykenstraat 27 >> 3521 VB Utrecht >> >> T. 06-51952295 >> I. www.ixsoftware.nl >> > > -- > Michael Schmalle - Teoti Graphix, LLC > http://www.teotigraphix.com > http://blog.teotigraphix.com > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl