A Faster Flex 3 SDK (Deitte.com) At Brightcove I've spent some time creating faster Flex 3 SDKs by merging some changes from the Flex 4 SDK. It's not a lot of changes, but it makes a fairly significant improvement in compilation speeds in Flex Builder. I find for small changes in a large project, there's about a 20%25% speedup, but this varies greatly depending on what you're doing. I'll give some performance numbers below and explain exactly what changed, but first I'll show you how you can use these changes yourself. Using the Changes Here are the files you'll need, with one zip file for Flex 3.0, Flex 3.1, and Flex 3.2: fast-3.0.zipfast-3.1.zipfast-3.2.zip Inside of the zip files you'll find jars that should overwrite existing files in FLEX_SDK/lib, where FLEX_SDK is the location of the Flex SDK you are using. There's another zip file that you can try out, which contains some more changes from Flex 4. fast-experimental-3.0.zip Performance Numbers Why I Did This More on the Changes
How to Load and Interact with an External SWF File in AS3 and Flash One of the most versatile features of Flash is the ability to import swf files into a "containing" Flash movie and the ability for the "containing movie" to interact with the imported swf. We have addressed various aspects of this issue with our previous tutorials, External Clips in Flash CS3, Loading External SWF Files for a Dynamic Presentation, and Loading and Unloading SWF's with 'stage' References in AS3. In the simple example shown below, the external swf (built from the file ext.fla included for download) consists of a 400 by 200 movie that has a global variable called total and a public function called updateBackAndTotal, which takes a single color parameter as an argument. A call to updateBackAndTotal(clr) draws a rectangle with color clr to fill the stage of the external swf and adds as text the value of the total variable. The file ext.swf on its own is shown first. Download Download the two fla files for this tutorial in the following compressed folder. ExternalSWF.zip
XML-RPC XML-RPC is a remote procedure call (RPC) protocol which uses XML to encode its calls and HTTP as a transport mechanism.[1] "XML-RPC" also refers generically to the use of XML for remote procedure call, independently of the specific protocol. This article is about the protocol named "XML-RPC". History[edit] The generic use of XML for remote procedure call (RPC) was patented by Phillip Merrick, Stewart Allen, and Joseph Lapp in April 2006, claiming benefit to a provisional application filed in March 1998. Usage[edit] XML-RPC works by sending a HTTP request to a server implementing the protocol. Identification of clients for authorization purposes can be achieved using popular HTTP security methods. In comparison to REST, where resource representations (documents) are transferred, XML-RPC is designed to call methods. JSON-RPC is similar to XML-RPC. Data types[edit] Common datatypes are converted into their XML equivalents with example values shown below: Examples[edit] <? <? <? Criticism[edit]
Locale data for AS3 3D Card Flips with Tweens in Flash CS4 and Flash CS3 Flash Player 10 supports native 3D methods in ActionScript 3 so flipping images with perspective distortion is much easier in Flash CS4 than in Flash CS3. It has its challenges, though. One of them is the problem of blurring of 3D objects when those 3D methods are used. Download Download all files corresponding to this tutorial: tweenflip.zip All the source files in the package are well-commented. The Timeline Code - Customizing an Instance of TweenFlipCS4 The static text on the stage was created at authoring time. Here is the Timeline code in flip_cs4.fla followed by explanations. import fl.transitions.easing import flashandmath.as3.TweenFlipCS4; var card1:TweenFlipCS4; var card2:TweenFlipCS4; card1=new TweenFlipCS4("bkimage.jpg","bkcard.jpg","horizontal"); this.addChild(card1); card2=new TweenFlipCS4("deimage.jpg","decard.jpg"); this.addChild(card2); setCardsPosAndProps(); function setCardsPosAndProps():void { card1.x=25; card1.y=85; card2.x=330; card2.y=85; card1.setFunc(Back.easeOut);
GNU Emacs Manual GNU Emacs Manual Table of Contents DistributionGNU GENERAL PUBLIC LICENSEPreambleHow to Apply These Terms to Your New ProgramsA. GNU Free Documentation LicenseADDENDUM: How to use this License for your documentsIntroductionB. Edge: June 2009 - A beginner's guide to the Mate framework by Brian Rinaldi For the longest time, Cairngorm seemed to be the only viable lightweight Flex framework. Lately some new Flex frameworks have been growing in popularity. One of the newer frameworks that is gaining ground among bloggers and other Flex developers is Mate. Created by Nahuel Foronda and Laura Arguello of AsFusion, Mate (pronounced mah-teh) is a tag-based, event-driven framework that focuses on giving developers maximum flexibility. In general, Mate is easy to learn. Like other frameworks, Mate addresses the common architectural concerns in Flex such as event handling, data binding, and asynchronous processing. Getting started The sample application I use in this article is the Upcoming.org API. For the back end of this application, I use Adobe ColdFusion. You can download the code for the sample application via Subversion at Admiring the view Creating events about upcoming events The EventMap and mapping events Confronting your Manager
RedmineWikiFormatting Links¶ Redmine links¶ Redmine allows hyperlinking between resources (issues, changesets, wiki pages...) from anywhere text formatting is used. Link to an issue: #124 (displays #124, link is striked-through if the issue is closed) Link to an issue note: #124-6, or #124!#note-6 Link to a changeset: r758 (displays r758) Link to a changeset with a non-numeric hash: commit:c6f4d0fd (displays c6f4d0fd). Wiki links: [[Guide]] displays a link to the page named 'Guide': Guide [[Guide|User manual]] displays a link to the same page but with different text: User manual [[Guide#User-guide|User guide]] displays a link to the header on the same page with different text: User guide You can also link to pages of another project's wiki (using the project identifier): [[sandbox:some page]] displays a link to the page named 'Some page' of the Sandbox wiki [[sandbox:]] displays a link to the Sandbox wiki main page Wiki links are displayed in red if the page doesn't exist yet, eg: Nonexistent page. Escaping: Acronym¶
BrowserLab Dear BrowserLab customers, When we originally launched BrowserLab as a free service back in 2009, our customers were struggling with testing their web content across desktop browsers and platforms. Since then with the growth of the importance of mobile devices and tablets, the landscape has changed dramatically. Because of this shift, we have seen the usage of BrowserLab drop over the past year while at the same time our engineering team has been focusing on solving this new challenge with new solutions. Due to this, we will be shutting down the Adobe BrowserLab Service effective immediately. If you need to test across multiple desktop browsers, we recommend that you check out BrowserStack and Sauce Labs as two viable alternatives to BrowserLab. If you are working on mobile web projects, check out Adobe Edge Inspect. We’d like to thank all of our customers over the years for using and providing input for the Adobe BrowserLab Service. Best Regards, Bruce Bowman Sr.
HTML Current Status This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title links to the most recent version of a document. Completed Work W3C Recommendations have been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and are endorsed by the Director as Web Standards. Learn more about the W3C Recommendation Track. Group Notes are not standards and do not have the same level of W3C endorsement. Standards Group Notes Drafts Below are draft documents: Candidate Recommendations, other Working Drafts . Candidate Recommendations Other Working Drafts Obsolete Specifications These specifications have either been superseded by others, or have been abandoned. Retired
Action Script Error Repository Antipattern Un article de Wikipédia, l'encyclopédie libre. En génie logiciel, les anti-patrons ou antipattern sont des erreurs courantes de conception des logiciels. Leur nom vient du fait que ces erreurs sont apparues dès les phases de conception du logiciel, notamment par l'absence ou la mauvaise utilisation de patrons de conception, appelés design pattern en anglais. Les anti-patrons se caractérisent souvent par une lenteur excessive du logiciel, des coûts de réalisation ou de maintenance élevés, des comportements anormaux et la présence de bugs. Il existe également les GreyPatterns (dont le bénéfice ou les inconvénients ne sont pas clairement établis). Anti-patrons de développement[modifier | modifier le code] Abstraction inverse[modifier | modifier le code] Exemple : avoir un objet qui ne fait que des calculs en virgule flottante, et être obligé d'utiliser cet objet pour faire du calcul avec des entiers. Action à distance[modifier | modifier le code] Ancre de bateau[modifier | modifier le code]
flex-compiler-shell-daemon - Google Code Usage $ fcshd.py "mxmlc /path/to/foo.mxml -o /path/to/foo.swf" Loading configuration file [...][...]/path/to/foo.swf (349854 bytes)(fcsh) $ fcshd.py "mxmlc /path/to/foo.mxml -o /path/to/foo.swf" Loading configuration file [...]Nothing has changed since the last compile. Skip.../path/to/foo.swf (349854 bytes)(fcsh) Why? If you do flex development outside Flex Builder (very likely if you use Linux, as the official Flex Builder is quite buggy there), using the command line mxmlc is a painfully sloooooow. Fortunately, Adobe released a tool called the Flex Compiler Shell, abbreviated as fcsh, which speeds up the compilation time considerably. Unfortunately, fcsh doesn't work well when you want to integrate fcsh with the common build toolchains, where the compiler is expected to compile the source and exit (with at least a non-zero exit code if the compilation failed, of course). Here is a simple solution to the problem: "The Flex Compiler Shell Daemon", or fcshd for short. Installation