Hi, On Tue, Mar 29, 2011 at 9:24 AM, Leonard Rosenthol <[email protected]> wrote: > Why to LinkActions when they can be to ANY type of action? > Maybe I missunderstood the poppler core, but it seems to me that LinkAction is the the base clase for any action in poppler core, that's why I use LinkAction.
> And are you creating a new JavaScriptAction class to handle the details of JS > processing?? > There is already a LinkActionJavascript action which stores the javascript of the action as a GooString, so we need to use that (see my other patch, were I add the glib wrapper for this). More precisely, details of JS processing will be dealt by bindings (and/or viewers), not by poppler core, but according to the my understanding of the PDF spec. Exposing these additional Actions makes sense even for viewer that don't want to support javascript. Greetings José > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf > Of [email protected] > Sent: Tuesday, March 29, 2011 1:35 AM > To: [email protected] > Subject: [poppler] [Patch] Parse Additional Actions for Widget Annots. > > Hi, > > Here is a patch to parse the additional actions dict that is present in > Widget Annots. This is one of the first patches we will need to get > javascript support as many of the javascript in the pdfs are encoded in > JavascriptActions that are associated to the AditionalActions dictionary. All > comments welcome, specially about the way I am saving the AditionalActions as > an Array of Pointers to LinkActions. > > > Greetings, > > > José > _______________________________________________ poppler mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/poppler
