Now the question about Memento and custom classes.
I set my custom classes by [RemoteClass] metadata tag cause when I save the state I want force to pass this classes by Value and not by Reference.
It’s the best practise?

and then… if my custom classes extend Flex or Flash classes, this way doesn’t work cause i can’t modify the super classes.

Thank you in advance
Paolo

I’ll take a closer look at the code, with that clarification in mind.

Thanks so much!

- cubiclegrrl

1. All of the components that make up the example Memento are in .as files. The main parts (following the names used in the Design diagram) are:
a. Memento.as
b. Originator.as
c. Caretaker.as

The DoLoadFMS.as is the equivalent to what most Java programmers would call the “Main” and the LoadSlide.as is just a utility class for loading the slides.

2. The only component used (visual) was a button component and a black graphic backdrop was added. Both could have been handled in code, but slapping on the graphic was super easy and all of the components were called by the same code as with Flex (I believe). I’m pretty sure that the Flex button components can be access through an MXML file. (I’ve not spent enough time yet with Flex, but Chandima and others on this list have. However, the same basic AS 3.0 code works with both Flex and Flash up to a point.)

Your point about bridging the visual and non-visual is something I haven’t really thought about until recently. For the most part, I’ve been trying to move from a combination of drawn-on-the-stage visual (in Flash) to all code so that both Flex and Flash users can more easily use the same files. On this blog, I’m going to be moving more toward Flex, but as a whole, we’re trying to make it available to both Flash and Flex users.

Thanks for your feedback and please feel free to add more comments.
Kindest regards,
Bill

(It’s not Mr. Sanders….makes me feel older than I am!)

I’m a Java programmer trying to OOP in Flash/Flex 3 these days. A couple of questions for the above example:

1.) Is the “Memento” class stored in an .AS file or some other format?
2.) What happens when you try incorporating a non-visual, Memento-like class into the script section of an MXML file?

The overwhelming emphasis in the documentation (at Adobe and elsewhere) is on custom classes that merely extend the base ActionScript classes, not anything you’d to encapsulate information. Your work is the closest I’ve found for that, but information about bridging the visual and non-visual worlds is sorely lacking.

Thanks much,

cubiclegrrl

Thanks for that insightful comment. Whoaaa! What you’re suggesting could set mementos from here to the moon and back if you wanted. That would be totally cool. When you get the write-up on your blog, send us a link to it.

Take care,
Bill

I’ll be writing a post about this on my blog sometime soon, but as always Bill, another great write up!

Dan

I looked at Hive. I’d think that a state/MVC combination would be very interesting.

Bill