Ok, that was it.

So now I have some thoughts and some questions.

1. Very Nice!

2. Can the UI be built in a declarative (i.e. MXML) kind of way?

3. Does your container system operate on a relative basis? By that I mean:

   a. can you specify a containers size as a percentage of its parent?

   b. if you resize a container can that cause its siblings to resize
automatically. For
      example a resizing bar between two containers where resizing
shrinks one container
      and grows the other.

Thanks
Hank

Thanks
Hank

On 10/5/05, David Karam <[EMAIL PROTECTED]> wrote:
> Hi
> I think you have a beta of the Flash 8 plug in. Try updating it.
> Best,
> David
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of hank williams
> Sent: Wednesday, October 05, 2005 5:26 PM
> To: Open Source Flash Mailing List
> Subject: Re: [osflash] Component Library
>
> David,
>
> I tried running the app pointed to by your first link.
>
> It doesnt work for me because it seems to be stuck in some infinite loop
> that is probably timing related. It continuously gives me the "your app is
> running slow would you like to abort" message.
>
> Just to give it a fair chance I clicked "no" at least 30-40 times. I dont
> think its actually running **that** slow. I think you must be doing
> something when you start up that is a timing problem.
>
> Once I do finally abort, I do see what looks like a window in the upper
> left-hand corner. But the window header text is flickering as if it is stuck
> in some loop. At this point the app does not respond to mouse clicks.
>
> I am quite interested in what you are doing, so I hope you can make it work.
>
> Regards
> Hank
>
> On 10/5/05, David Karam <[EMAIL PROTECTED]> 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

Reply via email to