Re: [pgadmin-hackers] stack trace

2003-06-26 Thread Dave Page


> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED] 
> Sent: 25 June 2003 23:44
> To: Dave Page
> Cc: [EMAIL PROTECTED]; Reinhard Max; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-hackers] stack trace
> 
> We still have an open wxWindows bug with Unicode, and maybe Adam has 
> another from QB.
> Maybe this issue is a reason to upgrade.

Yes, if it helps. If someone can try it and report back, then if it
makes a difference we should *all* upgrade.

Regards, Dave.

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


Re: [pgadmin-hackers] wxWindows Build

2003-06-26 Thread Dave Page


> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: 26 June 2003 02:38
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-hackers] wxWindows Build
> 
> 
> I should point out (perhaps as I should have before) that the 
> 2003-06-07 CVS tree of wxWindows does not build on Mac OS X.  
> That should be reason enough to upgrade the CVS tree.
> 

OK, is there a newe[r|st] one that does?

Regards, Dave.

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html


Re: [pgadmin-hackers] [pgadmin-support] PGA 3 Copy

2003-06-26 Thread Dave Page


> -Original Message-
> From: John Bercik [mailto:[EMAIL PROTECTED] 
> Sent: 25 June 2003 16:20
> To: Dave Page
> Subject: RE: [pgadmin-support] PGA 3 Copy
> 
> 
> Dave,   I do 3 ways,  Right click copy / paste,  Ctrl C / 
> paste and just
> highlight copy / middle click paste.  I even changed my 
> background color thinking they might be pasting white but i 
> get nothing.

I'll have to admit to being stumped then :-(

Does anyone else have any ideas?

> The fonts are just default RH9.  Nice huh?  You're app is looking
> sweet.   

Thanks - it does look nice. Maybe it's just your screenshot, but the
fonts look very nicely anti-aliased. 

> BTW Query Builder kills Pgadmin3 when I pick it.

Yes, Adam is currently looking into this.

Regards, Dave.


> Keep at it and thanks,
> John Bercik
> 
> On Wed, 2003-06-25 at 11:02, Dave Page wrote:
> > > -Original Message-
> > > From: John Bercik [mailto:[EMAIL PROTECTED]
> > > Sent: 25 June 2003 15:51
> > > To: Dave Page
> > > Subject: RE: [pgadmin-support] PGA 3 Copy
> > > 
> > > 
> > > I'm trying to copy the text on the bottom right that has the
> > > Constraint and Alter Table commands.  I am unable to paste it 
> > > anywhere other than pgadmin3.  RH9 has KDE version 3.1
> > 
> > Hmm - are you using right-click copy, or a shortcut like 
> control-c? I 
> > used the right click menu.
> >  
> > > Here's a screenshot:
> > > http://htnweb1.emr.musc.edu/test.jpg
> > 
> > Looks good - (OT: have you tweaked the fonts on your system?)
> > 
> > Regards, Dave.
> -- 
> Best regards,
> 
> John Bercik
> 
> Medical University of South Carolina
> [EMAIL PROTECTED]
> 843-792-1715
> 
> 

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html


Re: [pgadmin-hackers] Belarusian

2003-06-26 Thread Andreas Pflug
Chih-Hsin Lee wrote:

> Is the spelling of "Belarusian" correct? Is it Belorussian?

Could be wrong, but this is extracted from wxWindows, not pgAdmin3. Fix
it in the translation, if you like.

Regards,
Andreas


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


Re: [pgadmin-hackers] Request for translation of pgAdmin3 into Traditional Chinese

2003-06-26 Thread Jean-Michel POURE
On Thursday 26 June 2003 04:28, Chih-Hsin Lee wrote:
> Dear Jean-Michel,
>
> Sorry, another question. I saw the po files other translators made. Some
> included "&" in the translated strings, while some did not. What should I
> treat it when I do it with traditional Chinese, a multibyte language? Does
> wxWindows treat "&Copy" to keyboard hotkey such as "alt-C"?
>
> Sincerely,
> Chih-Hsin Lee

Dear Chih-Hsin,

Yes, wxWindows treat "&Copy" as a keyboard hotkey such as "alt-C". The hotkey 
is displayed undelined. Sometimes, it is hard to determine hotkeys in 
translations, because you have to make sure there are no duplicates. 
Therefore, I only keep hotkeys is same as in English.

But you may also like to wait until the translation is finished and determine 
your "own" hotkeys using pgAdmin3.

Best regards,
Jean-Michel


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


Re: [pgadmin-hackers] Language issue

2003-06-26 Thread Jean-Michel POURE
On Wednesday 25 June 2003 20:17, Andreas Pflug wrote:
> For the user interface, I invented "user language" (langue). This
> expression is used only in limited places, so this is easier.

Thanks, perfect. Do you think we could patent your invention? There are 
thousands of inventors like us who need protection...

:)

Cheers, Jean-Michel


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


Re: [pgadmin-hackers] stack trace

2003-06-26 Thread Jean-Michel POURE
On Wednesday 25 June 2003 23:25, Dave Page wrote:
> I thought we had agreed to stick to 2003-06-07 unless a specific reason
> for upgrading cropped up?

I agree we all need to stick to the same wxGTK version.

>From now on, I will be rebuilding wxGTK everyday from CVS. The packages wron't 
be publised. When needed, we should be able to upgrade all RPM packages. 

Cheers,
Jean-Michel


---(end of broadcast)---
TIP 8: explain analyze is your friend


Re: [pgadmin-hackers] stack trace

2003-06-26 Thread Andreas Pflug
Jean-Michel POURE wrote:

On Wednesday 25 June 2003 23:25, Dave Page wrote:
 

I thought we had agreed to stick to 2003-06-07 unless a specific reason
for upgrading cropped up?
   

I agree we all need to stick to the same wxGTK version.

From now on, I will be rebuilding wxGTK everyday from CVS. The packages wron't 
be publised. 

No don't do this! I tested yesterday, and had to go back to 18th to get 
a workable system with gtk2. The current head is marked as "broken 
except windows", there's heavy reconstruction work underway.

Regards,
Andreas


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


Re: [pgadmin-hackers] stack trace

2003-06-26 Thread Jean-Michel POURE
On Thursday 26 June 2003 00:43, Andreas Pflug wrote:
> Maybe this issue is a reason to upgrade.

Why no strore in CVS a small document with wxWindows library requirements, so 
that anyone can use the same. I see no objection in upgrading regularly the 
RPM packages, the only point is that we need to be informed...

Cheers,
Jean-Michel


---(end of broadcast)---
TIP 8: explain analyze is your friend


Re: [pgadmin-hackers] Belarusian

2003-06-26 Thread Jean-Michel POURE
On Thursday 26 June 2003 07:25, Chih-Hsin Lee wrote:
> Is the spelling of "Belarusian" correct? Is it Belorussian?

Probably. In future versions, we should only provide the list of localised 
languages (Français, Deutsch, English...). So do not take too much time 
translating these entries. I post an e-mail to the list about this issue...

Cheers,
Jean-Michel


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


[pgadmin-hackers] Language list

2003-06-26 Thread Jean-Michel POURE
Dear all,

Would it be possible to display the list of available languages in the form:
Translated_language_name (locale).

This would give us:
Français (fr_FR)
English (en_US)
Deutsch (de_DE)
etc...

The list would not be translated. Whenever a translator adds a .po file 
directory in src/ui, only the locale would be displayed until we update 
languages.h.

Cheers,
Jean-Michel


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


Re: [pgadmin-hackers] Belarusian

2003-06-26 Thread Andreas Pflug
Jean-Michel POURE wrote:

On Thursday 26 June 2003 07:25, Chih-Hsin Lee wrote:
 

Is the spelling of "Belarusian" correct? Is it Belorussian?
   

Probably. In future versions, we should only provide the list of localised 
languages (Français, Deutsch, English...). So do not take too much time 
translating these entries. I post an e-mail to the list about this issue...

 

This would mean that every time a language is added all translators must 
touch their programs
Better all translators decide whether they got the time to translate, or 
simply leave exotic language names unchanged.

Regards,
Andreas




---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


Re: [pgadmin-hackers] Belarusian

2003-06-26 Thread Jean-Michel POURE
On Thursday 26 June 2003 11:51, Andreas Pflug wrote:
> This would mean that every time a language is added all translators must
> touch their programs

Developpers change pgAdmin3 to display the language name (in its translated 
form: Français, English, Deutsch...) everytime a language is added. 
Otherwise, pgAdmin3 should only display the locale name, which allows 
translators to review their translation.

Now, let's suppose that an English user switches to Turkish. How can that user 
switch back to English if the language pop-up is displayed in Turkish?

It would be better if we could only display translated language names:

Français (fr_FR)
Deutsch (de_DE)
English (en_US)
etc..

Cheers,
Jean-Michel


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


Re: [pgadmin-hackers] wxWindows Build

2003-06-26 Thread Adam H. Pendleton




Dave Page wrote:

  
  
  
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
Sent: 26 June 2003 02:38
To: [EMAIL PROTECTED]
Subject: [pgadmin-hackers] wxWindows Build


I should point out (perhaps as I should have before) that the 
2003-06-07 CVS tree of wxWindows does not build on Mac OS X.  
That should be reason enough to upgrade the CVS tree.


  
  
OK, is there a newe[r|st] one that does?

Regards, Dave.

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html

  

Damned if I know.  I tried a few last night, and had problems with all
of them.  The program builds, but the include files are screwed up, so
I couldn't build anything against wxWindows.  I will keep trying to
find a good one.

ahp




Re: [pgadmin-hackers] wxWindows Build

2003-06-26 Thread Dave Page
Title: Message



 

  
  -Original Message-From: Adam H. 
  Pendleton [mailto:[EMAIL PROTECTED] Sent: 26 June 2003 
  13:48To: Dave PageCc: 
  [EMAIL PROTECTED]Subject: Re: [pgadmin-hackers] 
  wxWindows Build 
   
  Damned if I know.  I tried a few last night, and had problems with 
  all of them.  The program builds, but the include files are screwed up, 
  so I couldn't build anything against wxWindows.  I will keep trying to 
  find a good one. 
Yeuch. 
Have we completely removed the 2.4 target now? How about the Mac port is 
non-Unicode only for now?
 
Regards, Dave. 


Re: [pgadmin-hackers] What is ACL

2003-06-26 Thread Jean-Michel POURE
On Thursday 26 June 2003 05:48, Chih-Hsin Lee wrote:
> I am doing the translation for pgAdmin3.pot, What is "ACL"?

Typically, this is a case where you should keep the English acronym, because 
it is widely used. If you create your own, it may not be understood. In 
French, I kept ACL.

Cheers,
Jean-Michel


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [pgadmin-hackers] wxWindows Build

2003-06-26 Thread Adam H. Pendleton




Dave Page wrote:

  Message
  
  
  
   Yeuch. Have we completely removed the 2.4
target now? How about the Mac port is non-Unicode only for now?
   
  Regards, Dave. 

Not sure what you mean here.  Do you mean can we stil use wxMac 2.4?  I
have no idea; I don't know why the requirement for wxWindows 2.5
exists.  I always assumed pgAdmin3 used some feature of wxWindows that
required 2.5.  If that's not the case, I will happily move back to
2.4.  If Unicode support is the only reason to use 2.5, then sure, we
can support a non-Unicode Mac version, for know.  Whatever the
solution, let me know what you decide.  Right now I am trying to solve
the QB and Mac problems, so that we can have them ready when we release.

ahp




Re: [pgadmin-hackers] wxWindows Build

2003-06-26 Thread Dave Page
Title: Message



 

  
  -Original Message-From: Adam H. 
  Pendleton [mailto:[EMAIL PROTECTED] Sent: 26 June 2003 
  16:04To: Dave PageCc: 
  [EMAIL PROTECTED]Subject: Re: [pgadmin-hackers] 
  wxWindows BuildDave Page wrote:
  


 Yeuch. Have we completely removed the 2.4 target now? How about the 
Mac port is non-Unicode only for now?
 
Regards, Dave. 
  Not sure what you mean here.  Do you mean can we stil use wxMac 
  2.4?  I have no idea; I don't know why the requirement for wxWindows 2.5 
  exists.  I always assumed pgAdmin3 used some feature of wxWindows that 
  required 2.5.  If that's not the case, I will happily move back to 
  2.4.  If Unicode support is the only reason to use 2.5, then sure, we can 
  support a non-Unicode Mac version, for know.  Whatever the solution, let 
  me know what you decide.  Right now I am trying to solve the QB and Mac 
  problems, so that we can have them ready when we release. 
Hi 
Adam,
 
As far 
as I am aware it is just the Unicode support that we use 2.5 
for. BTW, when I can persuade 
it to install, I should have a FreeBSD 5.1 box to play with - albeit a pretty 
slow one!
 
Regards, Dave


[pgadmin-hackers] frmQueryBuilder.cpp.patch

2003-06-26 Thread Adam H. Pendleton
Here is a patch that fixes bug #2 in QB.  I have, of course, encountered 
another fatal bug right away :-(, but at least here's another one down.  
This code actually overcomes a problem with the wxWindows code, not our 
own, per se, but until it is fixed  in wx (I have notified them of the 
problem), this will have to do.

ahp

--- pgadmin3/src/ui/frmQueryBuilder.cpp 2003-06-26 05:38:24.0 -0400
+++ pgadmin3.new/src/ui/frmQueryBuilder.cpp 2003-06-26 14:05:53.0 -0400
@@ -299,8 +299,10 @@
 
 wxMDIClientWindow* frmQueryBuilder::OnCreateClient()
 {
-   myClientWindow *tmpwin = new myClientWindow();
-   return tmpwin;
+   m_clientWindow = new myClientWindow();
+   return m_clientWindow;
+// myClientWindow *tmpwin = new myClientWindow();
+// return tmpwin;
 }
 
 

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly