Re: MyStyle database.

• Messages sorted by: [ date ][ subject ][ author ]
• Next message: Sasha Vasko "Re: MyStyle database."
• Previous message: "MyStyle database."

Sasha_Vasko@osca.state.mo.us writes:

> 
> The disadvantage of course is that we'll need to break compatibility with
> old
> configuration files.
> 
Another disadvantage is that the Style database (aka new look file)
will have to be read by each module at startup time.  Could we have
AfterStep cache the styles in memory somewhere?  This would be a poor
use of memory, but would cause startup to be faster.  If all of the
styles were in memory, then the individual modules could just read
from that shared memory location.  Updating the look would then be
pretty fast.  AS would simply update the memory locations and tell the 
modules to reread the memory rather than re-parse the same file 3 or 4 
times.

In retrospect, my message does not seem very coherent.  My main
complaint is that each module would have to parse two files at
startup.  One of those two files would get parsed by every module.  It 
seems like there would be a more efficient method.

-- 
 (__)  Doug Alcorn
 oo /  alcornd@earthlink.net
 |_/   dalcorn@calltech.com

• Next message: Sasha Vasko "Re: MyStyle database."
• Previous message: "MyStyle database."