Re: [Adobe-source-devel] List View / Tree View with ASL

[Sean P. <sea...@ma...>]

Here is the history of the widgets in the platform library:

They started life as part of the Begin test app - just a thin shim between ASL and the Mac OS Carbon platform widgets.
One of our contributors ported Begin to Windows and we decided to go through the effort to clean up the widgets and make them "real."
Then Apple dropped Carbon for 64 bit, and Microsoft moved away from Win32 in favor of WPF. Adobe decided not to follow either and invest in our own framework (you can see it in our video products).

None of the Adobe contributors can afford the bandwidth to really do a good job with the widgets, so we just keep them alive for testing.

You are correct that there is no list/tree view. The property model library (Adam) doesn't deal with sequence manipulation so it wasn't needed for that. Foster has been doing work on a sequence model library (which is in APL) and is getting some use with our internal list widget. He may be able to comment further.

The "future" directory was created when we were looking to make the widgets "real" and before we split the library into ASL and APL. I'd love to clean up the directory structure in APL but haven't had the time (my time, when I have it, is on the ASL side). Feel free to jump in an help!

Sean

 
On Sunday, May 10, 2009, at 11:18AM, "Robert Dailey" <rcd...@gm...> wrote:
>I've been reading through the documentation and I've found various widget
>types under the platform library. I don't fully understand ASL yet nor how
>widgets are created and accessed from C++, but I didn't see a List/Tree view
>widget. Unfortunately, I'm pretty confused because the same widgets (Button,
>for example) seem to be in different locations in the Perforce repository.
>There's one for each platform, which is fine, but then there's some under
>'future', and other confusingly named directories.
>
>What I would like to know is if ASL currently has support for a list/tree
>view widget on the Windows platform. If so, where can I read more about this
>widget? Secondly, what does the 'future' directory mean? Why are there so
>many copies of the same widget source files scattered around the place? Some
>copies don't even seem to be related to a specific platform.
>
>Thanks.
>