> I'm curious as to how you would achieve the "no longer requiring a refresh"
> objective if you keep everything in one file. New items in this file would
> still have to be parsed out wouldn't they?

They would, but by keeping track of the ARB script's last modified 
timestamp it is possible to impose a rebuild of the cache when the 
script has been modified. This can happen automatically the next time 
ARB is invoked after an edit.

> I have well over 1000 aliases, and having a script file for each item (some
> of them very simple, often one line) seems a bit clunky to me. 

That's truly amazing! Here was I feeling bogged down and considering 
weeding out the unused of my 52 aliases. Do you find that you use them 
all still? I'm guessing that you use ARB to simulate PowerPro's macro 
capability to an extent.

This brings up an issue that I hadn't contemplated -- how long does it 
take for you to rebuild your alias cache? Do you modify your aliases 
often? You might find that imposed auto-refreshes would hinder you if 
modifying your ARB script is a frequent pastime.

> If ARB is to have autocomplete, these files still have to be listed and
> their names placed into a vector - which is much faster than the current
> rebuild process, but a rebuild (of the alias vector) nonetheless. Perhaps
> you will generate the autocomplete list anew whenever ARB is called?

If I were to continue parsing aliases from a single file then no 
difference would be made to the caching mechanism that's currently in 
place. On the other hand, if I were to read a directory for a list of 
alias scripts then I most likely wouldn't need to cache them if things 
move quickly enough.

> How about history? These would still have to be stored and reloaded
> separately right?

Correct, the history will still be written to and read from a user- 
definable file.

> Personally I'm not too bothered whether the files are prefixed, stored in a
> specific folder or both/neither - whichever you find neater. I agree with
> David's suggestion of a user-defined prefix/path.

After some further thought it seems that I can pass that choice to the 
users anyway. I can give them a variable asking for the prefix that 
signifies an ARB alias and if they enter a slash somewhere, we're 
talking about a subfolder. Too simple.

I'm 99.46% confident that no functionality would change as a result of 
any potential change to the way ARB handles its aliases -- the only 
planned difference is the removal of the option to manually rebuild the 
cache since it will no longer be needed.

-- 

Best regards,
Alex



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