background preloader

Adobe Flex 3 Component Life Cycle

Adobe Flex 3 Component Life Cycle
Related:  Flash AS3

João Saleiro - Google+ - After 6 years doing Flex, am I moving to HTML5? Short… After 6 years doing Flex, am I moving to HTML5? Short answer: no. But I'm investing in HTML5. (really) Long answer: see below. After returning from the Flex Summit, many people have contacted me asking what was going to happen with Flex and if I was going to "migrate" our projects (like ) and services to HTML5. Background I founded Webfuel in 2004 and since then we've specialized in building long-term (> 6 months) enterprise-grade RIAs that had to scale well and be prepared for constantly changing requirements with a low cost in maintainability, while simultaneously providing a top-notch user experience. Worse PR ever in November 2011 The Flash platform was already in bad shape, much thanks to one year of chaotic PR and there were already some inconsistent signs from Adobe hinting what was going to happen. In December '11 Adobe has donated Flex to Apache. Did Adobe kill Flex? Will the perception around Apache Flex ( ) improve? jQuery IDEs

crontab Unix systems start up the cron daemon in multi-user mode. Hence, so does Linux. The cron daemon will execute programs at predestined times. The daemon wakes up every minute and runs the commands as necessary. Files in which the time and interval to run commands are specified, as well as the commands themselves, are called crontab files. By default, either only the superuser or every user will have the right to create and maintain a crontab file (which of the two depends on the local configuration). The information in user files is often stored in memory by the daemon - therefore, when you change the user files manually, by editing them, you will need to restart the cron daemon to activate the changes. $ crontab -e to edit your personal entry. Alternately, you can use a file in your HOME directory (or another location where you have write-access) and edit this file. crontab <the-file-name> To deactivate it, use: crontab -r format of the crontab file VARIABLE=value $ at 20:00 Jul 17 2038

com - Security Domains, Application Domains, and More in ActionScript 3.0 Pages: 1 | 2 Application Domains As seen with security domains, class definitions can be isolated from one another when SWFs are in different security sandboxes, each having their own complete set of definitions to work with. Application domains exist inside security domains While security domains sandbox for security, application domains sandbox for definition separation. Application domains work together in a linked hierarchy making them more complex than security domains which are each isolated and individualized. At the root of this hierarchy is the system domain , the application domain that contains the native definitions of the Flash Player API. When a new SWF is placed into its respective security domain as it initializes an instance of Flash Player, an application domain is created to contain the ActionScript definitions that were compiled with it. New SWF domain loaded into and inherits from system domain More on inheritance is covered in the Application Domain Inheritance section.

Pratique d'ActionScript 3 Pratique d'ActionScript 3 s'adresse à tous les flasheurs. Cet ouvrage dresse un panorama de l'utilisation d'ActionScript 3 et de ses nouveautés, ainsi que du nouveau lecteur Flash 9. L'auteur explique au travers de nombreux exemples et cas concrets comment traiter désormais les objets, le texte, le son et la vidéo, le chargement et l'envoi de données externes (variables, XML, etc.), les sockets, etc. Article lu 5644 fois. A propos de l'auteur▲ Thibault IMBERT est aujourd'hui ingénieur système chez Adobe France. Il a commencé en tant que développeur Flash pour différentes agences, avant de rejoindre comme formateur et responsable pédagogique pour toutes les formations conçernant la plate-forme Flash. Pendant son temps libre, Thibault expérimente ActionScript 3, comme en témoigne son site Remerciements▲ Préface▲ Télécharger ce chapitre (35 pages) au format pdf ( miroir ) Télécharger ce chapitre (35 pages) au format pdf ( miroir )

Flash Professional Help | Graphic filters Enhanced in Flash Professional CC Each time you add a new filter to an object, it is added to the list of applied filters for that object in the Property inspector. You can apply multiple filters to an object, as well as remove filters that were previously applied. You can apply filters only to text, button, movie clip, components, and compiled clips objects. You can create a filter settings library that lets you easily apply the same filter or sets of filters to an object. With Flash Professional CS6 and earlier versions, applying filters was restricted to movie clip and button symbols only. Create or add a component on stage.Right click on the component, and select Convert to Symbol. With Flash Professional CS6 (and earlier versions), you could add filters or various other kinds of effects after wrapping the component inside a symbol. Adding Bevel filter to a Button component

Object Definitions Introduction One of the features of Nagios' object configuration format is that you can create object definitions that inherit properties from other object definitions. An explanation of how object inheritence works can be found here. When creating and/or editing configuration files, keep the following in mind: Lines that start with a '#' character are taken to be comments and are not processed Directive names are case-sensitive Characters that appear after a semicolon (;) in configuration lines are treated as comments and are not processed Retention Notes It is important to point out that several directives in host, service, and contact definitions may not be picked up by Nagios when you change them in your configuration files. One way to get around this problem is to disable the retention of non-status information using the retain_nonstatus_information directive in the host, service, and contact definitions. Sample Configuration Files Object Types Description: Definition Format:

Download file with FileReference Tuning Garbage Collection with the 5.0 Java[tm] Virtual Machine Introduction The Java TM 2 Platform Standard Edition (J2SE TM platform) is used for a wide variety of applications from small applets on desktops to web services on large servers. In the J2SE platform version 1.4.2 there were four garbage collectors from which to choose but without an explicit choice by the user the serial garbage collector was always chosen. In version 5.0 the choice of the collector is based on the class of the machine on which the application is started. This “smarter choice” of the garbage collector is generally better but is not always the best. When does the choice of a garbage collector matter to the user? Amdahl observed that most workloads cannot be perfectly parallelized; some portion is always sequential and does not benefit from parallelism. The graph below models an ideal system that is perfectly scalable with the exception of garbage collection. The serial collector will be adequate for the majority of applications. Ergonomics for an application. Generations

Branding Here is a branded version of Flowplayer. Almost all of the following features are available only in commercial versions of Flowplayer such as a custom logo, a custom play button and a configurable “right-click” context menu. The above player has all of the commercial features enabled. Remember to click the player with your right mouse button. Logo Customization of the logo plugin is the main reason for buying the commercial versions of Flowplayer (which gives us the ability to work on this project full- time). You can also specify all display properties for the logo as with any other plugin. Logo example Here we have a customized logo. The right-click menu is the menu that is shown when a user right-clicks the player with the mouse. Here is the default configuration in the free version. As you can see from the example above, the contents of the menu are defined by means of a JavaScript array. 1 Objects with a single property. 2 Menu separators. 3 Labels. Play button Example

java - Why is it a bad practice to call System.gc Java SE 6 HotSpot[tm] Virtual Machine Garbage Collection Tuning Note: For Java SE 8, see Java Platform, Standard Edition HotSpot Virtual Machine Garbage Collection Tuning Guide. The Java™ Platform, Standard Edition (Java SE™) is used for a wide variety of applications, from small applets on desktops to web services on large servers. In support of this diverse range of deployments, the Java HotSpot™ virtual machine implementation (Java HotSpot™ VM) provides multiple garbage collectors, each designed to satisfy different requirements. This is an important part of meeting the demands of both large and small applications. However, users, developers and administrators that need high performance are burdened with the extra step of selecting the garbage collector that best meets their needs. This better choice of the garbage collector is generally an improvement, but is by no means always the best choice for every application. When does the choice of a garbage collector matter? A feature referred to here as ergonomics was introduced in J2SE 5.0. eden . . .