> restricted
> > wanted to throw an idea of merging more than one of those items
> into a
> > single .ini. while maintaining:
>
> An approach that would do something similar is to use a script of
> configure commands to do effectively merged importing.
>
> I know this means you still have to edit every file separately, but I
> am not sure that is a bad thing.
Oh, I'm not against multiple files for regular configuration or playing with
your own setup. I'm just trying to think ahead about shared scripts. With
the new .ini import formats (especially with the import command not
permanently storing the info in the .pcf) it's become exponentially easier
to build scripts for sharing and optionally run a script and see if you like
it before doing the work to integrate it into your config.
I was just trying to get a situation where you could have a script that
might involve any combination of items in powerpro and have everything
included into a single file. I've done a little more thinking since
then...there are some things that the new .ini format couldn't do: execute
commands
I was trying to get the .ini file to do everything to combine any part of
powerpro into a single file for running a script or function. I think what I
need to do is get .powerpro scripts to do everything. Let me work on this a
while.
Thanks Bruce
David Troesch | Atlanta, GA | ICQ# 2333123
Life is short. Fly fast. RIP Sergio:12/03
Funstuff: Always remember you're unique, just like everyone else.
**** EDIT YOUR POSTINGS !!!! ****
Please remove as much as possible from original messages before replying to them.
________________________________________________
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/
