Mailing List
Home
Forum Home
Flash Pro
Subjects
Firework Effect
setInterval bug identified and fixed
setInterval bug identified and fixed
ScrollPane component doesn 't auto update
Help: MX 2004 How to script a print button to print the entire sli
Event Dispatcher between classes
memory management removeMovieClip /
MX2004 Dataset itemClassName
Order of events per frame
XML to Object help
Textfield prototype question
Flash and QuickTime VR
Reading and displaying RSS feeds in Flash MX
Flash MX 2004 Sucks
AW: [Flashcoders] Switch/Case vs If/else
AW: [Flashcoders] Switch/Case vs If/else
Flash Interface with 10mb xml file
Web Service Results
Listener Object 's best practice
 
RFC: Component Frameworks Chapter

RFC: Component Frameworks Chapter

2004-02-28       - By Giacomo Guilizzoni

 Back
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

Hi there.

I'm writing my third chapter for what's now known as the "Brian Lesser
O'Reilly Flashcom Book" ;), and this one is on "the Macromedia Component
Framework and Component Frameworks in general".

I have written about 50% of it, but before I go on I would like to make sure
that my chapter will be as useful to you guys as possible, hence this email.

Basically what I'm looking for is:
-what's the one thing you would like me to cover?
-what's the most confusing thing about the Macromedia Component Framework?
-why do you use it, why don't you?
-have you built a client-server component framework yourself? If so, what
were the lessons you learned that you would like me to share with the world?
;)

Basically my spin on the chapter is this: talk about client-server component
frameworks in general, and use the macromedia component framework as the
primary example for each section (and yes, I will discuss its shortcomings).

Here's the TOC for the chapter so far (obviously not final):
-Introduction
-What is a framework?
-A Component Framework's Goals
  -A good framework is solid
  -A good framework is light-weight
  -A framework's main purpose is to allow OOP
  -The APIs are "just right"
  -Other goals
-A Component Framework's Building Blocks
  -A global singleton on each side that's always running
  -Name-space isolation
  -Component registration
  -Component creation and destruction
  -Method routing
  -Component data management
  -Component interaction (event mechanism)
  -Component base classes
  -The components themselves: client-side and server-side
  -Access control (read/write)
  -Security
  -Others
-Client-Side APIs
  -connect
  -close
  -setSize
  -setRole
  -...
-Server-Side APIs
  -connect
  -onAppStart
  -onConnect
  -onDisconnect
  -onnAppStop
  -destroy
  -...
-Using the MM components in your applications
-Extending the components provided with flashcom
-Sample: Creating a new component from scratch
-Sample: An authenticating component

I have looked at the archives and (I think) incorporated all the main
discussions about the framework in the TOC above. If there's something I
missed, let me know.

Those who provide the most useful feedback (according to a panel of judges
that include only myself) ;) will get a chance of reading what I've written
so far (under some sort of NDA or O'Reilly will freak out), and get thanked
in the book. Wow, the glory. ;)

TIA,
Peldi

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Supported by Fig Leaf Software
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Lower Prices for Certified Training! Check out new lower prices for
Certified Macromedia Training from Fig Leaf Software. Expand your
skill set with courses in ColdFusion, Flash, Rich Internet
Applications and .NET in the new year.  Fig Leaf Software provides
the highest caliber instruction at our training centers in Washington  
D.C., Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at
your location.

Get the details at http://training.figleaf.com/
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: flashcomm-unsubscribe@(protected)
For additional commands, e-mail: flashcomm-help@(protected)