Allow Browser invocation of Air application

Hello Friends
                       Can Anybody guide me how to implement Allow browser invocation Feature in my Air pplication.i mean To say
application can be launched when the user clicks a link in a web browser.
Please tell me After Change<allowBrowserInvocation></allowBrowserInvocation> tag setting to true in application Descriptor  xml.what to do next?
Thanks And Regards
    Vineet Osho

hello Guys please give
me any idea for this browser invocation so that i impelment that  feature.i am completely confused.please help me out.
waiting for your response.
Thanks and Regards
    Vineet Osho

Similar Messages

  • Communication problem between air application from swf at browser

    Hi,
    I am trying to communicate adobe air native application from brwser using swf, I check for native application installed or not. If installed then launch and if not then install and launch.
    I am facing problem when browser crashes and communication get lost with adobe air native application. And when user restart web browser and try to make local connection for communication with native application, some times it get failed. so, how to handle this state please help.
    Thanks
    Nitesh Kumar

    Hi sinious,
    How could I clean up connection when browser is aborted or lost?
    below you can find the code snippet to check for air application and connection
    airSWFLoader = new Loader();
                                  loaderContext = new LoaderContext();
                                  loaderContext.applicationDomain = ApplicationDomain.currentDomain;
                                  airSWFLoader.contentLoaderInfo.addEventListener(Event.INIT, onInit);
                                  airSWFLoader.load(new URLRequest("http://airdownload.adobe.com/air/browserapi/air.swf"),loaderContext);
    function onInit(e:Event):void 
                                  airSWF = e.target.content; 
                                  switch(airSWF.getStatus().toString())
                                            case "available" : AirLoaderStatus = 1;
                                            break;
                                            case "unavailable" : AirLoaderStatus = 2;
                                            break;
                                            case "installed" : AirLoaderStatus = 3;
                                            break;
    private function getAppStatus():void
                                  clearInterval(intervalIdentifier);
                                  if(AirLoaderStatus == 0){intervalIdentifier = setInterval(getAppStatus,1000);return;}
                                  m_launchInstallBtn.visible = true;
                                  var statusInfo:String = airSWF.getStatus();
                                  airSWF.getApplicationVersion(m_installerFileName, m_pubID, versionDetectCallback);
    function versionDetectCallback(version:String):void
                                  if (version == null)
                                            trace("Not Installed");
                                            // Take appropriate actions. For instance, present the user with
                                            // an option to install the application.
                                  else
                                            m_isPluginsInstalled = true;
                                            // Take appropriate actions. For instance, enable the
                                            // user interface to launch the application.
    private function onlickMouse(event:MouseEvent):void
                                  m_text.text += "\nm_isPluginsInstalled:"+m_isPluginsInstalled+":::AirLoaderStatus:"+AirLoaderStatus;
                                  trace("\nm_isPluginsInstalled:"+m_isPluginsInstalled+":::AirLoaderStatus:" +AirLoaderStatus);
                                  switch(event.currentTarget)
                                            case m_launchInstallBtn:
                                                         if(AirLoaderStatus == 1)
           installAirsetup();
                                                      else
                                                                if(!m_isPluginsInstalled)
                                                                          airSWF.installApplication(m_url, m_runtimeVersion, m_argsToPass);
                                                                          airSWF.launchApplication(m_installerFileName, m_pubID, m_argsToPass);
                                                                else
                                                                          airSWF.launchApplication(m_installerFileName, m_pubID, m_argsToPass);
                                            break;
    in the above code snippet I pass localConnection for send and recieve as an argument in m_argsToPass.
    the connection names strarts with "_".
    In the air application I I split the event arguments like given below
    argsArray = event.arguments.toString().split(",");
    and then try to establish connection.
    Please suggest, how could I clean the connection on lost/ abort of browser, since then swf object embeded in browser also get lost.

  • Terminate air application from browser . Help !

    I have managed to call AIR application from flex application using
    airSWF.launchApplication(appID, pubID, arguments);
    How can i stop the AIR application from the flex application running in browser. Any help would be helpful.

    Did you try ...
    location.href = url

  • Launch air application from browser like adobe connect pro

    I will like to install and launch my adobe air application from the browser, just like adobe connect pro does. Any help on this?

    Did you try ...
    location.href = url

  • AIR browser invocation install

    Hello, guys and gals. I have a situation here.. In which is hard to define what went wrong.
    My goal is to build an AIR application (let's call that myApp) and assistence .SWF (AIRBadge) file allowing to install/invoke myApp.
    So far I succeeded on calling getStatus from the AIRBadge, returning "installed". I got AIR 2.6.
    The problem is that when I call methods: installApplication() or launchApplication() an ADOBEA~1.exe launches, but that's all that happends. No JavaScript error, no ActionScript error.
    The only clue that I found was the log file that AIRInstaller does. The last lines there says:
    [<date>:<time>] Application Installer begin with version 2.6.0.19120 on Windows XP x86
    [<date>:<time>] Commandline is: -playerVersion=10,1,53,64 -sandboxType=remote -securityDomain=localhost -https=false -fromUserEvent=false -- -url PStore.air -- alabala purtukala mandrahulka
    [<date>:<time>] Installed runtime (2.6.0.19120) located at c:\Program Files\Common Files\Adobe AIR
    [<date>:<time>] Application Installer end with exit code 2

    I found the problem: the function stack should begin from a mouse click within the flash. Also the URL of the AIR file when calling installApplication method, should be the full URL to work correctly.

  • Can HTML based browsers rotate along with a Desktop AIR application if browser is modular?

    I get a buged out browser module in my Desktop AIR application after doing an application level rotation/orientation-change/flip screen for viewing on other side of monitor .
    Most of the HTML content rotates 180 degrees without any issue, but, it seems some of the "components" aren't getting with the program.
    Dropdown box lists don't rotate, even though the button to initate use of the dropdown list does. So, when viewing the application from the new orientation,
    the dropdown lists are upside down from an end user perspective ( just never rotated properly from a developer perspective )
    I was having to flip my application by sending out a message to a service and recieving the call from a WCF to tell the whole OS to flip via WIN32 API but
    64bit operating systems do this a lot slower, so i'm trying to find a new solution.
    I am wondering if a workaround can be done by replacing the misbehaving things like the dropdown box with native flex components?
    Any thoughts/ideas/conclusions?

    Did you try ...
    location.href = url

  • Deployment of an Adobe AIR application in an enterprise environment

    Dear Team members,
    first of all my apologies for posting this thread in more than one forum (see Installations Issues) but the argument is very important to us and I don't know where discuss it.
    I would like to post a question to you regarding deployment doubts that we are trying to address.
    My company is working on the new version of our primary application previously built as a J2EE application with some reporting functions with Flex, and we want to use AIR in order to leverage its possibilities:
    Seamless integration with existing application functionalities (implemented as standard JEE web application pages) thanks to the integrated HTML capabilities
    Improved integration of the user interface with the desktop
    Native processes to provide additional functionalities
    Our application is targeted to pharmaceutical industry, subject to FDA regulations, and it affects more than 5000 users for each customer, so we have some specific requirements affecting the deployment and distribution of the software:
    Allow to run multiple versions of the software on the same client machine (to support test and acceptance activities in addition to the production environment)
    Minimize the effort of the initial setup on each client
    Manage the version upgrades without manual activities on each client
    Keep the test/acceptance and production environments strictly aligned to improve effectiveness of formal validation (ideally, an application once validated should be transported in production without any source code modification, recompilation or repackaging)
    The current browser-based strategy is perfectly fit to these requirements, and in the shift towards a desktop-based strategy we need to continue satisfying them as much as possible. We evaluated the standard distribution strategy of Adobe AIR applications, and noticed several attention points in this scenario.
    The first issue we encountered is the back-end services endpoint discovery problem. Simply hardcoding a server URL in the packaged application could be a viable solution for public internet-accessible applications, but we need to support multiple customers in their intranet, and each one typically requires multiple environments for the application (acceptance, production, etc.). Maintaining dozens of different packages of the AIR application to support all these customer environments clearly is not the solution. Neither we want to force thousands of different users to enter and maintain the correct server location in their local preferences.
    So, we thought to use a badge hosted in the back-end application to run the local AIR application: using the underlying API, we could activate the application specifying also the network location of the back-end services. We could also rely on the badge to install the application (and the AIR runtime if necessary)… however, application packaged as native installers cannot be installed, upgraded, or launched by the badge API (and we need to package ours as native to use native processes).
    We also noticed that multiple versions of an AIR application cannot be installed side-by-side in a client machine, and that the installation and upgrade of the application can be performed only when the local user has administrative rights on the machine (using standard or native packages), forcing us to rely on external software distribution systems in some customer scenarios (introducing additional complexities in the release cycle).
    At this point, in our opinion the standard deployment strategies of Adobe AIR applications are unfit for enterprise environments. In the enterprise world, many of the applications have migrated to a completely browser-based solution, while others enhanced their client layer to comply with the requirements, for example installing only a thin portion of the client code and allowing to connect to multiple server versions/environments with it (e.g. the SAP GUI universal client). Without smarter deployment and distribution tools, AIR applications currently are a step back compared to web applications in terms of manageability.
    So, we are trying to develop a solution to address these problems, with some concepts similar to JStart: install on the client machine a launcher application capable of being activated from a web page, dynamically locate, download and run the actual client bytecode, transparently enforce client software updates, and supporting multiple applications (and multiple versions of the same application). However, we are facing many technical problems due to internal architecture of AIR and we already spent a considerable amount of effort trying to find a solution. We are now thinking to return on the choice of AIR, going back to Flex.
    What is the position of Adobe on this argument? Is Adobe aware of these issues and are there any plans on this topic? Any advice?
    Thank you in advance

    For those following along, Oliver Goldman will be answering this post in future articles on his blog.
    Many great comments and questions here. I’m working on some follow-up posts to address these; nothing I could cram into this comment field would really do your query justice. - Oliver Goldman
    Pursuit of Simplicity
    Chris

  • Packaging an AIR application in a native installer

    Hi! I'm trying to create a native installer of my AIR Application,  because (I think) it's the only way make the native processes working.  But I have a problem: I used the following command to pack: "adt  -package -storetype pkcs12 -keystore myCert.pfx -target native  -storetype pkcs12 -keystore myCert.pfx myApp.exe myApp-app.xml", but I get  the error: "File myApp-app.xml is not a valid AIRI or AIR file". In the  Flash Builder I use as additional compiler arguments:  "-locale=pt_PT,en_UK,fr_FR,de_DE,ro_RO,es_ES  -allow-source-path-overlap=true -source-path=assets" and I add the  source path "src/locale/{locale}/". What is the sintax for packing my  AIR application in a native installer? Thanks in advance.

    Hi again! Thanks for the reply. I based myself on the link to see what command syntax I should use to pack my Air Windowed Application and it was the command that I presented in the previous post.
    adt version "2.0.1.12090"
                                                  My Descriptor File
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.0">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.0
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
             Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>com.MyCompany.Application</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>Production Control System</filename>
        <!-- The name that is displayed in the AIR application installer.
             May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>Production Control System</name>
        <!-- An application version designator (such as "v1", "2.5", or "Alpha 1"). Required. -->
        <version>2.1.3</version>
        <!-- Description, displayed in the AIR application installer.
             May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID>My Company</publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
            <!-- The title of the main window. Optional. -->
            <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <systemChrome>none</systemChrome>
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <transparent>true</transparent>
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <supportedProfiles>extendedDesktop</supportedProfiles>
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
             specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image48x48></image48x48>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <customUpdateUI>true</customUpdateUI>
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
        <!-- iPhone/iPad -specific capabilities -->
        <!-- <iPhone> -->
            <!-- A list of plist key/value pairs to be added to the application Info.plist -->
            <!-- <InfoAdditions>
                <![CDATA[
                    <key>UIDeviceFamily</key>
                    <array>
                        <string>1</string>
                        <string>2</string>
                    </array>
                    <key>UIStatusBarStyle</key>
                    <string>UIStatusBarStyleBlackOpaque</string>
                    <key>UIRequiresPersistentWiFi</key>
                    <string>YES</string>
                ]]>
            </InfoAdditions> -->
        <!-- </iPhone> -->
    </application>

  • Possible bug in Browser Invocation

    I have done more testing with the isHTTPS property of the Browser Invoke event. I have started an application from a webserver with no https anywhere but still the isHTTPS property is true at all times. If this is a bug how do I report it. It seems to me that if an application must be secure this feature has to work correctly. If I am mistakenly doing something wrong can someone help?

    I am using the browser invocation method to start my AIR application. I only want the app. to function correctly if started from a https connection. Therefore in my code I am trying to check that the isHTTPS attribute of the browser invoke event is true. However, whether the application is started from http or https, the isHTTPS attribute is always true. I have had to code a workaround for this, but I should not have had to do this.

  • Installing an AIR application generated from a PHP script using a badge

    I have written a PHP script to return a file with the Content-Type header set to application/vnd.adobe.air-application-installer-package+zip to simulate a response that looks like an AIR file.  The Content-Length and Content-Disposition headers are also being sent.  I am then writing the bytes of the file to the output.  This appears to work in the browser, as the file downloads and can be installed.  However, when the badge tries to use the URL, I get a Stream 2032 error.  Does the AIR badge not allow a URL without an .air extension, even if the response is in the correct format for an AIR file?  If this is allowed, are there other headers that need to be set for this to work?
    Thanks,
    Paul

    I figured it out.  The AIR installer was stripping out my query parameters.  I made the URL use slashes for the parameters with a rewrite instead of ? and & it worked.

  • Browser Invocation - from HTML element click

    If anyone knows how to make this happen, I would really
    appreciate any info. Adobe is trying to replicate the 'popup
    protection' that most modern browsers implement which prevents new
    browser windows from being opened when the action is not triggered
    by a user click (to prevent popup spam). However when the browser's
    implemented this feature they allowed javascript code the may be at
    the end of a cascade to open a browser window by correctly noticing
    that the event that triggered the code cascade was indeed a click.
    However it seems that Adobe's implementation requires a click
    directly on the SWF containing the embedded air.swf and therefore
    prevents any non-flash content on a web site is to successfully
    launch an air application even when triggered by an direct user
    interaction.

    Hi, Rico-
    Have you read the section of the API doc on calling an Animate composition from outside of the composition?
    http://www.adobe.com/devnet-docs/edgeanimate/api/current/index.html#differentcompositions
    -Elaine

  • Distributing AIR Application

    Helo.
    I do part of a portal of tutorials related to Adobe products
    and i write tutorials to Flash and recently started to look on
    Adobe AIR and immediately wrote a tutorial on how to create
    applications in the Air Flash CS3. Now i am ending to write a
    tutorial showing how to create custom chromes using Flash and i
    want let a air file to the users download and install them on
    machines.
    The question is, can i do this? Do i need make some register
    in some place or i can't let my files to be downloaded? I have read
    a page of terms and i do not know if I'm within those terms.
    Other thing, how can i create that swf with a image of my
    application and a button to install my AIR file?
    Thanks

    quote:
    can i do this?
    I don't know if
    you can, but
    I can. So yes, maybe you can, too.
    quote:
    Do i need make some register in some place or i can't let my
    files to be downloaded?
    You don't need Adobe's permission to create or
    distribute an AIR application. Some Adobe components do get
    installed automatically by the AIR installer along with your
    program when you use the two main installation mechanisms, and
    these are covered under your license to use AIR.
    The first supported installation mechanism is just running a
    .air file, which launches the AIR installer (if AIR is installed on
    that machine) and installs your program.
    The second mechanism is the badge installer, which works from
    a web page in any browser that has a recent version of the Flash
    plugin. This option doesn't require AIR to be installed on the
    client computer first. It will download that if necessary, install
    it, and then download your AIR file and kick off the regular
    installation process. Just search for "badge" in the documentation
    to learn more.
    The main thing you're not allowed to distribute without
    permission from Adobe is the AIR installer itself. You can get
    redistribution permission, but you do have to ask.
    quote:
    how can i create that swf with a image of my application and
    a button to install my AIR file?
    This is roughly what the badge installer does.
    Not exactly, but it's the same idea.

  • How to Call a AIR application from Flex Application

    Hi,
        I have Used AIR (Desktop application) in Flex Builder to Upload a File from a local path and save it it a server path.
    I need to Call this AIR(Desktop application) from my Flex Application.... i.e
    I am using a link button to send a event using Script and Forward that Desktop application  from Flex Screen
    But it doesnot load that (Desktop application)  in Screen. Only Balnk screen is loaded from path
    Here is the code
    AIR(Desktop application)
    <?xml version="1.0" encoding="utf-8"?><mx:WindowedApplication 
    xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="openBrowseWindow();">
    <mx:HTTPService id="urlpath" showBusyCursor="true" useProxy="false" method="
    POST" url="http://localhost:8080/nat/FlexAction.do?method=UrlPath"result="pathresult(event)"
    fault="faultHandler(event)"
    >  
    </mx:HTTPService> 
    <mx:Script>
    <![CDATA[
    import mx.events.FileEvent; 
    import mx.rpc.events.ResultEvent; 
    import mx.rpc.events.FaultEvent; 
    import mx.utils.ObjectUtil;  
    import mx.controls.Alert;
    private  
    var openFile:File = new File() 
    private  
    function openBrowseWindow():void{openFile.addEventListener(Event.SELECT, onOpenFileComplete);
    openFile.addEventListener(Event.OPEN, load);
    openFile.browse();
    private  
    function load():void{Alert.show(
    "load"); 
    var imageTypes:FileFilter = new FileFilter("Images (*.jpg, *.jpeg, *.gif, *.png)", "*.jpg; *.jpeg; *.gif; *.png"); 
    //var textTypes:FileFilter = new FileFilter("Text Files (*.txt, *.rtf)", "*.txt; *.rtf"); 
    var allTypes:Array = new Array(imageTypes);openFile.browse(allTypes);
    private  
    function faultHandler(event:FaultEvent):void { 
    //Alert.show("Fault")Alert.show(ObjectUtil.toString(event.fault));
     private  
    function pathresult(event:ResultEvent):void{Alert.show(
    "res") 
    //Alert.show(ObjectUtil.toString(event.result));}private  
    function onOpenFileComplete(event:Event):void{ 
    //mx.controls.Alert.show("event: "+event.target.nativePath +"UR!!!"); 
    var pPath = event.target.nativePath; 
    var parameters:Object = {FlexActionType:"PATH",path:pPath};  
    // Alert.show("Image Selected from Path : "+pPath); urlpath.send(parameters);
    //Alert.show("Passed.."+parameters);}
    ]]>
    </mx:Script>
    <mx:Button click="openBrowseWindow();onOpenFileComplete(event)" name="Upload" label="Upload" x="120.5" y="10"/> 
    Here is Mxml Code for Flex Application
    <?xml version="1.0" encoding="utf-8"?><mx:Application 
    xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" xmlns="http://ns.adobe.com/air/application/1.0.M4" >
    <mx:Script>
    <![CDATA[
    import mx.controls.Alert; 
    private function Upload():void{ 
    // CursorManager.setBusyCursor();  
    //var url:String = "HomeAction.do?method=onLoad"; 
    //var url:String = "assets/Air.swf"; 
    var url1:URLRequest = new URLRequest("assets/Air.swf");navigateToURL(url1,
    "_self"); 
    // CursorManager.removeBusyCursor(); }
    ]]>
    </mx:Script>
    <mx:LinkButton id="up" click="Upload()" x="295" y="215" label="UpLoad"/>
    In this code i forward using s url to Open tat  Desktop application but a blank screen appears with out the proper output...
    Please Help me in this to forward AIR from Flex Screen..
    Thanks in Advance
    With Regards
    Gopinath.A
    Software Developer
    First Internet Systems Pvt. Ltd.,
    Chennai

    try this
    http://www.leonardofranca.com/index.php/2009/09/17/launching-an-installed-air-application- from-the-browser/
    regards
    Leonardo França
    Adobe Certified Expert Flex 3 with AIR
    Adobe Certified Expert Rich Internet Application Specialist v1.0
    Adobe Certified Expert Flash CS3 Professional
    Certified Professional Adobe Flex 2 Developer
    Adobe Certified Professional Flash MX 2004 Developer
    http://www.leonardofranca.com
    http://twitter/leofederal
    Manager AUGDF - Adobe User Group do Distrito Federal
    http://www.augdf.com.br
    http://twitter/augdf

  • Cl_gui_frontend_services=   allow browsing to directory path

    Hi guys,
    i have created a program to automate the download of joblogs and spools using CALL TRANSACTION SM37 .
    currently i am taking the location where files need to be stored from selection screen.
    now  i want to use  <b>cl_gui_frontend_services=>?</b>
    to allow browse function to directory path where i need to save the files(i.e spool and joblog).
    it will be of great help if you could send me a piece of code using cl_gui_frontend_services=>? which can <i><i><u>allow browsing to directory path</u></i></i> where i can save the files.
    Thanks
    Ankit
    LnT Infotech,Mumbai

    I had the same problem like Adel when calling the browser via cl_gui_frontend_services=>execute().
    On my old school XP machine the synchronous start is doing well, but not on my colleagues W7 64 machines.
    I used a registrey key to get - in my case - the path to the Internet Explorer.
    (htmlfile\shell\open\command)
    On W7/64Bit this key contains the path to the 32 bit Binary:
    C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    If I start this application it's not synchronous, if i hard-code the path 64 bit binary
    (C:\Program File\Internet Explorer\IEXPLORE.EXE) the application runs synchronous.
    A pragmatic programmer could replace the ' (x86)' in the path, which should work on most Windows platforms
    Regards
    Dominik

  • Opening a PDF in Acrobat via an AIR application

    Hey,
    I'm creating my first AIR application. The application needs to be able to launch Acrobat to view a PDF file.
    I have done a lot of searching and can't seem to find anything, could someone point me in the right direction?
    I read a response here:
    http://stackoverflow.com/questions/161570/how-do-i-launch-a-standalone-swf-from-within-an- abode-air-application
    That said:
    "The AIR-Runtime is (still) not able to launch external Applications, except Acrobat Reader for PDFs and the default Browser (you can let the browser display the swf)."
    Which led me to believe there was a way to do this.
    Thanks for your help.
    -Jason

    You can view PDF by opening the html window with iframe (width and height 100%) that points to the PDF file.
    I don't think its currently possible to start programs like Acrobat reader from AIR.

Maybe you are looking for