Re: pgAdmin3 doc location

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>
Cc: <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: pgAdmin3 doc location
Date: 2003-06-23 15:15:50
Message-ID: 03AF4E498C591348A42FC93DEA9661B844B119@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Andreas Pflug [mailto:Andreas(dot)Pflug(at)web(dot)de]
> Sent: 23 June 2003 16:09
> To: Dave Page
> Cc: pgadmin-hackers(at)postgresql(dot)org
> Subject: pgAdmin3 doc location
>
>
> Hi Dave,
> I've seen you just added options-tab doc under en_US/*.html.
> I wanted to comment on doc location before, just forgot to do it. I
> think making the location for application documentation doesn't make
> sense, because each version of the binary should be packed with the
> exact matching doc version. Therefore, only one version is
> needed. On the other side, if the doc location is well-known
> to us, we could
> easily switch directories to the best matching language version
> (fall-back language will be of course en_US). Additionally,
> if we switch
> to a different format (e.g. HTML workstop) to support search
> and index,
> upgrading the setting wouldn't be possible anyway.

Yeah, that's been on my mind as well. The problem is, how do you specify
a higher location that will still allow web versions to work? Or do you
propose junking web versions of the app docs and searching for them
using a similar algorithm to that used to find xrcs?

BTW, did you get a chance to look at the row insert bug I mentioned in
the edit grid?

Regards, Dave.

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Andreas Pflug 2003-06-23 15:35:12 Re: pgAdmin3 doc location
Previous Message Dave Page 2003-06-23 15:11:08 Re: pga2: fix and add