On Fri, Mar 22, 2013 at 12:36 AM, Erik de Bruin <e...@ixsoftware.nl> wrote:

> I think both the FlexJS as well as VanillaSDK frameworks can benefit
> from this. So it should be available to both. I don't know much about
> XSLT, but if it 'converts one into another', I think it should
> ultimately go with that other thing that 'converts one into another',
> FalconJx.
>
>
Makes sense.  Obviously you will have a better idea where to plug it in
after seeing my code.


> But for now, as it is a work in progress, I think it's best place is
> in ASJS, in the root, next to my 'publisher'. The publisher was also a
> proof of concept, that has since been integrated into FalconJx.
>
> Clear as mud, right?
>
>
I am guessing that you just said "flex-asjs (develop)/fxg2svg/" is good for
now? ;-)


> EdB
>
>
>
> On Fri, Mar 22, 2013 at 8:29 AM, Om <bigosma...@gmail.com> wrote:
> > On Thu, Mar 21, 2013 at 2:21 PM, Alex Harui <aha...@adobe.com> wrote:
> >
> >>
> >>
> >>
> >> On 3/21/13 2:17 PM, "Om" <bigosma...@gmail.com> wrote:
> >>
> >> > As promised, I am getting closer to share my basic FXG to SVG
> >> > transformation stylesheet.  I propose the location:
> >> >
> >> > flex-asjs (develop)/fxg2svg/
> >> >
> >> > Anyone hates this proposal?  If not, I will check my code in soon
> with a
> >> > couple of very basic examples.
> >> >
> >> Doesn't matter at this early stage.  But what is it?  XLST?  How does it
> >> get
> >> into the workflow?
> >>
> >>
> > For now it is just an XSLT file.  This converts a given spark skin (fxg)
> >  into a valid SVG document with inline CSS.  I was hoping you or Erik
> will
> > help me figure out how this would go into the workflow :-)  I am not too
> > familiar with you folks' current work.  I will go through that workflow
> > when I get a chance.
> >
> > My current goal is to try and have a basic spark skin class converted to
> > SVG/CSS to validate this approach.
> >
> > Thanks,
> > Om
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Reply via email to