#Doitnow swc how to
#Doitnow swc pdf
#Doitnow swc zip file
#Doitnow swc code
#Doitnow swc free

Aliquam vel velit vel mi adipiscing semper in ac orci. Donec lobortis magna vel nibh mollis tempor. Suspendisse placerat nibh in libero tincidunt a elementum mi vehicula. Cras elementum luctus mauris, vitae eleifend diam accumsan ut. Mauris ultrices dapibus lacus non ultrices. Donec ut nisl metus, sit amet viverra turpis. Praesent tellus libero, lacinia ac egestas eget, interdum quis purus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Phasellus convallis, tortor a venenatis mattis, erat mi euismod tellus, in fermentum sapien nibh sit amet urna. Pdf.writeText(12, 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent vel lectus lorem. Pdf.addText('This is a sample text', 5, 15) Var m圜oreFont: IFont = new CoreFont(FontFamily.HELVETICA) pdf.setFont(FontFamily.ARIAL, Style.NORMAL, 12) The following line turned out not to work as the API had changed since the original example was posted Var newPage: Page = new Page(Orientation.PORTRAIT, Unit.MM, Size.A4) Pdf.setDisplayMode(Display.FULL_PAGE, Layout.SINGLE_PAGE)

#Doitnow swc pdf

Var pdf: PDF = new PDF(Orientation.PORTRAIT, Unit.MM, Size.A4) Removed the image to simplify the testing

#Doitnow swc code

You need to extend the Flex class Sprite for AIR to be able to run the code What I did was to take the AS code from this example and converted it into the following package. I include this info here to help explain the process.

#Doitnow swc how to

So, the easiest way I found to do this (before I found out how to use Eclipse) is as follows. The AS class library is in a SWC file (ie is compiled) and the Flex / AS compiler imports the classes that you need from that file. The basic method is that you create a new AS package that imports the classes that you need from the library. However I was unable to get any help to work out what, if anything, I was doing wrong. It is highly likely that my problems with purePDF we of my own making. However, as discussed in my forum post here, I was unable to get purePDF to work so I switched to AlivePDF which was more successful. The latter interested me particularly because it is a port of iText java library which I was already familiar with. I found two AS libraries that create PDF files client-side – AlivePDF and purePDF. Before I discuss the command line compiler settings, I need to digress into talking about the libraries I found. What I wanted to do was to use an existing library and extend it. Ray’s example assumes you are creating an AS package from scratch. Both of these compilers are in the Flex SDK /bin folder. A simpler way is to use the amxmlc command line compiler instead which outputs directly to the SWF file.

#Doitnow swc zip file

As Ray says, the Adobe docs suggest using the acompc command line compiler, which outputs a SWC / Zip file that you can extract the SWF from. There are 2 ways to compile your SWF file. The AS library you need in your AIR app is contained in a SWF file as you can see in Ray’s post. Unzip it somewhere (in my case D:lex_sdk_4.1). Until I started this process I had never really looked at ActionScript so the following is very much from the perspective of a newbie! Basic AS infoįirst, read Ray’s post as a starting point.ĭownload the Flex 4 SDK from here. There are lots of other AS libraries out there that can be used using the techniques discussed in this post.You can set up Eclipse to do that (ie you dont need FlexBuilder or be restricted to command line compiling).

#Doitnow swc free

You can use the free Flex SDK to develop the SWF file you need to invoke the required ActionScript classes.

A “proof of concept” is at the end of this post.

It is possible to create PDF files completely client-side from Javascript AIR apps via ActionsScript.

This post covers what I found along the way. Knowing that it was possible to invoke ActionScript classes from HTML/Javascript AIR apps, eg this post by Ray Camden and using that post as a start, I began exploring the possibilities. It seemed to me that a way around the lack of printing support would be to have the ability to create PDF files client-side, as opposed to sending all the data to be printed to the server then getting a PDF back again. As has been blogged in many places, printing from AIR is very limited and problematic.