Adobe Flex Intro PPT posted

A couple of weekends ago, I did a presentation for The Chennai Cold Fusion User Group (CCFUG Homepage). Am posting the ppt here. The presentation covered the basics – intro to RIAs, intro to Adobe Flex, a couple of examples and a little bit about Adobe AIR. Check it out… if you have nothing else to do ๐Ÿ˜‰ … The audience were cold fusion developers who were new to Adobe Flex and Adoe AIR. I touched the basics and then walked them through some code examples of Flex and Air.

Check out some snaps from the event and check out this post by Akbar after the event. You may also want to check out the CCFUG homepage at

Silverlight, Sparkle and Flex

First it was Sparkle and now the new babe in the block is Sliverlight. A month ago, I saw a video covering the Sparkle developers showcasing some pretty cool stuff about Sparkle. Ok. So, I am not one of those bunch who hate anything that comes out of Microsoft because it comes out of Microsoft. The way I see it, this is how it all maps –

  • Sparkle (XAML) = Flex (MXML)
  • Flash Player = Silverlight

There seems to be some really uncanny similarities between XAML and MXML… (Of course they are both XML!). Check it out. The graphics that these bunch of Latin-Greek-Hieroglyphs churn up are pretty good.

<Canvas xmlns=”; xmlns:x=”; x:Name=”_119_red_scanlione_gloss” Width=”1056″ Height=”816″> <Canvas x:Name=”Layer_1″> <Rectangle x:Name=”Rectangle” Canvas.Left=”0″ Canvas.Top=”0″ Width=”1056″ Height=”816″ Stretch=”Fill” Fill=”#FFFF0000″/> <Path x:Name=”Path” Canvas.Left=”404.558″ Canvas.Top=”258.867″ Width=”258.844″ Height=”258.844″ Stretch=”Fill” Fill=”#FFFFFFFF” Data=”F1 M 411.029,258.867L 656.931,258.867C 660.505,258.867 663.402,261.764 663.402,265.338L 663.402,511.24C 663.402,514.814 660.505,517.711 656.931,517.711L 411.029,517.711C 407.455,517.711 404.558,514.814 404.558,511.24L 404.558,265.338C 404.558,261.764 407.455,258.867 411.029,258.867 Z “/> <Rectangle x:Name=”Rectangle_0″ Canvas.Left=”0″ Canvas.Top=”0″ Width=”1056″ Height=”816″ Stretch=”Fill”> <Rectangle.Fill>

I really don’t think Sparkle or Silverlight is a threat to Flex or Flash Player. But, I definitely think here begins a competition. With Apollo, Adobe definitely has a head start over any new web 2.0 stuff. Lets not forget that Flash Player is what? 10+ years older than anything that will be born 2 years from now ๐Ÿ˜€ . As they say, we ARE living in interesting times!!! Definitely, we are!

Honestly, I think everyone has to learn from Microsoft to create such lovely sexy logos! It doesn’t make any sense. But, then who cares? Its a damn Logo and it looks great! ๐Ÿ˜‰

Silverlight samples – Pretty Impressive! (You will need to install Silverlight for this)


Yipppppeeee!!!! Apollo Alpha is out!

Wow!! Am I excited….. I just got a mail from Adobe saying Apollo Alpha is available for download. ๐Ÿ™‚ I am just downloading it. Too excited to writing anything more! ๐Ÿ™‚ Lemme try it now!!

Apollo nearing launch

Here’s a list 15 facts about apollo from the flex blogosphere ๐Ÿ˜‰

So, by way of a follow-up to an earlier post: โ€œAdobe Apollo nearing launchโ€, here’s a list of 15 things about Adobe Apollo:

  1. The ability to install web applications as desktop applications. So the web applications exist outside of the browser and are browser independent.
  2. Applications that work out of Apollo don’t have to be connected to the internet to function.
  3. In addition, Apollo applications can have access to your files and your network.
  4. Real time notifications can be sent via the Apollo framework.
  5. Adobe’s PDF file format is a peer format, which is of huge strategic significance.
  6. Apollo will work on Mac and Windows to begin with, Linux support to follow.
  7. Because of the technologies underpinning Apollo, the emphasis is clearly on ‘mashups’, which web applications created from loosely coupled APIs belonging to other web applications.An example given was a media player that made use of the Amazon API to pull down music artwork and a visualize that made use of Flickr images.
  8. Although the guy from Adobe, chief software architect Kevin Lynch, tried to play down the significance of Apollo and the fact that Apollo is Adobe playing Microsoft at their own game, Apollo is as significant a strategy that Adobe could hope to conceive.A strategy that will no doubt come under immense scrutiny over the next near, not least scrutinized by Microsoft’s own web strategy people.
  9. Apollo uses the WebKit web rendering engine built into Apple’s Safari web browser and the Nokia S60 platform.
  10. Over time, Adobe hope to bring JavaScript, ActionScript (a derivative of EMCA script, which is essentially JavaScript, but used inside Adobe Flash) and the JavaScript used within the WebKit, into ‘one VM’ or Virtual Machine, which is a piece of software that executes code and reinterprets into another language more ‘native’ to the device, in this case, the computer.
  11. Whereas it’s clear that Microsoft aren’t all that bothered about customers running older platforms, Adobe’s Apollo will be more compatible with Windows than, err .. Windows! Essentially, pre Vista and pre XP computers will be supported.Again, this is because of the totally open nature of the technologies that underpin Apollo and allow for compatibility with a huge swathe of differing versions of operating systems.
  12. While this wasn’t directly mentioned in the Podcast, what Adobe are working towards with Apollo is something that one could imagine giving birth to the Widgets used in Apple’s Dashboard.It’s clear that Apple have their own ideas about how a Widget ought to take shape. What with Apple looking to release Dashcode, which is IDE (Integrated Development Environment) for developing Widgets used in Dashboard.However, I wouldn’t be at all surprised if both Apple and Google didn’t get their heads together on this issue and work with either Adobe or OpenLaszlo (an open source framework of similar intention and purpose as Apollo) to help establish a standard practice.Meanwhile, the World Wide Web Consortium have moved to establish the Widgets 1.0 Working Draft:

โ€œThe type of widgets that are addressed by this document are usually small client-side applications for displaying and updating remote data, packaged in a way to allow a single download and installation on a client machine. The widget may execute outside of the typical web browser interface. Examples include clocks, stock tickers, news casters, games and weather forecasters. Some existing industry solutions go by the names ‘widgets’, ‘gadgets’ or ‘modules’.โ€

However, when asked about how similar Apollo applications sound to Apple’s Dashboard Widgets, Kevin Lynch confessed that he hadn’t given the idea much thought.

I’m not going to speculate on whether he had or he hadn’t, but he didn’t dismiss the ability of Apollo of being able to produce such things.

Indeed, Apple’s own Widgets are built around exactly the same open standards and technologies as both Apollo and OpenLaszlo.

  • Adobe will make the ‘runtime’ player for Apollo free, much like the Flash player is free. However, the revenue will come from the expected increase in sale of their web development applications, such as DreamWeaver and Flash.
  • While it’s possible for people to develop a whole range of things with Apollo, Adobe don’t want to build too much into Apollo, such as Adobe Reader, which would make Apollo too heavy and not ‘light weight’, which is their specific goal.
  • A public developer release of Apollo will take place some time in 2007, but no fixed, specific date was given.
  • In conclusion

    Personally, I’d think Apollo is big. I’d also say that it’s the logical direction forward.

    What I don’t want to see is Microsoft succeed here, because they will drag the whole thing towards their proprietary hooks & barbs, entangling a really powerful platform of the future on an idea based around a business model of the pastโ€ฆ

    [

    Apollo to use WebKit(Safari) HTML engine

    It’s now official. Apollo will use the Webkit HTML engine for supporting HTML/AJAX based applications.

    WebKit is an open source web browser engine. WebKit is also the name of the Mac OS X system framework version of the engine that’s used by Safari, Dashboard, Mail, and many other OS X applications.

    [