> it's a shell probllem, isn't it?

yes, of course this is only shell problem, not PowerPro.

> how is the shell to know that
>   [EMAIL PROTECTED]("testarg")
> is to be opened with powerpro?

I mean running from command prompt with space as separation character
and proper extention, and of course without leading dot:
       test.powerpro  ("testarg")
Of course at the moment it is not possible to run scripts with labels
from command prompt.

> maybe you could associate everything not otherwise associated with
> another program, with powerpro?  not sure that's possible, and rather
> doubt that it's desirable.

hmmm, very very risky. I won't try to do it.

> maybe you could associate .ppb files with ppbang, and ppbang could be
> modified to strip the .ppb before sending the command on?

No. I check ppbang and this only passes parameters to PP, so there
isn't possibility to doing some parsing on arguments string before PP
reach it. It seems that this behave exactly like current shell
extention syntax with powerpro.exe.

I do some investigation on this problem.
1. Default shell extention for *.powerpro uses following syntax:
           powerpro.exe *Script RunFile %1
2. shell extenetion for *.bat files uses following:
           "%1" %*
where "%1" is a .bat name
and %* are following [optional] arguments
3. So changing shell extention syntax to:
           powerpro.exe *Script RunFile %1 %*
In this syntax arguments after space are passed - good!
So it should work, but didn't, because *Script not allow arguments - not good.
4. It is possible to try changing syntax again to something like this:
           powerpro.exe RunFile.%1 %*
or
           powerpro.exe RunFile.%1 (%*)
or
           powerpro.exe RunFile.%1 (%2, %3, %4, %5, %6, %7, %8)
because launching
           powerpro.exe RunFile.test ("testarg")
works great from command line, but... runfile.scriptfile syntax do not
allow file extentions nor script path!!!
So this didn't work too! :-(

But maybe workaround might be setting shell syntax to something like...
           powerpro.exe RunFile.parser %1 %*
...and script called "parser.powerpro" would modify passed args
(strips path and extention) and call originaly launched script...???
I think that this might work... but more investigation must be done...
maybe tomorrow... good night for all...


Attention: PowerPro's Web site has moved: http://www.ppro.org 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/power-pro/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to