Thread: Re: [BUGS] More SSL questions..
> > Perhaps there is another extension that is good for Win32 >but i don't >> think *.txt is it. >> > >If there needs to be an extension, the new MS thinking in .NET >seems to >favour .config files. Both ASP.NET web applications and windows .NET >executables are automatically given associated .config files by visual >studio.net Well, those are both XML files that follow a very specific schema (and it's the same schema for both these, except there are of course some tags not relevant in each one). I don't see the ".net does it" argument as very powerful unless we go all the way - and we don't want to do that. My vote is to either go with .txt - to make it autoopen - or go with no extension at all (as in unix, except remove the initial dot that makes the whole filename into the extension). //Magnus
Folks,
I've been following this discussion for some time now and I think that you
are losing the focus. I mean, who is your target audience ? How many people
may be out there who have the technical knowledge to put the correct
settings in the database config files but do not know how to open and modify
them just because they do not pop up using simple double clicks ? [The same
goes for the hidden/not hidden directory discussion, BTW.]
Therefore, I'd like to suggest to consider the following solutions:
1. Use the ".ini" extension. Ini files contain plain text, are associated
with notepad.exe by default and will show up as "Configuration Settings" in
the explorer. It doesn't matter if they do not fully comply with the default
ini file format in case of Postgres, as long as they are not accessed by the
corresponding special API functions.
or
2. Use a Postgres specific extension like ".pgconfig" and let the installer
create a proper file type association. I suppose most Windows users will use
the installer (and those who don't will know how to handle the files
manually). Alternatively/Additionally, the installer might also set up a
link like "Modify configuration file" in the program group associated with a
"notepad <path><file>" command. The Apache HTTP server installer does
something similar for its "httpd.conf" file, IIRC. This would also "bypass"
the hidden directory issue.
What do you think ?
Best regards,
Christian.
----- Original Message -----
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Gary Doades" <gpd@gpdnet.co.uk>; "Bruce Momjian"
<pgman@candle.pha.pa.us>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>; <pgsql-hackers-win32@postgresql.org>;
"Matthew T. O'Connor" <matthew@zeut.net>; "Andrew Dunstan"
<andrew@dunslane.net>; "T.J." <tjtoocool@phreaker.net>
Sent: Friday, January 07, 2005 11:38 PM
Subject: Re: [pgsql-hackers-win32] [BUGS] More SSL questions..
> > Perhaps there is another extension that is good for Win32
>but i don't
>> think *.txt is it.
>>
>
>If there needs to be an extension, the new MS thinking in .NET
>seems to
>favour .config files. Both ASP.NET web applications and windows .NET
>executables are automatically given associated .config files by visual
>studio.net
Well, those are both XML files that follow a very specific schema (and
it's the same schema for both these, except there are of course some
tags not relevant in each one). I don't see the ".net does it" argument
as very powerful unless we go all the way - and we don't want to do
that.
My vote is to either go with .txt - to make it autoopen - or go with no
extension at all (as in unix, except remove the initial dot that makes
the whole filename into the extension).
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Christian Klemke wrote: > Alternatively/Additionally, the installer might also set up a link > like "Modify configuration file" in the program group associated with > a "notepad <path><file>" command. The Apache HTTP server installer > does something similar for its "httpd.conf" file, IIRC. This would > also "bypass" the hidden directory issue. > > Probably the best of an unappealing set of alternatives. I would strip any leading dot and leave the rest up to the installer guys. Adding ".txt" just sends shudders down my spine. cheers andrew
Christian Klemke wrote: > Folks, > > I've been following this discussion for some time now and I think that > you are losing the focus. I mean, who is your target audience ? How many > people may be out there who have the technical knowledge to put the > correct settings in the database config files but do not know how to > open and modify them just because they do not pop up using simple double > clicks ? [The same goes for the hidden/not hidden directory discussion, > BTW.] > > Therefore, I'd like to suggest to consider the following solutions: > > 1. Use the ".ini" extension. Ini files contain plain text, are > associated with notepad.exe by default and will show up as > "Configuration Settings" in the explorer. It doesn't matter if they do > not fully comply with the default ini file format in case of Postgres, > as long as they are not accessed by the corresponding special API > functions. The .ini extension is pretty much the default for system level setting stuff on Win32... I would say we should probably go with that. Sincerely, Joshua D. Drake > > or > > 2. Use a Postgres specific extension like ".pgconfig" and let the > installer create a proper file type association. I suppose most Windows > users will use the installer (and those who don't will know how to > handle the files manually). Alternatively/Additionally, the installer > might also set up a link like "Modify configuration file" in the program > group associated with a "notepad <path><file>" command. The Apache HTTP > server installer does something similar for its "httpd.conf" file, IIRC. > This would also "bypass" the hidden directory issue. > > What do you think ? > > Best regards, > Christian. > > > ----- Original Message ----- From: "Magnus Hagander" <mha@sollentuna.net> > To: "Gary Doades" <gpd@gpdnet.co.uk>; "Bruce Momjian" > <pgman@candle.pha.pa.us> > Cc: "Tom Lane" <tgl@sss.pgh.pa.us>; > <pgsql-hackers-win32@postgresql.org>; "Matthew T. O'Connor" > <matthew@zeut.net>; "Andrew Dunstan" <andrew@dunslane.net>; "T.J." > <tjtoocool@phreaker.net> > Sent: Friday, January 07, 2005 11:38 PM > Subject: Re: [pgsql-hackers-win32] [BUGS] More SSL questions.. > > >> > Perhaps there is another extension that is good for Win32 >> but i don't >> >>> think *.txt is it. >>> >> >> If there needs to be an extension, the new MS thinking in .NET >> seems to >> favour .config files. Both ASP.NET web applications and windows .NET >> executables are automatically given associated .config files by visual >> studio.net > > > Well, those are both XML files that follow a very specific schema (and > it's the same schema for both these, except there are of course some > tags not relevant in each one). I don't see the ".net does it" argument > as very powerful unless we go all the way - and we don't want to do > that. > > My vote is to either go with .txt - to make it autoopen - or go with no > extension at all (as in unix, except remove the initial dot that makes > the whole filename into the extension). > > //Magnus > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org -- Command Prompt, Inc., home of PostgreSQL Replication, and plPHP. Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Attachment
"Christian Klemke" <Christian.Klemke@t-online.de> writes:
> I've been following this discussion for some time now and I think that you
> are losing the focus. I mean, who is your target audience ? How many people
> may be out there who have the technical knowledge to put the correct
> settings in the database config files but do not know how to open and modify
> them just because they do not pop up using simple double clicks ?
Fair point ;-)
> 1. Use the ".ini" extension. Ini files contain plain text, are associated
> with notepad.exe by default and will show up as "Configuration Settings" in
> the explorer. It doesn't matter if they do not fully comply with the default
> ini file format in case of Postgres, as long as they are not accessed by the
> corresponding special API functions.
Well, this seems to me to have the same objection raised by Bruce for
".txt", which is that it might cause people to make mistaken assumptions
about the valid format of the file. I don't think it's worse than .txt
but I'm not sure it's better either.
> 2. Use a Postgres specific extension like ".pgconfig" and let the installer
> create a proper file type association. I suppose most Windows users will use
> the installer (and those who don't will know how to handle the files
> manually). Alternatively/Additionally, the installer might also set up a
> link like "Modify configuration file" in the program group associated with a
> "notepad <path><file>" command. The Apache HTTP server installer does
> something similar for its "httpd.conf" file, IIRC. This would also "bypass"
> the hidden directory issue.
The link idea doesn't work because the installer doesn't necessarily
know where these files will be --- they are per client user, not per
installation.
regards, tom lane
Tom Lane wrote: >The link idea doesn't work because the installer doesn't necessarily >know where these files will be --- they are per client user, not per >installation. > > > > Could the shortcut could be like this?: notepad %APPDATA%\pgfoofile cheers andrew