Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 37DB2D767 for ; Tue, 23 Oct 2012 08:22:00 +0000 (UTC) Received: (qmail 43175 invoked by uid 500); 23 Oct 2012 08:21:59 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 43141 invoked by uid 500); 23 Oct 2012 08:21:59 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 43113 invoked by uid 99); 23 Oct 2012 08:21:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2012 08:21:58 +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 (athena.apache.org: domain of jbalsas@gmail.com designates 74.125.82.43 as permitted sender) Received: from [74.125.82.43] (HELO mail-wg0-f43.google.com) (74.125.82.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Oct 2012 08:21:54 +0000 Received: by mail-wg0-f43.google.com with SMTP id dq11so2433982wgb.0 for ; Tue, 23 Oct 2012 01:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OWN4wIWQ5psIBTx+AU8y0Ad59ZqD7BhevCyAHp5vJ3c=; b=Gj+k3pxRT5YbOzZmiWvzPiHwl8lCDxEX8Vk9Ei7tDNJHrC6yLIdKHVgo+2KSonC0w5 TE/J6EpJwN8vkpUkxXFIcZmxW2L6SDK3CIbmRnoJkyhn10hmKdZI67g7u0pNQ6qXZ+he rjnJ/63Ns+XzyMQukvb4PBolU0Bb8C8gSlyAvV967mM7rIlVZvSO7KjeQHUAtOKImVO5 GL9/zqrdLtt3ltYEpDvUmckyEmWp/shdMR/qcQlTLdj6CaU1iVcK/+pkv8OJjZM06Qmo 4lreKhGoF7ZSJCkyPb9ie1er/VqAsKBq2kjwxow5wtk6gPP8Q7UuBn4jMKsPzax2ZBFW nOiQ== MIME-Version: 1.0 Received: by 10.180.91.71 with SMTP id cc7mr27199865wib.2.1350980492325; Tue, 23 Oct 2012 01:21:32 -0700 (PDT) Received: by 10.194.95.198 with HTTP; Tue, 23 Oct 2012 01:21:32 -0700 (PDT) In-Reply-To: References: <149F8129B58B2D418508E63117D9C5419B5AEB2A81@nambx05.corp.adobe.com> <20121018182503.155250488ldctf3z@www.teotigraphix.com> <149F8129B58B2D418508E63117D9C5419B5AEB2A9D@nambx05.corp.adobe.com> <20121018184907.15754xvkf0ivzn8j@www.teotigraphix.com> <149F8129B58B2D418508E63117D9C5419B5AEB2AD0@nambx05.corp.adobe.com> <20121018192504.32414d3p9d77uj80@www.teotigraphix.com> <20121019151853.12172akqveozbfrx@www.teotigraphix.com> <149F8129B58B2D418508E63117D9C5419B5AEB2F8E@nambx05.corp.adobe.com> <20121022163134.98536finv3io7j8m@www.teotigraphix.com> <149F8129B58B2D418508E63117D9C5419B5AFAE2DF@nambx05.corp.adobe.com> <20121022165401.20322izbqxsydyll@www.teotigraphix.com> Date: Tue, 23 Oct 2012 10:21:32 +0200 Message-ID: Subject: Re: compc config adjustements (was RE: ASC 2.0 and Falcon) From: Chema Balsas To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d04374a0757f47504ccb5a832 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04374a0757f47504ccb5a832 Content-Type: text/plain; charset=ISO-8859-1 I've created subtasks in the jira ticket for the four projects that Gordon asked to prioritize for now. This way we can avoid stepping on each other toes ;) I don't seem able to assign subtasks to myself, however. Also, that produced a lot of noise (sorry about that)... is there a better workflow to do this? We should fill the rest of subtasks to get a clear picture of what's done and what remains. 2012/10/23 Chema Balsas > Hi Mike, how are you going with those mustella tests? If you're looking at > https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview I'd > say that for now you just need to read the "Installation" and "Using > Mustella" sections. Let me know if I can help you with anything. > > I've just submited a patch for the compile target of mx at > https://issues.apache.org/jira/browse/FLEX-33226. Maybe we can use it as > a template if it's what Gordon needs from us. > > @Gordon Please, can you check if this is what you're looking for? I assume > once we get one right everything will go much faster. Also, running the > mustella tests is quite hard on my computer so for now I only verified it > passed the "mx/utils/ColorUtil" tests. If this is indeed the way to go, > I'll check if everything works as expected before sending a definitive > patch. > > > 2012/10/22 Michael Schmalle > >> I haven't yet run those(or know how) and when I was reading to docs, it >> was a bit over my head at the time. So I'm going to have to figure the >> tests out before I am going to commit anything like I said previously. >> >> Is there anyone that knows those test to write a child wiki page that >> would explain exactly what a committer needs to know at the minimum to >> check in. >> >> There is a lot of information on that one page. >> >> >> Mike >> >> >> Quoting Gordon Smith : >> >> I think you'd also want to run the Mustella tests. I don't think there >>> is an Ant target for those. >>> >>> - Gordon >>> >>> -----Original Message----- >>> From: Michael Schmalle [mailto:apache@teotigraphix.**com >>> ] >>> Sent: Monday, October 22, 2012 1:32 PM >>> To: flex-dev@incubator.apache.org >>> Subject: RE: compc config adjustements (was RE: ASC 2.0 and Falcon) >>> >>> Ok, >>> >>> So I'm guessing that running the build is the correct way to test if >>> anything is broken correct? I'm kind of new to this larger scale >>> development and don't want to mess anything up. >>> >>> (before I commit to the develop branch) >>> >>> Mike >>> >>> Quoting Gordon Smith : >>> >>> Please prioritize the conversion of >>>> >>>> frameworks/projects/framework >>>> frameworks/projects/rpc >>>> frameworks/projects/mx >>>> frameworks/projects/spark >>>> >>>> Those four will be a good start. >>>> >>>> - Gordon >>>> >>>> -----Original Message----- >>>> From: Michael Schmalle [mailto:apache@teotigraphix.**com >>>> ] >>>> Sent: Friday, October 19, 2012 12:19 PM >>>> To: flex-dev@incubator.apache.org >>>> Subject: Re: compc config adjustements (was RE: ASC 2.0 and Falcon) >>>> >>>> I did manage to do a prototype conversion this morning of the >>>> frameworks compile target. >>>> >>>> There are a couple things I am uncertain about, >>>> >>>> -| resource-bundle-list="${**basedir}/bundles.properties" >>>> -| >>>> -| output="${FLEX_HOME}/**frameworks/libs/framework.swc" >>>> >>>> Tokens in flex-config are just {token} right or the dollar sign >>>> ${token}? It's been awhile for me as well. And I was more with >>>> component dev than setting up component builds with flex-config. >>>> >>>> Other than the listed things above, it seems pretty straight forward >>>> with the tags. If you want to create a list, you can or I will next >>>> week and we could work it together and then I can commit when it all >>>> looks good and still compiles the SWCs. :) >>>> >>>> >>>> Mike >>>> >>>> >>>> Quoting Chema Balsas : >>>> >>>> Hi Mike, >>>>> >>>>> I've dealt with the differences between compc and config files >>>>> several times in my day to day work... now I wish I'd written them >>>>> down... :D >>>>> >>>>> I think I could find some time to try and help with this. Have you >>>>> already identified which builds need to be updated? We could compile >>>>> a list of them, then start from different ends and try to meet >>>>> somewhere halfway... >>>>> >>>>> @Gordon I don't know if this is a silly question, but is there a >>>>> reliable way of telling if the resulting swc is exactly the same as >>>>> the old one? >>>>> Should something like size or md5 maintained so we could check for >>>>> that? >>>>> >>>>> Cheers, >>>>> Chema >>>>> >>>>> 2012/10/19 Michael Schmalle >>>>> >>>>> Ok Gordon, >>>>>> >>>>>> I think I understand what you are saying, you want include files >>>>>> that completely configure the target without the compc task so it >>>>>> can be loaded from other clients. >>>>>> >>>>>> This is to be commited when changed in the develop branch. >>>>>> >>>>>> I will ask more questions if needed tomorrow as it sounds like that >>>>>> is your Apache work day. >>>>>> >>>>>> Thanks for all your answers today it has been appreciated. >>>>>> >>>>>> Mike >>>>>> >>>>>> >>>>>> Quoting Gordon Smith : >>>>>> >>>>>> Could you quickly elaborate on the "convert the tags" part >>>>>> for me? >>>>>> >>>>>>> >>>>>>>> >>>>>>> Each project in sdk/trunk/frameworks/projects builds a SWC. For >>>>>>> example, look at the build.xml file inside >>>>>>> sdk/trunk/frameworks/projects/****framework, >>>>>>> which builds framework.swc. Its "compile" target has the >>>>>>> task >>>>>>> >>>>>>> >>>>>> output="${FLEX_HOME}/** >>>>>>> frameworks/libs/framework.swc" >>>>>>> resource-bundle-list="${** >>>>>>> basedir}/bundles.properties"> >>>>>>> >>>>>>> 11.1 >>>>>>> >>>>>> uri="library://ns.adobe.com/****flex/mx >>>>>>> >" >>>>>>> manifest="${basedir}/manifest.****xml"/> >>>>>>> >>>>>> uri="http://www.adobe.com/****2006/mxml >>>>>>> >" >>>>>>> manifest="${basedir}/manifest.****xml"/> >>>>>>> >>>>>> uri="library://ns.adobe.com/* *flex/mx >>>>>>> "**/> >>>>>>> >>>>>>> ****FrameworkClasses>>>>>> classes> >>>>>>> >>>>>> ***> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> **> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> path="${basedir}/defaults.css"****/> >>>>>>> >>>>>> path="${basedir}/defaults-3.0.****0.css"/> >>>>>>> >>>>>> path="${basedir}/assets/****Assets.swf"/> >>>>>>> >>>>>> path="${basedir}/assets/****CalendarIcon.png"/> >>>>>>> >>>>>>> true >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> I want it to look instead like >>>>>>> >>>>>>> >>>>>>> >>>>>>> where you write the framework-config.xml file using the syntax in >>>>>>> files like flex-config.xml. >>>>>>> >>>>>>> The difficulty is that the syntax for the XML you put inside the >>>>>>> framework-config.xml file is different in various ways from the XML >>>>>>> tags inside the tag (for one thing, XML config files don't >>>>>>> use >>>>>>> attributes) so the conversion isn't always obvious. >>>>>>> >>>>>>> I want the "compile" target for every project in the projects >>>>>>> directory to use a config file for its compilation options. >>>>>>> >>>>>>> Then you or I can write JUnit tests that use Falcon to compile each >>>>>>> SWC by invoking Falcon with this config file. >>>>>>> >>>>>>> - Gordon >>>>>>> >>>>>>> >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Michael Schmalle >>>>>>> [mailto:apache@teotigraphix.****com >>>>>>> ] >>>>>>> Sent: Thursday, October 18, 2012 3:49 PM >>>>>>> To: flex-dev@incubator.apache.org >>>>>>> Subject: RE: ASC 2.0 and Falcon >>>>>>> >>>>>>> Quoting Gordon Smith : >>>>>>> >>>>>>> Gordon I can help with MXML once I get my feet wet in >>>>>>> understanding >>>>>>> >>>>>>>> exactly "What" needs to be implemented. >>>>>>>>> >>>>>>>>> >>>>>>>> Tomorrow I'll be working on eliminating the falcon/sdk directory, >>>>>>>> since this violates Apache rules. >>>>>>>> >>>>>>>> Next week I'll check in the first few MXML parser tests for simple >>>>>>>> tags like and . At that point the pattern to follow >>>>>>>> for MXML parser tests will be clear. >>>>>>>> >>>>>>>> >>>>>>>> I can help with further tests after this. >>>>>>> >>>>>>> >>>>>>> - Gordon >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Ok, I understand and replied in my previous email that I realize >>>>>>> MXML is >>>>>>> #1 priority. I will be working on this sooner than later as I see >>>>>>> what you do. >>>>>>> >>>>>>> >>>>>>> In the meantime, you could learn XML config file syntax and >>>>>>> convert >>>>>>> >>>>>>>> the tags. >>>>>>>> >>>>>>>> >>>>>>> I experimented with the config when I was porting my asdoc program >>>>>>> that extended mxmlc. >>>>>>> >>>>>>> Could you quickly elaborate on the "convert the tags" part >>>>>>> for me? >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -----Original Message----- >>>>>>>> From: Michael Schmalle >>>>>>>> [mailto:apache@teotigraphix.****com >>>>>>>> ] >>>>>>>> Sent: Thursday, October 18, 2012 3:25 PM >>>>>>>> To: flex-dev@incubator.apache.org >>>>>>>> Subject: RE: ASC 2.0 and Falcon >>>>>>>> >>>>>>>> So in essence you are saying; >>>>>>>> >>>>>>>> 1. Gordon needs help implementing MXML. >>>>>>>> 2. Flex is incompatible with the new VM that is stage3D based and >>>>>>>> a new architecture for components needs to be created based on >>>>>>>> Stage3D. >>>>>>>> 3. The ASC compiler of Falcon is going to need to be implemented >>>>>>>> to produce bytecode that is compatible with the new AVM. >>>>>>>> >>>>>>>> >>>>>>>> Correct? >>>>>>>> >>>>>>>> >>>>>>>> Gordon I can help with MXML once I get my feet wet in >>>>>>>> understanding exactly "What" needs to be implemented. >>>>>>>> >>>>>>>> >>>>>>>> Mike >>>>>>>> >>>>>>>> Quoting Gordon Smith : >>>>>>>> >>>>>>>> Furthermore, the new runtime uses new bytecode that the Falcon >>>>>>>> >>>>>>>>> compiler does not produce, and the new compiler that does produce >>>>>>>>> it doesn't compile MXML. >>>>>>>>> >>>>>>>>> - Gordon >>>>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: Thibault Imbert [mailto:timbert@adobe.com] >>>>>>>>> Sent: Thursday, October 18, 2012 3:16 PM >>>>>>>>> To: flex-dev@incubator.apache.org >>>>>>>>> Subject: Re: ASC 2.0 and Falcon >>>>>>>>> >>>>>>>>> Hi Om, >>>>>>>>> >>>>>>>>> The rendering architecture of the new runtime is Stage3D only. So >>>>>>>>> essentially, there is not "native" DisplayObject. >>>>>>>>> So your framework needs to leverage Stage3D, just like iOS is >>>>>>>>> leveraging OpenGL for their components UI. >>>>>>>>> >>>>>>>>> That's why we have been funding Starling to help people >>>>>>>>> transition to a full Stage3D model. Recently, the community has >>>>>>>>> created a drawing API extension for Starling: >>>>>>>>> http://www.bytearray.org/?p=****4832 >>>>>>>>> >>>>>>>>> 3 >>>>>>>>> 2>and >>>>>>>>> a few >>>>>>>>> weeks back a skeleton bones extension was also created to create >>>>>>>>> complex animations on top of Starling: >>>>>>>>> https://github.com/****DragonBones/****SkeletonAnimationFramework >>>>>>>>> >>>>>>>>> >. >>>>>>>>> All of that >>>>>>>>> is open source, you can fork it, create extensions, etc. >>>>>>>>> >>>>>>>>> Feathers is the right model and approach, lightweight UI >>>>>>>>> framework on top of Starling (which does all the Stage3D work >>>>>>>>> behind the scenes). >>>>>>>>> >>>>>>>>> Keep in mind Feathers "vision" is not to replace Flex, it is a >>>>>>>>> lightweight UI framework for Uis in games, developed by a Flex >>>>>>>>> developer who wanted to have some of the power of Flex (skinning, >>>>>>>>> productivity) without reproducing the same mistakes as Flex (lots >>>>>>>>> of dependencies and display list based). >>>>>>>>> >>>>>>>>> Thibault Imbert | sr. product manager gaming (Graphics, Language, >>>>>>>>> VM, >>>>>>>>> Compiler) | Monocle | adobe systems gaming.adobe.com >>>>>>>>> | bytearray.org >>>>>>>>> >>>>>>>>> | @thibault_imbert >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 10/18/12 3:01 PM, "Om" wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> Just a heads up, given the architecture changes of the next-gen >>>>>>>>>>> runtime, Flex will not be able to run in it. I would "highly" >>>>>>>>>>> recommend you guys having a look at Feathers (work from Josh >>>>>>>>>>> Tynjala >>>>>>>>>>> - feathersui.com) on top of Starling, which will run >>>>>>>>>>> beautifully in our next runtime. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Could you please give us some technical details as to why Flex >>>>>>>>>> wont be able to run in the new runtime? This would help us >>>>>>>>>> figure out what we can/need to do given where we are currently. >>>>>>>>>> >>>>>>>>>> Of course, any other information you can provide to help us move >>>>>>>>>> Flex towards Stage3D/Starling would be beneficial. >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Om >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Oct 18, 2012 at 2:55 PM, Michael Schmalle >>>>>>>>>> ****wrote: >>>>>>>>>> >>>>>>>>>> Quoting Thibault Imbert : >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Hi Mike, >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> This is true, but ASC is already moving to ASNext targeting >>>>>>>>>>>> the next generation runtime which is targeting game >>>>>>>>>>>> developers. So our resources are assigned to that and the >>>>>>>>>>>> time we have to take ASC >>>>>>>>>>>> 2.0 changes to Falcon, are limited. Gordon will bring >>>>>>>>>>>> key/showstopper bugs fixed in ASC >>>>>>>>>>>> 2.0 to Falcon, we cannot commit to anything more. >>>>>>>>>>>> >>>>>>>>>>>> Just a heads up, given the architecture changes of the >>>>>>>>>>>> next-gen runtime, Flex will not be able to run in it. I would >>>>>>>>>>>> "highly" >>>>>>>>>>>> recommend you guys having a look at Feathers (work from Josh >>>>>>>>>>>> Tynjala >>>>>>>>>>>> - feathersui.com) on top of Starling, which will run >>>>>>>>>>>> beautifully in our next runtime. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> I have just started working with Josh and this component >>>>>>>>>>> architecture, it is very nice. I spoke of feathers earlier >>>>>>>>>>> today and was talking with Josh about MXML support. >>>>>>>>>>> >>>>>>>>>>> So your saying there needs to be a component framework >>>>>>>>>>> developed that will run in the new architecture to be cross >>>>>>>>>>> compatible? I don't quite understand what you are saying. >>>>>>>>>>> >>>>>>>>>>> Mike >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Some videos: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> https://vimeo.com/51010861 >>>>>>>>>>>> >>>>>>>>>>>> http://www.youtube.com/watch?******v=DGRy7H17MkA&feature=** >>>>>>>>>>>> youtu.* >>>>>>>>>>>> * >>>>>>>>>>>> * >>>>>>>>>>>> *be&hd=>>>>>>>>>>> feature=y >>>>>>>>>>>> o >>>>>>>>>>>> utu.**be&hd=> >>>>>>>>>>>> 1< htt >>>>>>>>>>>> p://www.youtube.com/watch?v=****DGRy7H17MkA&feature=youtu.be&** >>>>>>>>>>>> **h >>>>>>>>>>>> d >>>>>>>>>>>> =1>>>>>>>>>>> youtu.be >>>>>>>>>>>> & >>>>>>>>>>>> hd=1> >>>>>>>>>>>> > >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thibault Imbert | sr. product manager gaming (Graphics, >>>>>>>>>>>> Language, VM, >>>>>>>>>>>> Compiler) | Monocle | adobe systems gaming.adobe.com >>>>>>>>>>>> | bytearray.org >>>>>>>>>>>> >>>>>>>>>>>> | @thibault_imbert >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 10/18/12 11:36 AM, "labriola@digitalprimates.net" >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> We have no plans keeping ASC 2.0 (and above) in sync with >>>>>>>>>>>> Falcon, as I >>>>>>>>>>>> >>>>>>>>>>>> said previously, today the compilers are different projects >>>>>>>>>>>>> and >>>>>>>>>>>>> >>>>>>>>>>>>>> targeting two different audiences. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Yeh, we totally get why parsing the AS language and >>>>>>>>>>>>> generating bytecode will be very different for the game >>>>>>>>>>>>> market. I can't imagine the amount of time you guys are >>>>>>>>>>>>> spending on the differences in for loops alone.... >>>>>>>>>>>>> >>>>>>>>>>>>> Mike >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> Chema >>>>> >>>>> >>>> -- >>>> 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 >>> >>> >>> >> -- >> Michael Schmalle - Teoti Graphix, LLC >> http://www.teotigraphix.com >> http://blog.teotigraphix.com >> >> > > > -- > Chema > -- Chema --f46d04374a0757f47504ccb5a832--