On Thu, Sep 13, 2012 at 12:42 PM, Alex Harui <aha...@adobe.com> wrote:
> > On 9/13/12 12:27 PM, "Om" <bigosma...@gmail.com> wrote: > > > >> > > I believe that making an AIR app for this would cause problems with > > continuous integration or build bots. XSLT can be invoked via ant and > can > > be run anywhere. > I've used AIR apps in shell scripts. I haven't tried it in Ant, but I > don't > know why it wouldn't work. I'd be ok with writing an ASDoc generator in > Java as well. > That would tie the ASDoc generator to Windows and Macs. I dont think Falcon has (yet) this restriction. I would rather that we dont add this requirement now. Unless we can restrict the generator to use just AIR 2 features. > > > Moreover, I am not sure if we do, but if we are handling large amounts > of > > text/strings, we should probably avoid AIR. > Is XSLT that much faster? IIRC, the ASDoc build takes a while. > > > I am not sure how fast XSLT is, but string manipulation sucks up a lot of memory in AIR/Flash Player. Which in turns drags down performance. > > I am sure this community has folks who can handle XSLT? > I'm sure it does, and I'm sure I could eventually figure it out, but it > would allow for wider participation. > > > I agree. It makes sense to do it in a language that most people are familiar with here. But my above points about AIR still holds good. > > Thanks, > > Om > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
