PAI in deployed apps?

Folks, is there a simple and qiuck way to use PublishedAspectInspector in
deployed apps? Combined with STB it seems like perfect solution to implement
quickly program settings that do not need to be polished.

Anyway, some parts in PAI and Aspect mechanics is clasified as development,
and it gets stripped automatically. Is there a simple way around that? Or
should I just forget it and write options editor by hand?

Thanks,

rush
--
http://www.templatetamer.com/
http://www.folderscavenger.com/

rush,

> Folks, is there a simple and qiuck way to use PublishedAspectInspector in
> deployed apps?

I don't believe the license allows re-distribution of those components.  You
might be able to persuade (or per$uade ;-) OA to allow you to do so as a
special case.  But I doubt if the PAI is really suitable for end users at all,
and by the time you'd included the compiler in your distribution, worked out
how to prevent the user assigning nil, or 'Hello World' to a Float-valued
aspect, you probably wouln't have saved all /that/ much time :-(


> Or should I just forget it and write options editor by hand?

It'd probably be possible to use the Aspect info (present in your development
image) to automate that, or at least to automate a large chunk of it.

    -- chris

"Chris Uppal" <[hidden email]> wrote in message
news:4346aa66$0$38045$[hidden email]...
> special case.  But I doubt if the PAI is really suitable for end users at
all,
> and by the time you'd included the compiler in your distribution, worked
out
> how to prevent the user assigning nil, or 'Hello World' to a Float-valued
> aspect, you probably wouln't have saved all /that/ much time :-(

hmm well I managed to get rid of workspace appearing as editor, so as long
as one sticks with string, number, boolean, date and folders aspects PAI
takes care that correct editor is displayed.

But you are right, when one factors in license and deployment issues, it is
too much trouble.

Thanks,

rush
--
http://www.templatetamer.com/
http://www.folderscavenger.com/

Rush,

> But you are right, when one factors in license and deployment issues,
> it is too much trouble.

If it's any help, we are more than likely to allow you to bend the
rules and deploy the Published Aspect framework as part of your runtime
application. If you do want to go that way, just send us an e-mail and
let us know what the application does (we simply want to know that is
not a competing Smalltalk environment) and we will let you know if it's
okay to deploy the code.

Best Regards,

--
Andy Bower
Dolphin Support
www.object-arts.com

"Andy Bower" <[hidden email]> wrote in message
news:[hidden email]...
Thanks, in this case I have created a options dialog by hand, but it is good
to know.

rush
--
http://www.templatetamer.com/
http://www.folderscavenger.com/