Hello NetVicious,

Thursday, February 24, 2005, 14:31:21, you wrote:

N> jueves, 24 feb 2005 at 20:28, it seems you wrote:

>> Currently, The Bat! keeps its files in two directories:
>> 1. The read-only program files in the "Program Files" folder
>> 2. The files that it modifies in the "MAIL Directory"

>> We don't like to make one additional directory besides the "MAIL
>> directory", we don't like to have three different directories.
N> Well  in  this  case, TB! should create or mark the ini files with the
N> Windows  username  it's  using the program. If you don't separate this
N> the different users of the program will have the same configurations

>> But if there is rationale for this third directory, please let us know.

N> The   old   ini   files  where  deprecated  with  the registry because
N> with  the old ini files each program had one only configuration. Later
N> in Win2000 M$ added the Documents&Settings folder.

N> I only said one think. Now with the registry each user could have it's
N> config. If TB! uses ini files if TB! don't marks or uses different ini
N> files  for  each user all the users of the computer will have the same
N> configuration, and if one user changes something the others users will
N> get also the same changes.

N> BsPlayer  (www.bsplayer.org)  uses xml files marked with the username.
N> Example:  BSPlayer.User1.xml  and BSPlayer.User2.xml. You could create
N> folders on mail folder or where you like for the user ini files.


Some things here:

0. the old .ini files were deprecated because every application put
them under the Windows system directory -- which, even at the
beginning (and I am talking about Windows 1.x here) was an atrociously
bad idea.

1. even if this is getting not to be common anymore, you can have many
users sharing a single Windows system. User-specific settings should
*by default* be saved under the current user system folder; the user
can be given an option to move it elsewhere. The reason here is a
simple one -- privacy.

2. samewise, each user should be able to configure TB! as if this user
were to be the single TB! user. This means that configuration data, be
it in the Registry or in an initialisation file, should also be stored
under the current user area (either HK_CurrentUser, or under 'My
Documents', for example). This means, for example, that one user can
use BayesIt! while another user, on the same box, can use Bayes
Filter.

3. Except for system settings, using the Registry just makes life a
lot more miserable for those of us that jump systems, or have to
rebuild them -- for whatever reason. On the other hand, for corporate
users that roam on a Domain, not having the settings under the
HK_CurrentUser will, of course, be a major pain.

4. And, on the other hand (that's the third hand for those of you that
did not count them) this is probably not a significant issue given
that the roaming user will still need to access the mail base
(probably on an altogether different computer that the one in use to
execute TB!).

So... right now, it is difficult to decide which way. I myself would
go off the Registry, no questions asked -- I simply hate the beast,
and the current abuse of what started as a good idea. My personal vote
is for XML-based initialisation files.

-- 

 ..hggdh..

Using The Bat! v3.0.2.10 and  on Windows 2000 5.0 Build  2195 Service
Pack 4, waiting for an UNIX-based TB!


________________________________________________________
 Current beta is 3.0.9.1 Deep Alpha | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/

Reply via email to