
Ahi vamos!
Conferencia online presentando la nueva suite CS4.
Writer, melómano, blogger, digital artist, designer and web developer focused on interactive media. ISO 9001 Certified Expert. AppSheet + AI Expert + Data Analyst Senior + Innovation Teacher. Google Certified Expert. Criptominero e Inversor Inmobiliario & Somm Student. 🎯✅️🔥💪🏽💫
"...a bitmap is made up of pixels. It can be thought of as a grid of color values, which designate a particular color for each and every pixel. Each pixel is a cell in the grid. A 100 x 100 pixel bitmap can be described by a grid of 10,000 color values, one for each pixel.
Each color value in a bitmap is a binary number. A binary number is made up of bits, whose values can be either 0 or 1. This binary number will differ in length, depending upon the color depth of the bitmap. The color depth of a bitmap determines the range of possible color values that can be used in each pixel. For example, each pixel in a 24-bit image can be one of roughly 16.8 million colors. Those colors are formed by mixing together varying quantities of three primary colors: red, green, and blue. The three main colors are called channels. It follows that:
Therefore the color value for each pixel in a surface created by Flash Player is 32 bits long, or 4 bytes.
4 * 8 = 32 bit
The bitmap that is created by Flash Player to represent the visual state of a movie clip when you turn bitmap caching on will have the same dimensions (width and height) as the movie clip.
A cached movie clip that is 100 x 100 pixels has 10,000 pixels.
100 * 100 = 10,000 pixels
Each of those pixels will be 32 bits or 4 bytes. Therefore the movie clip will use an extra 40,000 bytes of memory.
10,000 * 4 = 40,000 bytes
There are 1024 bytes in 1 kilobyte (K). So, 40,000 bytes can also be said to be roughly 40 kilobytes (40K).
..."
LO ACABO DE APRENDER!
Sometimes, Method 1 is almost impossible for you due to some reasons. Then Method 2 is a great alternative for you. If your hosting provider tells you that FLV videos are not supported for the hosting package you have purchased, you can Do It Yourself. See the following steps:

Este mes estuve envuelto por primera vez en el desarrollo de un widget* para un cliente.
What you have to do when a client give you thousands of HQ images for editing, resizing and re touching at pixel level and so on?


Let's start where most websites begin — in a bar, restaurant, or café, someone scribbles a site map or sketches a potential layout on a napkin. From there, the concept makes its way into Adobe Photoshop where a designer puts together the pixel-based vision, one layer at a time. Before long, he or she has shuffled the pixels into place to form the first page.
Then, additional pages are produced by creating new layer groups while turning off others. During a recent visit to a customer, we observed one designer working on a comp in Photoshop that contained more than 150 layers — 90% of which were toggled off at any given moment. To show the client, she had to tediously export a JPEG, turn layer groups on and off, re-export, turn layer groups on and off, re-export, and so on.
With Adobe Fireworks® CS3, this process can now be greatly streamlined. Instead of having to work with a single Photoshop file consisting of an unwieldy number of layer groups, you can begin to build Photoshop comps logically: one PSD equals one web page. Then, using the new Pages panel in Fireworks CS3, you can import the individual PSD files as actual pages. Fireworks CS3 now understands the native PSD file format and can maintain the appearance of the layers and layer groups, even to the point of editing layer effects and styles. After importing the PSD files as pages, layers and layer groups can be shared across multiple pages. Imagine only having to create a navigation bar once and then being able to distribute it across numerous comps. Change any element on a shared layer, and it updates on all the pages. Finally, by quickly adding hotspots to proposed navigational elements, Fireworks can export the page comps to the web with one click. Not only can clients now see the proposed layouts, but they can interact with them as well.

Apollo is the code name for a cross-operating system runtime being developed by Adobe that allows developers to leverage their existing web development skills (Flash, Flex, HTML, JavaScript, Ajax) to build and deploy rich Internet applications (RIAs) to the desktop.
Apollo enables developers to create applications that combine the benefits of web applications – network and user connectivity, rich media content, ease of development, and broad reach – with the strengths of desktop applications – application interactions, local resource access, personal settings, powerful functionality, and rich interactive experiences.

http://www.flickr.com/photos/58448846@N00/
Ahi las interfaces que hice para ATB en estos ultimos tiempos.
Nice eh?
Timer class provides a cleaner mechanism for timer events than the setInterval and setTimeout functions. The new Timer class has a number of advantages over setInterval, such as not having to deal with interval ID numbers, and a more modern, object-oriented interface. We regard using Timer instead of setInterval and setTimeout as a best practice.
"Conceptualmente, la relación existente entre las página XSLT vinculada y la página XML es similar, aunque no coincide con el modelo de la página CSS/HTML externa. Si se dispone de una página HTML con contenido (por ejemplo, texto), puede utilizar una hoja de estilos externa para dar formato al contenido. La página HTML determina el contenido y el código CSS externo (invisible para el usuario) determina la presentación. Con XSLT y XML, la situación cambia. El archivo XML (que el usuario nunca ve en un forma original) determina el contenido, mientras que la página XSLT determina la presentación. La página XSLT contiene las tablas, formato, gráficos, etc., que suele contener el HTML estándar. Cuando un usuario visualiza el archivo XML en un navegador, la página XSLT da formato al contenido."
La implementación de Flash para Linux puede resultar problemática, en especial, para los usuarios de Debian y Ubuntu. Somos conscientes de estos problemas, sin embargo, debido a la falta de actualizaciones y al escaso desarrollo del complemento Flash para Linux, en estos momentos, es posible que no podamos aceptar la combinación de su navegador y sistema operativo.
_____________________
Well, esta nota que está al final de Google Analytics demuestra claramente el coletazo de tiburón resultante de la adquisición de Macromedia por Adobe, hace poco más de un año, jugando para el monopolio infernal estadounidense en torno al sistema operativo más famoso do mondo. Está, todos sabemos la movida openSource de la maquina Flash de Adobe, pero Linux, Debian y Ubuntu son más que buenas intenciones para hacerle el awante al mostro Windows.