Serguei Mokhov wrote:
> For myself, the error messages are least of my worries. Most problems I have
> are with field labels that cannot fit within a given container when translated,
> so a part of a label's text gets truncated. For the dry run mode you need
> little context, you just show all possible dialogs and forms for a given
OK, that's reasonable.
> Nonetheless, Dave Page built 9X binaries for 1.0.2, which work perfectly okay
> for me. Another reason is the registry usage, but as I said, I want to
> avoid the use of registry in the dry run mode altogether.
Our project doesn't contain non-unicode support any more.
> So, if I address the caveats and other issues that come up and
> if the change is not too invasive, I have some chances for the
> work to be applied when I contribute it?
Yes, but not before 1.2 release (which will not take too much time)
It will be hard work:
- many comboboxes are filled from db, you might even force uncatched
- some (few) strings are exchanged at runtime. First that comes to my
mind is "Users/Groups" on the privileges tab, selectable by "display
users in privileges". You could scan for CTRL_STATIC in the sources.
In response to
pgadmin-hackers by date
|Next:||From: Serguei Mokhov||Date: 2004-09-19 20:27:54|
|Subject: Necessity of wxstd.po|
|Previous:||From: Serguei Mokhov||Date: 2004-09-19 17:52:52|
|Subject: Re: Dry Run Mode, + W9X|