| By Jesse Randall Warden | Article Rating: |
|
| April 7, 2004 12:00 AM EDT | Reads: |
15,201 |
Central is important to developers for a number of reasons. First, Central provides an application framework with which you can sell the applications you make. You just have to add a few purchasing details to an XML file and edit a Web form. Additionally, the user is presented with information about how to purchase. Considering Macromedia's current deals with companies such as Intel and AOL, you can be sure that your applications will get exposure.
The evolving Flash Player will do better on the desktop than within the browser. There are fewer restrictions and a lot more room to add features and internal APIs developers may want or need. The politics of ubiquity rule the overarching plan of the Flash Player's development in a Web environment; you don't have those restrictions with Central.
Central makes deployment scenarios much easier. With Central's built-in App Finder and Free Finder applications, users are more likely to find your applications. Additionally, you know exactly what technology your end user has; currently Flash Player 6.0.65.0. There are no diversions from these specs, the only difference is OS. It's nice to have such assurances in development, as any developer knows.
But to really understand what Central means to us, we have to look at the history of where Central came from, including the problems Flash application developers have had in the past, as well as where we're going.
For an application developer, the browser is pretty lame. If you look at the history, starting with when the Web hit, a lot of application developers turned into Web application developers. Whether it was for back-end ASP/PHP/JSP coding, Java applications (and all the flavors), or copious amounts of JavaScript/DHTML, application programmers had a new playing field with many avenues to explore and a lot of uncharted territory.
In the multimedia realm, the CD-ROM revolution made us aware of what was truly possible using all of the media disciplines (design, audio, video, programming) together to create unique and powerful interactive media. The push for the Web wasn't as easy, mainly because of bandwidth.
Even so, there was still a lot of interactive, offline work that application developers could do utilizing a lot of artistic media. Whether the range was a simple, interactive brochure for a kiosk, or a full-blown interactive application that may even have had Internet connectivity, Director was one of the few authoring programs that allowed you to merge the best that media could offer. However, as companies desired easier exposure to their customers (but with all the functionality) the plug-in wars got pretty harsh. Basic rights were violated, and IT tightened the noose of security - and for good reason. This made a lot of technologies inaccessible to a lot of people.
Enter Flash - this plug-in is everywhere. It is a cross-platform, lightweight media tool with which many people can view and experience whatever the creators make. You can create animations as well as applications on the same plug-in. Although Director has a great plug-in, even as a developer, I've had a lot of trouble getting it to work on anything even remotely associated with a firewall. Call it user error, but I haven't been able to get it to work easily - who's at fault doesn't matter. Flash, on the other hand, is very easy to install, and in many cases is already installed. This ease of proliferation has enabled a vast amount of the connected world to view Flash content.
Flash has been capable of connecting to outside data sources via GET/POST operations since Flash 4 and via XML and XMLSocket since Flash 5. With Flash 6 came Flash Remoting as well as the Flash Communication Server, built-in Central installation functionality, Web service code modules packaged with Flash MX 2004, and dynamic sound and video, all with the same real-time pixel-to-vector engine that can scale your content, and all running in a secure sandbox. From a multimedia standpoint, whether for creating rich media ads or Web applications, Flash is the way to go.
But Flash can't go much further in its current environment. Considering all the factors working against innovation in the IE browser market, Microsoft's attitudes toward browsers and browser applications in general, and the challenges of integrating with a new barrage of browsers, the Flash Player has many challenges to overcome. Challenges like allowing Flash to easily respond to "next" and "back" navigation, in all versions of IE that are realistic (and who determines this?), as well as Mozilla and friends, and the *nix flavors.
It's really about attitudes. Microsoft dropped development of IE for many reasons, but look where they're headed. Their prominent emphasis in Longhorn, and its development platform Avalon, is to create Web-connected applications that can be occasionally connected. This applies to laptops and devices such as PDAs and phones. There was a time when the push for win32 and Web applications as two product offerings was key to success and survival in technology. Studies show that a large portion (80% in some cases, but I never trust statistics) of Internet users utilize that connection without a browser. Applications that are connected have a lot more freedom outside the browser, not just in functionality, but in room to grow and adapt. Microsoft's enhancing their OS and allowing applications to access that rich GUI, as well as the classes they used to create it, opens a lot of doors for developers wishing to get into the rich GUI market. Flash, as its current IDE stands, is somewhat challenging to existing developers. The flair that Flash can offer, as well as its integration into disparate systems, makes it ideal for putting a nice face on applications - the issue lies in getting comfortable. The advent of Flex from Macromedia will definitely open the doors for enterprise application developers. Interestingly, I've read reports that a lot of smaller-time application developers feel they too would like the workflow of Flex. From how the initial offerings work, the Microsoft XML format and Macromedia's looked exactly the same in my eyes; one simply used ActionScript where code needed to be written, while the other used C#. Even the syntaxes were amazingly similar.
Macromedia, too, realizes that if they want to offer more benefits to developers, they cannot unnecessarily bloat the Flash Player with features comparable to Microsoft's current Smart Client. From a developer standpoint, one of the great successes of the Flash Player was its proliferation to a lot of platforms and devices because of its small file size and lightweight implementation. Additionally, it's getting harder and harder to support each and every browser intricacy and still have the player operate and function the same on each platform without spending unrealistic development time or unnecessarily bloating the Flash Player to deal with these various discrepancies.
This is where Central comes in. The OS is our playing field now, instead of the browser. And by being freed of the chains of functionality and file-size restraints while retaining a secure sandbox, it has room to grow where we want it to. In contrast, because of the mess created on the Web by the lack of standards and the lack of applications following those standards, people have learned and have started following standards, which doesn't leave a lot of growing room. Going against the grain to push the envelope of design and media is now Okay only if you validate - lame.
My subjectivity is born of the fact that, during college, I chose the Director application route over Web design, merely because there weren't a lot of rules I had to follow. As long as we didn't crash your computer, the playing field for the team of designers I worked with was wide open. This allowed for a great number of custom-built solutions and great flexibility and creativity. Flash initially offered this on the Web, but as more functionality is needed from a programming standpoint, it's hard to deliver much without stepping on some file-size or nonubiquitous toes. The Flash Player on the Web has reached its breaking point in terms of what we can add without significant tradeoffs. Flash, already maturing into a really great development platform, saw the rise of some third-party applications to extend Flash where it was lacking in the desktop environment. Screenweaver, SWF Studio, etc., all offer ways to easily give Flash functionality that the player was lacking, such as reading the local hard drive and saving a text file, as well as additional APIs, some custom created by developers. As most of my work was in the application arena as opposed to Web, these programs were, and still are, invaluable.
This isn't saying Web applications are bad or are going away. Rich GUI applications that people can use from anywhere with a Web browser and an Internet connection is a powerful concept. However, for people like me, who don't like dealing with browsers and all the fun little problems that Web developers and designers deal with day in and day out, a set platform is required. If you're a .NET developer, you get the .NET Framework; they also have one for devices. This is extremely cool for .NET developers, but what do Flash developers get? Originally, the same player with minor security restrictions freed. If you wanted functionality similar to what desktop apps had, you had to use a third-party application or Director. Now, we have Central. Just like some .NET apps, it has one-click installation. It also has built-in UI controls and a plethora of built-in APIs not offered in the Flash Web Player.
It's important to focus on where we're going, not where we are. Central, in its initial incarnation, is strictly for developers to get comfortable developing in it, as well as to provide Macromedia with the feedback it needs to better morph Central in a direction that is somewhat congruent with our Flash application development needs. We Flash developers now have a platform that has more potential for growth and the ability to adapt to our needs more easily and quickly. Not only that, but users can be upgraded more easily along with the applications that we deploy to them. Think of Flash with hardware acceleration and easier access to OS-integrated features. These are all possibilities depending on community need.
The really good stuff is yet to come. Once Macromedia starts marketing Central to the user base, packages it to places of great exposure (crossing fingers), and implements the AOL IM API (as well as related packages such as ICQ) along with some of the Breeze Live APIs for pods, Central will be a seductive platform to not only develop to, but also to sell applications on.
Published April 7, 2004 Reads 15,201
Copyright © 2004 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
About Jesse Randall Warden
Jesse R. Warden, a member of the Editorial Board of Web Developer's & Designer's Journal, is a Flex, Flash and Flash Lite consultant for Universal Mind. A professional multimedia developer, he maintains a Website at jessewarden.com where he writes about technical topics that relate to Flash and Flex.
![]() |
web_dev 05/07/04 03:45:23 PM EDT | |||
First and foremost, congrats to everyone in here remaining professional. People made great comments and I see and clearly understand all of your points. Thanks for letting me express my opinion without getting out of hand as many do on boards like this. Your article did drive me to think which is always fun, and I am back again!! So in that respect, your article was quite a success. Flash is revolutionary, yes, agreed. Constatly worrying about different browsers is a pain, agreed again. I am not a server dude at all. I can run them and configure them but my specialty is DHTML, CF, Java, MS SQL and Flash. My point is that clients come and go like trains. The concept of the Web Server, running centralized code over the internet is what makes this type of programming great. This is also what makes it better than client programming. I do not see a difference between the two as far as fucntionality goes. Any application that just simply moves data from point A to point B can be done with a web app. There are 1000''s of client apps out there that have designed soley for this purpose and it just does not make sense to me. Now if you are talking about an application like Fireworks for example, that is a very different story. That has proper justification to be created as a client application in my book, but it is doing more than just operating on some text, then storing it. I have not seen the Flash MX 2004 article and that is not the one that I am talking about. I was talking about a CF article posted in the CFMX Developer Journal. If all you did in your article was put a piece of text on the stage that says Hello World, then run it, then yes I would have been dissapointed. But Flash is changing dramaticly with every release, especially in the past year or two. The code syntax changes alot and major components are added. If it were a Hello World example that was delivered through a web service that would be a little more along the lines of what I would expect from a developer journal. The CF article I mentioned was not covering anything new to CFMX. Anyone who has used CF in the past 5 years should be able to do that the same way they always have. And as for writing my own article.... Only if I am getting paid! lol But I do have a suggestion if someone wants to cover it. Lets say I have 33 million rows in a database, say ORACLE version 8.71. Now lets say I write a select statement that selects about 25,000 of those rows. On the first search results page, I want to show the first 100 rows, yet still have a full record count. I dont want to bring all 25,000 rows back to the CF Server every time I go to the Next Page >>. I want it to be fast and effeciant. Much like google does, or used to do. Those guys win the blue ribbon in my opinion. They used to show a string like this. Now viewing the first 25 results from 1,300,598 records found out of 13,004,001,234 total pages searched in .13 seconds. Now that is impressive! I would like to try to do this without platform specific SQL or Stored procedures. Because next week I will need to do the same thing using MS SQL 2000. |
||||
![]() |
Owen van Dijk 04/10/04 02:21:55 PM EDT | |||
Hey, i had a "Hello World" example in my article named "The Flash MX 2004 Professional Data Architecture" published in November 2003. How cool is that to read from people like "web_dev" that it''s intended audience is amateurs, instead of professionals. Especially if i got feedback from seasoned developers in our community how my article helped them getting started. I think people like "web_dev" should put your money where your mouth is, and write an article and put it on the web or publish it in a magazine, or start a weblog where you can post your comments. Btw, if you''re not talking about my article, then i would like to know which one you mean, unfortunately i''m not subscribed to this magazine. :) |
||||
![]() |
JesterXL 04/09/04 03:31:10 PM EDT | |||
It is biased, yes. I''m biased towards Central; I want Flash Developers to find value in it. If DHTML developers find value in it, or at least question more to find out more about Central, then that''s cool too. I''m not sure which were half-truths, and which were not...? I''m idealist, so yes, it is wishful-thinking because I think a lot of what I say will come to fruition in a good way. I know squat about DHTML and it''s ability to work in the browser. I''ve coded like a few moving DIV''s, and that''s about it, so if what you say is factual, then cool. However, I disagree with Win/IE being able to do anything Flash can do; that''s a little broad. I''m not sure how having paying Flash jobs adds credence to what you say, though. There are a bunch of ways one can use Flash, but the fact you used Flash is cool. |
||||
![]() |
Christian 04/09/04 03:22:20 PM EDT | |||
I feel your article is biased and evangelistic. I agree a lot with the first feedback post. Your article is full of half-truths and wishful thinking. The half-truths relate to MSIE. MS Win/IE is equipped with excellent DHTML support(albeit proprietary to Win platform). Anything Flash or Swing can do so can Win/IE. Data retrieval can be done in the background with XMLHTTP. JavaScript can be abstracted using Behaviors. Just look what the crew at oddpost did. The cross platform argument is a perceived advantage -- in the real world 95% of businesses in North America use Windows. Putting Win/IE aside -- in general DHTML is a much more formidable foe in the RIA space than 2 or 3 years ago(every since Netscape 4.7 fazed out). Writing cross-platform DHTML is much faster due to browser maturity. Flash''s big problem is that JavaScript/DHTML/CSS/XHTML web apps are good enough(usability wise) and are fast to develop. I must add that I had two paying "Flash" jobs between 1999 and 2001. |
||||
![]() |
Jesse 04/09/04 12:53:40 PM EDT | |||
Thanks for your feedback! You make a lot of points, and I''m still digesting it all, but figured I''d see if I could help relay some things I said in a different way. I usually write a lot more than is necessarey to get a point across merely to make sure I''ve covered all angles. Sometimes, that''s not enough. To me, the ability to manage a desktop application in Central is made easy, 1000 or more. I have 2 assurances: Every single one of them is using Flash Player 6.0.65.0 and they are using Version X. If I choose to have them upgrade, I know that they have, and what version of my app they are running. What the web doesn''t give me is this platform version assurance. I have issues all the time with Mac/safari/fire...fox/etc. users not seeing the content the way I intended, as well as working the way I inteded. Central, at least, gives me this piece of mind. That could be the lack of my web design, skill, though. However, I''d rather be spending my time building an app rather than making sure it runs correctly. Competeting with IE is what I meant to convey. Rather, Central provides an alternative for Flash developers to deploy to, just as SmartClient is an alternative for .NET developers. This doesn''t lessen the importance of IE as a viable platform in any way. Your not getting an understanding from my article about what Central is very understandable; many people are reporting that they really don''t understand what Central really is, even after reading multiple marketing articles, targeted at developers and those that aren''t. Even Flash Develoepers, who''ve read both, are still unconvinced to even spend time on it. The above is my attempt to convey the value that I see, personally, in Central. I encourage you to do more research on it and not take my article as the end all, be all description of it. I did, however, correctly convey to you my dislike of the web vs. desktop apps; score a point for that message being conveyed correctly! You sound like a server-dude; because to me, a web app is not the same in effectiveness, and definately not in goals as a desktop app. I think they are different worlds, with a lot of similiarities. The reason I make the generalization about you is, as a user and developer, I care little for the server; what gives me value from the web is the browser and apps/content I use/read within it. I could care less if the server is Linux/Unix/Solaris/NT/Mac/what have you. None of them, in my eyes, directly rely more or less value of the web too me. My writing does tend to beat to a different drum, I''ll admit that. Keep in mind this article is an editorial, meant to be my opinion, and not to tackle any technical problem. The topic of conveying the value of Central to developers goes beyond solving just one problem, but rather a plethora of them. I''m not mad, and I don''t think the above is a flame. I talk a lot too... too much. If I got you to think, then I feel like I accomplished something. |
||||
![]() |
web dev 04/09/04 10:09:10 AM EDT | |||
I think the author of this article is missing the point of the web in general, especially with how it relates to desktop applications. One great point that was missed is code manageablilty. Desktop applications have to be updated through very tedious means especially when dealing with 1000''s of users. Things like SMS, issuances and other push technologies just can''t justify themselves when the exact same app can be created on the web and managed from a central location. Most companies have chosen IE as the platform that is to be supported. There are no worries about which platform, its microsoft Windows 2000 and XP. People make such a big deal out of the other platforms when there really are none. Those UNIX users are not using UNIX on a daily basis. They are telneting into a UNIX box from a MS windows machine. They have IE and if they expect to work for anyone of these companies then they will need to use IE rather than lynx on UNIX. Same goes for Mac users. IE is not un-standardized, neither is the web. There are just alot of people out there with bad ideas, ideas like trying to copmpete with Microsoft IE. IE is not hard to program for either. It is quite elegant and I can create a UI that is equally as compelling as any opther programming language out there, web based, CD-ROM based, Flash based, Desktop based or otherwise. I realize that your trying to write an article on a new product or service, so your trying to bring up points that make it sound good. This Central thing, whatever that is. I read your whole article and I still have no idea what it is or what it can do for me. All I hear is you complaining about how the web sucks and how desktop apps rule. A desktop based flash application is effective for the same reasons that the web is effective, which is the whole point that was missed just so you could sell your product. It''s really the concept of a web server that makes the web what it is not the web browser and definalty not Flash. Very strange writing, which I have come to expect from MX dev journal. Kinda like the Hello World article that was posted a few months ago in this magazine. Im sorry but I thought that developer journals were for professionals, to discuss real topics and give answers to problems in the real world. The Hello world example is for ametuers, not seasoned professionals. The more I read the more I believe that this magazine is merely a sales tool. Not a developer journal. Don''t get mad and flame me, I just talk alot, I still have the subscription and will wait for it to get better because I love Macromedia. This is just me thinking out loud, use it as a piece of mind and move on with your life. |
||||
- AJAX World RIA Conference & Expo Kicks Off in New York City
- Java Kicks Ruby on Rails in the Butt
- Ulitzer’s Amazing First 30 Days in Public Beta
- "Government IT Expo" to Highlight Cloud Computing and SOA
- Will Ulitzer Dominate News Content on The Web? -Gartner
- Clear Toolkit 4: The Road Map
- Creating Adobe AIR Native Menu with Flash CS4
- Menu Interaction in Adobe AIR
- The Darker Sides Of Cloud Computing: Security and Availability
- Ulitzer vs. Ning - a Quick Review
- AJAX World RIA Conference & Expo Kicks Off in New York City
- Creating PDF Documents from Flex Applications
- Java Kicks Ruby on Rails in the Butt
- WebORB Launched for Flex, Flash, AJAX and Silverlight
- Adobe Takes LiveCycle into the Cloud
- Ulitzer’s Amazing First 30 Days in Public Beta
- Adobe Creates a Sandbox in the Sky
- AJAX and RIA Market Is Heating Up: Sun CEO
- "Government IT Expo" to Highlight Cloud Computing and SOA
- Will Ulitzer Dominate News Content on The Web? -Gartner
- Cover Story: How to Increase the Frame Rates of Your Flash Movies
- AJAX World RIA Conference & Expo Kicks Off in New York City
- Your First Adobe Flex Application with a ColdFusion Backend
- Adobe Flex 2: Advanced DataGrid
- Adobe/Macromedia - Microsoft, Look Out!
- i-Technology Blog: Death-Knell For "Rich Media? Hardly!
- Adobe Flex Interface Customization - Themes, Styles, Skins
- Personal Branding Checklist
- How To Create a Photo Slide Show ...
- "Real-World Flex" by Adobe's Christophe Coenraets







































