Re: [ros-kernel] Re: ROS gui

[Jarmo M. <ja...@mu...>]

In the old days when you installed the OS, you just copied the
apps to the disk. Settings file included. Now many apps require
installation.

My own app uses registry because it was designed for multiple
users. With INI files the settings should be separate for every
user. Also INI files will be more difficult than registry if it
uses hierarchy as my next version will use. So there is pros &
cons for registry and INI files.

My app installs itself when it notices that registry settings are
not there. And of course, ALL personal registry settings are
removed when unistalled. And when the last user of the app
uninstalls it, everything is removed from the registry and all
files and directories are deleted, if user wants.

I have an idea of "application private registry". It is located in
the application's folder. Registry functions would work as before.
It is just bound to system registry so it seems to be normal. OS
could keep list of bound registries and if not found, the bound
registry is removed from the list. So you can just delete the
application folder and your settings are deleted from OS as well.
Unfortunately this idea cannot be implemented.

JMu

----- Original Message -----
From: "Royce Mitchell III" <ro...@ev...>
To: <rea...@li...>
Sent: Saturday, July 20, 2002 5:13 PM
Subject: Re: [ros-kernel] Re: ROS gui


> We have a fundamental difference in philosophy :)
>
> Here's why I said what I said:
>
> I consider myself a power user. Almost everyone who knows me
calls me to fix
> their computer problems. I'm the local "computer geek". I've had
a lot of
> experience reinstalling Windows, and the most annoying thing
about
> reinstalling Windows is having to reconfigure Windows and the
applications
> with the settings I want. When applications use INI files, I
don't have to
> reconfigure them! They work with the new OS! Applications that
use the reg
> have to be reinstalled most of the time, although some
applications (
> PageMaker 6.5 & TurboCad 6 Professional for example ) will just
recreate
> their registry entries; although I still have to reconfigure
them for my
> preferences.
>
> As a developer, I *never* use the registry unless it's necessary
to hide
> settings, or my customer requests it.
>
> On animations, there are ways to show that a program is working
that doesn't
> require resource-intensive animations. Progress dialogs are a
good example.
> Another way is to have count-up/down timers, and status text
windows
> explaining what's happening at that moment.
>
> Most settings are a matter of a bool or int. How much memory
does that
> really take up?
>
> Royce3
>
> ----- Original Message -----
> From: "Eric Kohl" <ek...@rz...>
> To: <rea...@li...>
> Sent: Saturday, July 20, 2002 5:52 AM
> Subject: Re: [ros-kernel] Re: ROS gui
>
>
> >
> > "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
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > reactos-kernel mailing list
> > rea...@li...
> > https://lists.sourceforge.net/lists/listinfo/reactos-kernel
> >
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel
>