Seems your datagrid is a giant movieclip in a scrollview. Is that right? I've taken a look at the code, and you have done some interesting things. I particularly like the simplicity of your layout manager. No bells and whistles, but if you know what you're doing up front, it looks like it will work perfectly.
-----Original Message----- From: Scott Hyndman on behalf of Scott Hyndman Sent: Wed 10/5/2005 7:17 PM To: Open Source Flash Mailing List Cc: Subject: RE: [osflash] Component Library Where did this come from? Great job! You've got to love when things come out of left field like this. Is your datagrid a scrollview kind of deal? How many rows can it handle? I'm sure I'll have more questions...are you on MSN? (I'm writing a datagrid for ActionStep right now, so I'm interested in how you did a few things) /Scott -----Original Message----- From: [EMAIL PROTECTED] on behalf of David Karam Sent: Wed 10/5/2005 6:51 PM To: [email protected] Cc: Subject: [osflash] Component Library 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
<<winmail.dat>>
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
