Posts Tagged ‘Adobe’


Adobe releases a beta version of AIR 3.7. The beta release provides access to the AIR 3.7 runtime and SDK for Windows, Mac OS, iOS and Android.

Below are some of the key features and benefits of AIR 3.7:

Captive Runtime Debugging Capability for Mobile Apps: This feature provide Android developers with a mechanism to create & debug captive apps.

Preventing backup of Shared Objects (iOS): To comply with Apple updated guidelines, only user data can be backed up on iCloud. Any files that can be downloaded or generated should not be backed up and it should be marked as “DoNotBackup”. This feature allows developers to control which files should be backed up or excluded using the “DoNotBackup” attribute.

Forcing CPU Rendermode on some devices (iOS): This feature allows developers to control the render mode on different iOS devices. Using this feature developers can turn on CPU rendering for specific iOS devices, and utilize GPU rendering for others.

Loading External SWFs – iOS: This feature allows developer to externally host SWFs and load them as needed. External SWFs could contain game assets, different game levels, etc. Benefits of this feature are faster initialization time, smaller apps, and more control over your game or app.

For more details and download : http://labs.adobe.com/technologies/flashruntimes/air/


Before Adobe AIR 3, only Adobe could add core features to the Adobe ANEruntime. Developers only have to wait for new feature addition in core library. Now as a developers we can extend the runtime ourselves and expend the possibility in application. Using this ANE power now we are more integrated with target devices. Now we can easily incorporate legacy native code in our application.

This ANE capability is a prefect gift to mobile apps developer by Adobe. Thanks Adobe for providing this capability in AIR. 

Definition of ANE by Adobe :

Native Extensions for Adobe AIR are code libraries that contain native code wrapped with an ActionScript API. Native extensions provide easy access to device-specific libraries and features that are not available in the built-in ActionScript classes. Examples of native extensions include making a mobile device vibrate, integrating ad-networks and in-app purchasing systems into your games, and using the iOS Game Center in your iOS games.

ANE

Personally I recommend you to visit community page of ANE. This is very good showcase of Adobe AIR Native Extension feature. ANE community page url is : http://extensionsforair.com/

Apart from this you can also explore more from Adobe developer centre : http://www.adobe.com/devnet/air/native-extensions-for-air.html

Adobe Flex now Apache Flex

Posted: January 8, 2012 in Adobe, Flex, RIA, Technology
Tags: , , , , ,

End of the last year (Nov – 2011) Adobe planed to donate Flex to Apache foundation and now Flex is officially accepted by Apache Software Foundation(ASF). For more info on this check the mail thread conversation on voting at Apache – http://markmail.org/message/7q22pdviyxvkwbf5.

This year 2012 is the first year of Flex to live outside Adobe and managed by open source Apache Foundation. In the other side Adobe is also planning to renovate the Flex compiler and they are researching on making it possible to convert ActionScript code to JavaScript code. In this way we can develop HTML/HTML5 based application using ActionScript code. The open source movement is very popular and this is strengthen every year. Now onwards Apache is the the future for Flex. Apache Software Foundation was founded and is governed by the common people that really understand open source development model. It is one of the most respected software foundations in the world. To know more about how Apache Software Foundation (ASF) works then visit this link – http://www.apache.org/foundation/how-it-works.html.

For more info on this – http://wiki.apache.org/incubator/FlexProposal

Adobe Flex now Apache Flex


Adobe Flash Player

Adobe Flash Player

Flash is travelled very long distance in last decade, from Macromedia Flash to Adobe Flash. This Flash word is always in tech buzz. Initially it was popular in animator group then gradually attracted the attention of application developers and became a de-facto for RIA applications.

Flash is always preferable for developing richest content and deployed on browser. This enables consistent look and feel across different browser wherever Flash Player installed. Last year Flash was rejected by Apple’s for their devices and Apple started advocating open source technologies HTML5. This incident started a new thread in tech community over Flash existence.  Now again the same buzz started on Flash and its future after the Adobe’s recent announcement that they will no longer develop the Flash player for mobile browsers. In tech history there were several popular technology rolled out and rolled back depends on market movement, like JavaFX, SilverLight etc. Every technology has their lifecycle and this is manipulated by technology deviations.

Now we are entered in handheld device from desktop era. Here in this era everyone is looking for application migration for handheld devices. Here now if anything happens related to mobile or handheld devices then there is big news, but last year Adobe also stopped future development for Linux based AIR then there was silence.

Compare to Flash Player currently HTML5 is now supported on all major mobile devices. HTML5 is now a preferable technology for browser based application on mobile devices. With the latest release of Flash Player 11.1 for mobile browser Adobe will not support further for Flash player of mobile browser. This version of Flash player is still a very advance and powerful, there is still a scope of development Flash based application for mobile browser by taking advantage of new Flash Player 11.1 features.

As per market trends most of the customer want to port there application as a mobile devices apps, not as a browser based application. Here in this segment Flash is still a key player and we can port our Flash based application on Mobile device using AIR. Good news Adobe is still working on Flash Player 12 version so there is no point of worry.HTML5 is a very good technology but it still need time to fulfil the entire RIA requirement. Video/Media content delivery model is still not consistent in HTML5. Here Flash Player is best solution.

I am waiting for the day when Flash Player become an open source product and managed by some open source community. Then after we can say that we as Flash developers are using non-proprietary technology like HTML5. In this area Adobe has already taken initiative by planning to contribute the Flex SDK to an open source foundation.  This step will really give a high momentum in Flex SDK area.

Flash journey start from FutureWave to Macromedia and from Macromedia to Adobe, now Flash is ready to open source community in future. There is one thing for sure wherever Flash will go it will rock, it will not going to die soon like others.


This month Adobe gifted a new web animations tool called Edge to HTML5 world. This tool is for HTML5web designer for creating interactive graphics on website using HTML5. Currently this is a public preview release version of Edge. According to Adobe this new tool Edge will let web coders bring animation similar to that created in Flash Professional, to websites using standards like HTML5, JavaScript and CSS. The layout of this tool is like same as Adobe Flash tool. Content created with Edge is designed to work on modern browsers including those on Adobe EdgeAndroid, BlackBerry, Playbook, iOS, HP webOS, and other smartphone mobile devices as well as Firefox, Google Chrome, Safari, and Internet Explorer. Still, with HTML5 being a relatively new technology, it doesn’t today deliver a consistent experience across the widest range of devices and browsers. Adobe’s Edge is a first dedicated IDE for HTML5.

Adobe’s Edge Tool Interface Preview

Adobe’s Edge Tool interface preview

Edge Preview Highlights

This version of Edge focuses primarily on adding rich motion design to new or existing HTML projects, that runs beautifully on devices and desktops.

# Create new compositions with Edge’s drawing and text tools.
# Import popular web graphics such as SVG, PNG, JPG or GIF files.
# Easily choreograph animation with the timeline editor. Animate position, size, color, shape, rotation and more at the property level.
# Energize existing HTML files with motion, while preserving the integrity of CSS-based HTML layouts.
# Copy and paste transitions, invert them, and choose from over 25 built-in easing effects for added creativity.

Reference link for Adobe’s Edge

Adobe Lab for Edge – http://labs.adobe.com/technologies/edge/
Download Link – https://www.adobe.com/cfusion/entitlement/index.cfm?e=labs_edge
Sample file for preview – http://labs.adobe.com/technologies/edge/resources/

edge_adobe


Adobe released a preview version of interesting code free website designer tool called Muse. This tool is 100% code free, without writing a single line of code you can build your stylish and attractive website. Adobe Muse LogoThis is really interesting, I downloaded the preview version from Adobe lab and really enjoyed working on this.

Adobe already have a powerful website editor called Dreamweaver then why they introduced another one? The reason behind is Dreamweaver is for programmer to build website by writing code and this Muse is specially targeted for designer group those are very much familiar with DTP and printing software like inDesign. By using Muse designers are able to create websites as easily as creating a layout for print. Design and publish original HTML pages using the latest web standards, and without writing code.

The main feature of Adobe Muse are:
# Plan your project — Easy-to-use sitemaps, master pages, and a host of flexible, site-wide tools make it fast and intuitive to get your site planned out and ready for design.

# Design your pages — Adobe Muse is a WYSIWYG type of tool and it helps to design web pages very effectively. Combine imagery, graphics and text with complete control, flexibility and power (almost as if you were using Adobe InDesign).

# Add interactivity — Drag and drop fully customizable widgets like navigation menus and slide shows, embed HTML code snippets to include things like Google Maps, enable tool tips, rollovers and much more.

# Publish your site — Preview your site with Muse to see how it looks and test how it works. Then convert to a live website using Adobe for hosting, or export the HTML for hosting with a provider of your choice.

Adobe Muse Tool

For getting more please visit Muse official website – http://muse.adobe.com/

This tool is built by using Adobe AIR technology. If you are looking for online brochures page then this is for you but this is not accommodate complex and data interactive website. If you are a designer and want to develop attractive website in lesser time then this is for you. Lets see how this tool is welcomed by web designers.

Overall this is very interesting tool just give a try for this.


FluidHTML is a new markup language that greatly expands the application of rich media on the web. Rich Internet Applications are growing rapidly and globally. Yet the most common rich media languages are hard to learn and use and are not search engine indexable.

FHTML, Inc., was founded in March of 2009 to tackle this problem and to significantly simplify and empower development of rich media websites, content and applications for the web. FluidHtml, The Company’s product, is a new markup language that dynamically generates Flash content. Structured like HTML, FluidHtml allows any web developer to dynamically generate Rich Media sites and applications and is compatible with all major browsers. FluidHtml solves the Flash search problem by exposing the markup text to search engines. Now web publishers can combine the human appeal of rich media with all the business benefits of the web.

fluidHTML

FluidHtml has several additional important benefits. It runs in Flash, which is ubiquitous and which is consistent across all browsers. FluidHtml integrates seamlessly with server-side web technologies such as Java, .NET and PHP. And it includes a liquid layout engine with significantly more flexibility than CSS. FluidHtml markup is interpreted client-side using FHTML rendering engine. FHTML markup language is easily combined with HTML page and render on Flash based FHTML rendering engine.

flow

Benefits of FluidHTML

The use of rich media, interactive web applications, and web animations are growing dramatically, and consumer expectations of their web experience with your company are rising as a result. Historically, committing to rich website development meant using Flash, but this has significant problems for CIOs that FluidHtml solves. The main ones are these:

  • Learning curve for HTML web developer is very low
    FluidHtml is a markup language that is rendered in Flash dynamically with HTML-equivalent syntax. So, if we know HTML then we know FluidHtml. FluidHtml puts the power of Flash into the hands of your existing web developers because it follows HTML paradigms can easily be learned in a few weeks. By using our additional tags and properties, we can make applications, widgets and websites and we can mix FluidHtml and HTML on the same web page.
  • CSS3 Style Sheet Support
    Support for stylesheets in Flash is extremely limited. Typically, all style changes have to be done in ActionScript and cannot be shared with the styles on our website. FluidHtml has comprehensive stylesheet support, so now our dynamically-generated Flash applications can be styled and restyled easily. In version 2.0 of FluidHtml, our stylesheets are CSS3 compatible. So, the styles we use for HTML pages can also be used in FluidHtml to create Flash animations and layouts.
  • Liquid Layout and Data Binding
    FluidHtml supports liquid layout. This means objects can be positioned and resized relative to each other in various ways, rather than just in absolute position. Your application can easily adapt to different screens like desktop or mobile. And also support extensive Data Binding feature for components.
  • Developer friendly development approach
    No one today would code a large website in Flash because it was never built for this purpose. Flash is compiled, so each page of your site is essentially a compiled application. This isn’t true of HTML which can be dynamically generated on the server. Since FluidHtml is just markup on the page, it works like HTML. With FluidHtml you can generate Flash pages dynamically just as you do HTML.
  • Inherently Search Engine Compatible
    Flash has a difficult time with SEO. Because Flash is compiled, the search engines can’t index these binary objects. Adobe is working on making this better, but there is a natural limit to what can be done. However, FluidHtml is just markup, so it can be indexed by the search engines just like HTML. This means you can develop in FluidHtml and get all the benefits of Flash without sacrificing search engine indexability.

The upshot of all this is that with FluidHtml, your enterprise can enjoy all of the benefits of rich web deployment while dramatically reducing the total cost of development and maintenance over conventional rich media tools like Flash and Flex. And while Html5 is promising, it isn’t ready. And even when it is ready, it won’t necessarily be the right solution for multiple categories of applications

Technical specification

Programming Language: Tag based markup language FHTML+HTML. For interactivity we can use javascript and actionscript that is interpreted in Flash based FHTML interpreter.
Styling: For styling CSS2.0 and CSS3.0 (in FluidHTML v2.0)
Runtime: Flash Player 10 and above

FluidHTML Technical and Commercial Advantage
Sr. No. Advantage Parameter FHTML Advantages over HTML/FLASH
1 Technical Easy to create rich media websites, content and applications (RIAs, for short). Everyone that can code HTML should be able to build RIAs.
2 Technical Search engine optimization is available in FHTML.
3 Technical FHTML code does not need to be compiled like Flex, Silverlight and Flash.
4 Technical Learning curve for HTML developers is quick and easy.
5 Technical Text/colors/layout cans easily changes without compilation.
6 Technical FHTML content also renders on Apple product through HTML5 with inbuilt fallback mechanism after device and environment detection.
7 Commercial Reduces total cost of ownership for a business i.e. not require purchasing Flash IDE license.

 

References

Official Web page: http://www.fluidhtml.com/
About FHTML Inc.: http://www.crunchbase.com/company/fluidhtml
FAQ Page: http://www.fluidhtml.com/help/
Sotheby’s eCatalogue tool: http://www.sothebys.com/app/ecatalogue/fhtml


As a RIA specialist I have been doing client side development professionally over the last six years or so, in a variety of UI toolkits and libraries that spanned Ajax, Adobe Flex, HTML5, Swing, Applet and Silverlight. During this period I have been in touch with different RIA technology, JavaFX being one of them. Before continuing the discussion further first I would like to tell you little bit about JavaFX. The JavaFX is a rich client platform for building cross-device applications and content. Designed to enable easy development and deployment of rich internet applications (RIAs) with immersive media and content, the JavaFX platform ensures that RIAs look and behave equivalently across diverse form factors and devices. This is an innovative technology built on top of Java that allows the creation of next generation RIAs.

javafx_logo_color_1

Client side developers are always seeking for most efficient way of creating expressive RIAs. They need to build high fidelity GUIs that operates seamlessly on multiple web browsers, operating systems and devices, without having to rewrite their applications for varied environment. JavaFX promised to provide this kind of technology for end user developer, with the power of most preferable web and device technology- Java. With the advent of JavaFX it was thought that java would be one stop shop for developers.

It’s been three years since JavaFX was introduced to the world, but alas it didn’t gain a lot of momentum, though being launched at the right nick of time when the web community was moving towards RIA. It introduced a new scripting language called JavaFX Script, a very powerful language. In fact, it’s a DSL (Domain Specific Language) for creating rich user interfaces where the resulting application runs inside the Java virtual machine on the client. To my surprise when I first loaded the demos on their sites it took lot of time to load as compared to Adobe flash based application. I was hoping that being developed on Java as base technology it should have outperformed the flash based application. The benchmark on different site shows that JavaFX is by far the slowest. JavaFX APIs are not stable yet, it is not an industry standard and not many vendors are committed to it. Further, competing technology such as Adobe Flash is very popular and almost dominates the RIA domain. The key mantra of JavaFX is deployment and performance. Unfortunately, this is where JavaFX has failed miserably. The original Java applets and swing application failed miserably in deployment and JavaFX (which was supposed to be the next applet technology or applets 2.0) has inherited the failed deployment with it. In other words, nothing has really changed since 1995. This is what happens most of the time – you click on a link to launch a JavaFX application inside the browser. The browser freezes for about 5 seconds. To my woes, yesterday night while discussing about the JavaFX deployment process with one of my friend, I tried to show him the demo on JavaFX site, and the browser crashed twice. Should I blame him for this, for he was trying to click here and there while the demo was trying to load itself? I think JavaFX failed to gain any significant momentum mainly because of deployment problems which I described here. Deployment was never simple. Running an applet could freeze the browser for a few seconds, present you with a number of scary securities dialogs, and maybe even launch. If you were not that lucky, you would see the Java logo as an animated GIF. What I described above is the main reason JavaFX has failed so far. Deployment is still a disaster. If Oracle needs to know how deployment should work, it’s very easy. Just look at Adobe Flash. Make it as simple and transparent as running a Flash application. That’s it.

Some people say they don’t like JavaFX because they need to learn a new language. Well that’s just a bunch of hot air. First of all, any decent Java developer can pick up JavaFX Script in about 2 days. If you are developer (any kind) today, you have to learn new stuff all the time.

After acquisition of Sun Microsystem by Oracle, the roadmap or vision of JavaFX is changed. As everyone knows by now, Oracle is making significant changes to JavaFX. Oracle is stopping any further development of JavaFX Script. Instead, it will develop Java APIs which will become a part of JavaFX 2.0 to be released in the second half of 2011. So, instead of using JavaFX Script to develop rich Java applications, you will use the new Java API. There is still time to make JavaFX successful, but the time is running out. First, fix the deployment issue need to be addressed. Just start from scratch, don’t try to fix the current deployment system. Second, if Oracle doesn’t want or need JavaFX, then open source it and let the community drive its future. I think Oracle has 6-12 months at the most to try and revive JavaFX. If nothing happens by then (which would be about 4 years since the technology was announced), we just might as well close the door on JavaFX. Now market trends driven towards open ended technology like HTML5, people are not ready to depend on any third party proprietary technology. As the history suggests Java popularised for being cross-device technology. So for me JavaFX still have a market in device development segment. If they fix the performance and deployment issue ASAP.

Now Shipping: Flash Media Playback

Posted: August 30, 2010 in Adobe, Media
Tags: , ,

Flash Media Playback is a brand new free media player for Flash that makes it much easier to deliver high quality video the widest possible audience using Adobe Flash Player. Flash Media Playback has been designed to make it super simple to deploy video in no time at all with full support for all the delivery technologies including RTMP/RTMPe HTTP Dynamic Streaming and Progressive Download. All you need to do to use it is add some simple HTML to your webpages – The actual SWF file will come from Adobe.

Flash Media Playback is built on top of the Open Source Media Framework and as part of that framework has full support for all of the third party plugin services from key service providers supporting the framework. Service providers such as CMS, CDNS, Advertising and Analytics that help you drive a business delivering video on the web.

Using the Flash Media Playback video player

To incorporate the Flash Media Playback video player into your web page, simply add the player embed code to the HTML page. When visitors load the web page in a browser, FMP is automatically displayed with your video playing on the page.

Flash Media Playback Setup page

To copy the embed code, visit the Flash Media Playback Setup page at osmf.org/configurator/fmp/. The Flash Media Playback Setup page (see Figure 1) contains two main sections on the left and the right. Use the form on the left to enter the values for your video: video source location and various custom settings. The right side of the page contains a preview player and the preview embed code. Enter the values and then click Preview to generate the proper embed code.

fig01

Here are some important links to get started and learn more

The Flash Media Playback product pages:
http://www.adobe.com/products/flashmediaplayback/


The OSMF product page including Strobe Media Playback:
http://www.osmf.org/strobe_mediaplayback.html


Developer Center Articles for getting started
http://www.adobe.com/devnet/video/articles/fmp_player.html

Get started today, and keep creating great looking video experiences!