Comments on: Component-Based Applications http://rewindlife.com/2003/09/18/component-based-applications/ Technical discussion of Flex, Flash, and RIA development Sun, 05 Feb 2012 05:54:45 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: g2u http://rewindlife.com/2003/09/18/component-based-applications/comment-page-1/#comment-283 g2u Wed, 21 Jan 2004 15:03:22 +0000 http://rewindlife.com/?p=82#comment-283 I loved reading this great blog. Thanks. I loved reading this great blog. Thanks.

]]> By: Scott Barnes http://rewindlife.com/2003/09/18/component-based-applications/comment-page-1/#comment-282 Scott Barnes Fri, 19 Sep 2003 02:31:10 +0000 http://rewindlife.com/?p=82#comment-282 Well said man, Been waiting for an article like this to illustrate the gr00vyness of components. Good read indeed. Well said man,

Been waiting for an article like this to illustrate the gr00vyness of components.

Good read indeed.

]]> By: Chafic Kazoun http://rewindlife.com/2003/09/18/component-based-applications/comment-page-1/#comment-281 Chafic Kazoun Fri, 19 Sep 2003 00:56:40 +0000 http://rewindlife.com/?p=82#comment-281 I like it Phil. That is for sure a big part of components. To add, I think another is distribution and versioning. If I purchase a component from a 3rd party, it’s not difficult to update it down the line if the 3rd party makes an update available. That is part of the theory behind components, at least for me. I like it Phil. That is for sure a big part of components. To add, I think another is distribution and versioning. If I purchase a component from a 3rd party, it’s not difficult to update it down the line if the 3rd party makes an update available. That is part of the theory behind components, at least for me.

]]> By: Chafic Kazoun http://rewindlife.com/2003/09/18/component-based-applications/comment-page-1/#comment-280 Chafic Kazoun Fri, 19 Sep 2003 00:51:18 +0000 http://rewindlife.com/?p=82#comment-280 Yeah, I guess the best thing about components is the fact that they promote you not to mess with them. Interfaces are definitely a good addition and I'm looking forward to seing them applied in Flash Applications. There still is a long way to go, but I believe we are headed in that direction. It definitely is exciting Nice entry btw on your blog Owen. Yeah, I guess the best thing about components is the fact that they promote you not to mess with them. Interfaces are definitely a good addition and I’m looking forward to seing them applied in Flash Applications. There still is a long way to go, but I believe we are headed in that direction. It definitely is exciting

Nice entry btw on your blog Owen.

]]> By: Philter http://rewindlife.com/2003/09/18/component-based-applications/comment-page-1/#comment-279 Philter Fri, 19 Sep 2003 00:45:44 +0000 http://rewindlife.com/?p=82#comment-279 The way i look at it, it seems that classes encapsulate more often than not, a single piece of functionality. Components bring several of these individually functional pieces together to build something on a little more of a "macroscopic" level. However, even though the component is using several classes, each with different pieces of functionality, the component itself still has one overarching function to it. What do you think? Owen, Can you elaborate on your comment "there are some serious issues about deployment and development of SWC files"? I would like to know specifically what you are referring to. Phil The way i look at it, it seems that classes encapsulate more often than not, a single piece of functionality. Components bring several of these individually functional pieces together to build something on a little more of a “macroscopic” level. However, even though the component is using several classes, each with different pieces of functionality, the component itself still has one overarching function to it. What do you think?

Owen,

Can you elaborate on your comment “there are some serious issues about deployment and development of SWC files”? I would like to know specifically what you are referring to.

Phil

]]> By: Owen van Dijk http://rewindlife.com/2003/09/18/component-based-applications/comment-page-1/#comment-278 Owen van Dijk Fri, 19 Sep 2003 00:16:22 +0000 http://rewindlife.com/?p=82#comment-278 Interesting read. Some comments, you are referring to inheritance as reusing code, and you are also mentioning one of the problems, that is "subclassing" a class to suit your specific need. Inheritance is mainly more about specifying an "IS-A" relationship between objects, not about reusing objects behavior. The more obvious problem is that you are strong coupling your objects together, like a chain with a weakest link. The introduction of Interfaces in Flash MX 2004 pro might be the start for developers thinking more and more about interface inheritance than about implementation inheritance. About components, you basically described the workflow of many VB and Delphi developers and FormBased development. That is exactly what i mean in my posting "The future of Flash ( pt1. Runtime Model )" ( see last alinea ). Also EJB is coming close to a runtime component model, not to forget CORBA and COM(+). There is alot of similarities to Flash RIA development, and i wondered why the Flash Community didn't pick this up. Again, Ted has been doing great stuff with PowerSDK, and his framework really should deserve some more attention. About the implementation of Components and workflow in Flash MX 2004, there are some serious issues about deployment and development of SWC files, and i wouldn't recommend them at all for using them as an equivalent of a .NET Component ( Assembly, DLL ) or an Java Enterprise Bean. Interesting read. Some comments, you are referring to inheritance as reusing code, and you are also mentioning one of the problems, that is “subclassing” a class to suit your specific need. Inheritance is mainly more about specifying an “IS-A” relationship between objects, not about reusing objects behavior. The more obvious problem is that you are strong coupling your objects together, like a chain with a weakest link. The introduction of Interfaces in Flash MX 2004 pro might be the start for developers thinking more and more about interface inheritance than about implementation inheritance.

About components, you basically described the workflow of many VB and Delphi developers and FormBased development. That is exactly what i mean in my posting “The future of Flash ( pt1. Runtime Model )” ( see last alinea ). Also EJB is coming close to a runtime component model, not to forget CORBA and COM(+). There is alot of similarities to Flash RIA development, and i wondered why the Flash Community didn’t pick this up. Again, Ted has been doing great stuff with PowerSDK, and his framework really should deserve some more attention.

About the implementation of Components and workflow in Flash MX 2004, there are some serious issues about deployment and development of SWC files, and i wouldn’t recommend them at all for using them as an equivalent of a .NET Component ( Assembly, DLL ) or an Java Enterprise Bean.

]]>