Hi David, this sounds good, it will make the whole library more flexible. By the way: I was able to compile your lib (does it have a name?) and run the example application without any problems. I noticed that instead of subclassing MovieClip (as the MM components do) you used delegation to the parent mc. Of course this has a lot of advantages. But I missed a convenient way to attach a mc to a Panel. Do you think it would make sense to have such a convenience method in the Panel and its subclasses? Ciao Gregor
David Karam wrote: >Hi Gregor, > >It might not currently, but should (shortly) work as your describe. I am >collecting a list of requirements for the component library. This will >definely go on the list. I will post a list of development milestones and >put a little organization to this project after my wedding (on Friday!!!). > >Best regards, >David > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of Gregor Frey >Sent: Monday, October 10, 2005 10:21 AM >To: Open Source Flash Mailing List >Subject: Re: [osflash] Component Library > >Hi David, >can your components be used outside the whole application framework? >I tried > > var menuBar:MenuBar = new MenuBar(); > var gameMenu:Menu = new Menu("Spielmenü"); > var exitItem:MenuItem = new MenuItem("Schluß"); > gameMenu.addOption(exitItem); > menuBar.addMenu(gameMenu); > menuBar.paint(); > >But this doesn't show me a thing. >Ciao >Gregor > >David Karam wrote: > > > >>Hi >> >> >>I have posted a component library written in ActionScript 2. This >>library is based on a strongly decoupled view and controller with a >>considered method of data binding based on XML or class modeled sources. >> >>The component library has passed its design phased and is in the proof >>of concept phase. Try the sample application featuring: context >>sensitive menus, drag and drop tree nodes, strong data binding with xml >>source, a complex table/tree widget with pulldowns and invisible fields >>and context sensitive component behavior. The main application class >>(com.posttool.app.categoryEditor.Application) is in the Eclipse project >>listed below. >> >>http://posttool.com/as2components/deploy/ >> >> >>Class overview >> >>http://posttool.com/as2components/classDiagram.png >> >> >>Documentation >> >>http://posttool.com/as2components/docs >> >> >>Downloadable "FAMES" Project >> >>http://posttool.com/as2components/UI0.zip >> >> >>A Note about the use of SWF files >> >>I currently use SWF files (source files fla6 included) with a creative >>movieclip instance naming system to skin the UI. I will have clean >>documentation on this aspect shortly and post the spec for each component. >> >>This provides clean separation between designer and programmer. I hope >>that the ability to create drawings in Swfmill progresses to a nice api >>so that the skins could be specified that way. I also hope that Adobe >>Illustrator will be able to export compliant SWF skins for this system. >> >>This configuration is much more convenient than drawing the components >>with code. It puts control of the 'drawings' in the hands of designers >>and allows the windowing toolkit to be easily skinned. With the >>proliferation of SWF generators, many authors with a variety of tools >>will be able to create the component skins. >> >> >>Finally >> >>I would like to set this up as a new osflash project only if someone is >>interested in working on it with me. I realize that there are other >>component libraries being developed. I would like to distinguish this >>one as the simplest code base with clean separation between primitive >>drawing & controller code. >> >> >> >>Best regards, David Karam >> >> >>_______________________________________________ >>osflash mailing list >>[email protected] >>http://osflash.org/mailman/listinfo/osflash_osflash.org >> >> >> >> >> > > >_______________________________________________ >osflash mailing list >[email protected] >http://osflash.org/mailman/listinfo/osflash_osflash.org > > >_______________________________________________ >osflash mailing list >[email protected] >http://osflash.org/mailman/listinfo/osflash_osflash.org > > > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
