Re: [Adobe-source-devel] Finding resources

[Robert D. <rcd...@gm...>]

On Wed, Jun 3, 2009 at 8:33 PM, Sean Parent <sea...@me...> wrote:

> There certainly needs to be some client code to integrate ASL into a widget
> set - but that could be Win32, WPF, Cocoa, Carbon, GTK, Qt, Flash, HTML, or
> whatever framework you happen to be using. Adobe has their own widget set
> (if you lookup screenshots of our video apps you'll see it in existing
> applications). The layout library and property model libraries are intended
> to be generic components that can be integrated with whatever you are using.
> Kind of like std::vector<> isn't useful unless you supply a type to it.
>
> I hope that folks will share their integrations (maybe Adobe will open
> source their widget library at some point? ).
>
> We backed off from supporting the Win32 and Carbon APIs because MS is
> pushing WPF, Apple is pushing Cocoa, and Adobe chose neither.
>

So you mean to say that out of the box, ASL won't create any widgets? I have
to implement the widgets myself? That could take months, and isn't very
practical. I thought the whole idea behind ASL was to be an alternative to
frameworks like Qt and wxWidgets and provide a way, through a library, to
create GUI applications portably. I'm either still confused or I'm just in a
state of shock.

So just to make sure I get this straight... basically, you're saying that I
do the following to get an app up and running:

   - Download ASL
   - Create a button widget class, and implement it using Win32.
   - Now I can create a button in ASL

If this is true, then ASL's only purpose in that example is to be a
scripting language for widget layout.

And correct me if I'm wrong, but WPF doesn't support C++. So I don't know
what good bringing it up is. Since ASL is in C++, it kind of has to use
Win32 if it plans on supporting Windows UI. I don't see any other choice.