You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Harbs <ha...@gmail.com> on 2017/03/05 09:38:19 UTC
Re: [FlexJS] maven faling (WeakMap)
What’s the status one this? (I did not understand the issue very well.)
I’m relying on ObjectMap in my code, and it would be nice to have it working in the official build. ;-)
> On Feb 16, 2017, at 11:41 AM, Christofer Dutz <ch...@c-ware.de> wrote:
>
> Hi Alex,
>
> My current state is that the ASDoc generation uses the DITA output to generate the general data structures (It looked as DITA was a lot more complete than the others). But in contrast to your version it does two compilations … one for JS and one for SWF. Currently
>
> What I’m currently working on is to create a tree-walker that merges the two and marks elements as “available in both”, “available only in js” and “available in swf” and to output that as XML so we can easily output HTML and easily customize the output.
>
> Chris
>
>
> Am 16.02.17, 00:03 schrieb "Alex Harui" <ah...@adobe.com>:
>
>
>
> On 2/15/17, 2:46 PM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>
>> Nope … not yet … I’ve got some uncommitted stuff in my local repo, but
>> nothing globally usable yet … still thinking about how to do things
>> nicely ☺
>
> Then that's why it works for Maven. The Ant build currently has to use
> the old Flex SDK MXMLC compiler which doesn't allow "delete" as a function
> name. Once Falcon can generate DITA and you put in place the XSLT we'll
> have the old ASDoc back.
>
> Another option is that we invest a bit more in the FlexJS ASDoc app and
> use that for ASDoc for now.
>
> Thoughts?
> -Alex
>
>
>
Re: [FlexJS] maven faling (WeakMap)
Posted by Alex Harui <ah...@adobe.com>.
How many folks actually use the FlexJS ASDoc?
Do folks have the cycles to make the ASDoc example a bit better? The dual
branch is pretty much going to force us to give up on using regular Flex
to generate our ASDoc. It might be time to just switch to the ASDoc
example until Chris or others get the DITA-to-HTML conversion working. At
least more of us know how to change MXML and AS in the example than change
the compiler or tweak the XSLT for DITA. And it would be eating our own
dog food.
Thoughts?
-Alex
On 3/5/17, 9:03 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi Harby,
>
>Well I have a skeleton using DITA to generate the swf and the js version
>of the asdoc DITA output and was starting to work on something that
>merges the two trees into one and produces xml as output.
>But I was sort of dragged into other things recently so I haven’t done
>much on this.
>
>Right now, I would have to sort of think of a format I can use to
>serialize the DITA information as xml while providing information on if
>stuff is only available only in swf or js … was thinking of something
>like our state-properties in MXML…
>
>As soon as my currently open tasks are closed and the pre-planning of the
>FlexJS summit leaves me some free time, I’ll continue on this.
>
>Chris
>
>Am 05.03.17, 10:38 schrieb "Harbs" <ha...@gmail.com>:
>
> What’s the status one this? (I did not understand the issue very
>well.)
>
> I’m relying on ObjectMap in my code, and it would be nice to have it
>working in the official build. ;-)
>
> > On Feb 16, 2017, at 11:41 AM, Christofer Dutz
><ch...@c-ware.de> wrote:
> >
> > Hi Alex,
> >
> > My current state is that the ASDoc generation uses the DITA output
>to generate the general data structures (It looked as DITA was a lot more
>complete than the others). But in contrast to your version it does two
>compilations … one for JS and one for SWF. Currently
> >
> > What I’m currently working on is to create a tree-walker that
>merges the two and marks elements as “available in both”, “available only
>in js” and “available in swf” and to output that as XML so we can easily
>output HTML and easily customize the output.
> >
> > Chris
> >
> >
> > Am 16.02.17, 00:03 schrieb "Alex Harui" <ah...@adobe.com>:
> >
> >
> >
> > On 2/15/17, 2:46 PM, "Christofer Dutz"
><ch...@c-ware.de> wrote:
> >
> >> Nope … not yet … I’ve got some uncommitted stuff in my local repo,
>but
> >> nothing globally usable yet … still thinking about how to do things
> >> nicely ☺
> >
> > Then that's why it works for Maven. The Ant build currently has
>to use
> > the old Flex SDK MXMLC compiler which doesn't allow "delete" as
>a function
> > name. Once Falcon can generate DITA and you put in place the
>XSLT we'll
> > have the old ASDoc back.
> >
> > Another option is that we invest a bit more in the FlexJS ASDoc
>app and
> > use that for ASDoc for now.
> >
> > Thoughts?
> > -Alex
> >
> >
> >
>
>
>
Re: [FlexJS] maven faling (WeakMap)
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Harby,
Well I have a skeleton using DITA to generate the swf and the js version of the asdoc DITA output and was starting to work on something that merges the two trees into one and produces xml as output.
But I was sort of dragged into other things recently so I haven’t done much on this.
Right now, I would have to sort of think of a format I can use to serialize the DITA information as xml while providing information on if stuff is only available only in swf or js … was thinking of something like our state-properties in MXML…
As soon as my currently open tasks are closed and the pre-planning of the FlexJS summit leaves me some free time, I’ll continue on this.
Chris
Am 05.03.17, 10:38 schrieb "Harbs" <ha...@gmail.com>:
What’s the status one this? (I did not understand the issue very well.)
I’m relying on ObjectMap in my code, and it would be nice to have it working in the official build. ;-)
> On Feb 16, 2017, at 11:41 AM, Christofer Dutz <ch...@c-ware.de> wrote:
>
> Hi Alex,
>
> My current state is that the ASDoc generation uses the DITA output to generate the general data structures (It looked as DITA was a lot more complete than the others). But in contrast to your version it does two compilations … one for JS and one for SWF. Currently
>
> What I’m currently working on is to create a tree-walker that merges the two and marks elements as “available in both”, “available only in js” and “available in swf” and to output that as XML so we can easily output HTML and easily customize the output.
>
> Chris
>
>
> Am 16.02.17, 00:03 schrieb "Alex Harui" <ah...@adobe.com>:
>
>
>
> On 2/15/17, 2:46 PM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>
>> Nope … not yet … I’ve got some uncommitted stuff in my local repo, but
>> nothing globally usable yet … still thinking about how to do things
>> nicely ☺
>
> Then that's why it works for Maven. The Ant build currently has to use
> the old Flex SDK MXMLC compiler which doesn't allow "delete" as a function
> name. Once Falcon can generate DITA and you put in place the XSLT we'll
> have the old ASDoc back.
>
> Another option is that we invest a bit more in the FlexJS ASDoc app and
> use that for ASDoc for now.
>
> Thoughts?
> -Alex
>
>
>