Re: [Adobe-source-devel] Finding resources

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

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

> I would object to putting in support for searching above the folder
> containing the executable - this is a potential security risk (a resource
> can be replaced/overwritten without write access to the application
> directory).
>
> Copying application resources into a "package" is a good thing.


Good point. I had always agreed with this, it's just an interesting
way of looking at my suggestion. I never thought of how it could be
exploited for the worst.

I think there is some miscommunication here. When I called the begin
app a unit test, that's because I'm referring to the one in
//adobe_platform_libraries/test/begin. When I ran this app, it was
merely a dialog with a slider and an edit field. Nothing more. It
didn't look like a "GUI
front-end and editor for property model and layout library files
". Is there another begin app somewhere I am missing out on? Apologies
for my confusion.

There's also another thing I'm fairly confused about. And again, I do
apologize, as this is getting slightly off topic, but bear with me if you
would. Let's say that APL goes away, since that essentially seems like what
it will do eventually. With just ASL around, how can it possibly be
functional without any widget implementations? For example, if I have an
interface for a Button widget, but no implementation for it for Windows, no
button can be created. There needs to be Win32 code at *some level* in order
for ASL to be even remotely useful. Either that, or the design philosophies
I've been reading are completely misleading. Some detailed insight into this
would be really helpful for me. If there are articles I can read, by all
means please point me in the right direction.

Thanks again to everyone for helping.