Re: [ros-kernel] Re: ROS gui

[Eric K. <ek...@rz...>]

"Royce Mitchell III" <ro...@ev...> wrote:


> * there's no reason for explorer to access 20 registry entries every time
> you double-click something. It should be blind to settings changes made
> directly to it's config files/registry. All settings should be available
> from within the program so that it's not necessary to edit the config
> files/reg directly. At the very least it should re-read it's settings
unless
> it detects they have changed. ( Probably would have to be an ini file to
> monitor for file changes ).

Looking up registry keys and values is not an expensive task in terms of
time consumption, but keeping *all* settings in memory is expensive in terms
of memory consumption. This also obsoletes the concept of monitoring changes
to the registry, at least in most cases.

Btw, classic .ini-files are *dead*. Don't ever use them to store current
application settings! ReactOS should be an '.ini-free' zone.

What really needs to be fixed is the registry management. I really like the
idea of being able to build updated and customized install media.

> * this isn't just for explorer... but there should be very little (
ideally
> none ) images/animations included. They just slow the O/S down. If they
are
> necessary, then they should not be loaded until the first time they are
> needed.

IMO, animations are useful to show that lengthy jobs are still running.
Usually, animations are resources of an application. They will be loaded
when the application is started but they will be swapped to the pagefile
when they are not in use.

Regards,
Eric