1. your Presentation object needs to have a “children” ArrayCollection property, each of which is a Slide. (If you don’t call the property “children”, you need to supply a MOCCASIN_CHILDREN_PROPERTY with the name you used.)

2. override PresentationView’s createChildView() method to create a SlideView() for a new Slide child model.

3. when you create your new Presentation, add a Slide to it. This should cause the SlideView to be created.

Note that if you’re trying to be like PowerPoint or Keynote, you might not actually want your presentation views to be in the MoccasinView along with the slides. In that case you might want to make the SlideView the root model object of your MoccasinView and show the Presentation views somewhere else, like as items in an mx:List component.

I’m really impressed with your framework. I’ve managed to figure out quite a bit. One thing I’m working on at the moment is a graphical presentation editor. I can’t seem to figure out how to make an app that goes one model deeper i.e.

-> Moccasin -> Presentation -> Slide. I can get the editor functionality working on the PresentationView but I’d ultimately like to extend it to the SlideView. Problem is when I create a new Presentation Model it needs to automatically create a new slide model and attach it.

Hopefully all of that makes sense? Essentially all I want to do is take your simpleworld example and add another layer. e.g.

Moccasin -> Universe -> World -> Square

Cheers,

Rob

What I would really like to do (and what Marc has done a wonderful job of) is have a cool hookup between Moccasin and Degrafa. There’s probably a good way to do that without disrupting anything but I haven’t had time to check it out.

Very nicely done and useful framework. A question for you - I’ve been working on a graphical editing app and was using ObjectHandles framework to enable handles on objects and subsequnt dragging, sizing, rotation. The OH framework goes a little further on manipulation of object properties but it utilizes a wrapper type approach, much like Moccasin. I’m not sure if you looked at OH but do you have any suggestions on an approach to use both frameworks to complement each other? As it is, OH wants to be the outermost object wrapper so the graphical handles can match the extents of the underlying shape (usually a flex container holding whatever) but I don’t know how I can wrap a moccasin model, or for example a collection of objects selected by a drag selection and wrap with OH to allow the property mods. Is this viable or would you suggest extending moccasin to allow rotation handles and rotation mouse event handling and further extend it to allow those functions for multiple selected graphical objects?

thanks for any suggestions on this,
Danny

You probably won’t believe this, but I started working on something similar like a couple weeks ago, basically trying to figure out a framework suitable for graphical editing, with MDI, document management, undo/redo, and of course, the editor itself.

I’m having a look at the source right now, just want to say a big “thank you” for sharing this :)

Jeremy.

This is great - just diving into the source now, to see if it might integrate with a framework of my own, but I’m very excited about the possibilities.

Thanks!

Ian