From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 5005 invoked from network); 12 Mar 2003 17:56:57 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 12 Mar 2003 17:56:57 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 12 Mar 2003 17:56:57 -0000 Received: (qmail 30329 invoked by uid 8); 12 Mar 2003 17:56:56 -0000 Received: from xavier.alldunn.com (192.168.1.90, claiming to be "alldunn.com") by gate.alldunn.com with SMTP id smtpdYMFZ1L; Wed, 12 Mar 2003 12:56:51 EST Message-ID: <3E6F74DE.1090507@alldunn.com> Date: Wed, 12 Mar 2003 09:56:46 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org Subject: test message Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 26103 invoked from network); 12 Mar 2003 18:41:30 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 12 Mar 2003 18:41:30 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 12 Mar 2003 18:41:30 -0000 Received: (qmail 31542 invoked by uid 8); 12 Mar 2003 18:41:30 -0000 Received: from xavier.alldunn.com (192.168.1.90, claiming to be "alldunn.com") by gate.alldunn.com with SMTP id smtpdfVcinL; Wed, 12 Mar 2003 13:41:29 EST Message-ID: <3E6F7F54.4020001@alldunn.com> Date: Wed, 12 Mar 2003 10:41:24 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: test #3 does this one make it? -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 26725 invoked from network); 12 Mar 2003 18:43:01 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 12 Mar 2003 18:43:01 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 12 Mar 2003 18:43:0 -0000 Received: (qmail 31596 invoked by uid 8); 12 Mar 2003 18:43:00 -0000 Received: from xavier.alldunn.com (192.168.1.90, claiming to be "alldunn.com") by gate.alldunn.com with SMTP id smtpdEdsKL5; Wed, 12 Mar 2003 13:42:57 EST Message-ID: <3E6F7FAD.6040404@alldunn.com> Date: Wed, 12 Mar 2003 10:42:53 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robin Dunn CC: wxPython-dev@lists.wxwindows.org References: <3E6F7F54.4020001@alldunn.com> In-Reply-To: <3E6F7F54.4020001@alldunn.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] test #3 Robin Dunn wrote: > does this one make it? > Replpy to list is turned off... -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 29929 invoked from network); 12 Mar 2003 18:50:31 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 12 Mar 2003 18:50:31 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 12 Mar 2003 18:50:31 -0000 Received: (qmail 31829 invoked by uid 8); 12 Mar 2003 18:50:30 -0000 Received: from xavier.alldunn.com (192.168.1.90, claiming to be "alldunn.com") by gate.alldunn.com with SMTP id smtpddOfNn1; Wed, 12 Mar 2003 13:50:27 EST Message-ID: <3E6F816E.3010006@alldunn.com> Date: Wed, 12 Mar 2003 10:50:22 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: test #4 hello again -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 1350 invoked from network); 13 Mar 2003 08:28:33 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 13 Mar 2003 08:28:33 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 13 Mar 2003 8:28:32 -0000 Received: (qmail 6456 invoked by uid 8); 12 Mar 2003 23:28:31 -0000 Received: from xavier.alldunn.com (192.168.1.90, claiming to be "alldunn.com") by gate.alldunn.com with SMTP id smtpdDCrZZC; Wed, 12 Mar 2003 18:28:23 EST Message-ID: <3E6FC291.30307@alldunn.com> Date: Wed, 12 Mar 2003 15:28:17 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-users , wxPython-dev@lists.wxwindows.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: New build/release policy Hi all, First of all, sorry about the past few days. I'm being stretched thin by a couple other big things right now and unfortunately it showed through in the recent true/false issues. Secondly, the purpose of this mail is to outline a new policy that I'll try to stick to for doing builds and releases in the future. This will just be high level for now, but I expect to flesh it out more and put a page or two on the wxPyWiki about it soon. 1. The wxPython-dev mail list has been created. I asked for it before a number of people requested that development issues still be discussed on the -users list, which I mostly agree with. So instead of using this new list for discussing features and etc. I'd like to use it for coordinating between myself and people who contribute code to wxPython and also people who are willing to test prereleases of wxPython. So... If you have contributed code to wxPython in the past or plan to in the future, or are willing to test prerelease binaries then please join the wxPython-dev list by sending a mail message from the account you want subscribed to wxPython-dev-subscribe@lists.wxwindows.org. 2. I will go back to making prerelease binaries (and source snapshots) for a limited number of platforms and Python versions (probably only one or two binaries at a time) before making an official build and release. These will be announced on the wxPython-dev mail list, and issues from these should be reported back to the -dev group also. 3. I am especially interested in getting folks on board who are not afraid of getting sources from CVS and doing trial builds themselves on whatever platforms they have available. It would be nice if these people can also assist with making and testing the final binaries to help reduce the load on me at release time. 4. Final releases will be announced on wxPython-dev first just in case there are some last minute problems, then a day later on wxPython-users and then a day or two after that on forums outside of the community such as python-announce, FreshMeat, etc. 5. I promise to start using the spell checker in my mail software before sending release announcements! -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 16834 invoked from network); 13 Mar 2003 20:03:14 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 13 Mar 2003 20:03:14 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.81] by sunsite.dk (MessageWall 1.0.8) with SMTP; 13 Mar 2003 20:3:13 -0000 Received: from tulane.edu (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-2.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id ASS64117; Thu, 13 Mar 2003 08:17:35 -0800 (PST) Date: Thu, 13 Mar 2003 07:17:27 -0800 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: wxPython-dev@lists.wxwindows.org To: wxPython-users@lists.wxwindows.org From: Kevin Ollivier In-Reply-To: <3E6FC291.30307@alldunn.com> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.551) Subject: Re: [wxPython-users] New build/release policy Hi Robin, I think this sounds like a good strategy. I'm mostly working off CVS on Mac anyways, and I can set up my Windows build environment to use CVS as well. I could probably do builds and such as well, but I'd like to get comfortable with the process first. I actually will have to figure some of these things out when I do a pre-release of wxPython with wxMozilla anyways. ^_- Thanks, Kevin On Wednesday, March 12, 2003, at 03:28 PM, Robin Dunn wrote: > Hi all, > > First of all, sorry about the past few days. I'm being stretched thin > by a couple other big things right now and unfortunately it showed > through in the recent true/false issues. > > Secondly, the purpose of this mail is to outline a new policy that > I'll try to stick to for doing builds and releases in the future. > This will just be high level for now, but I expect to flesh it out > more and put a page or two on the wxPyWiki about it soon. > > 1. The wxPython-dev mail list has been created. I asked for it > before a number of people requested that development issues still be > discussed on the -users list, which I mostly agree with. So instead > of using this new list for discussing features and etc. I'd like to > use it for coordinating between myself and people who contribute code > to wxPython and also people who are willing to test prereleases of > wxPython. So... If you have contributed code to wxPython in the past > or plan to in the future, or are willing to test prerelease binaries > then please join the wxPython-dev list by sending a mail message from > the account you want subscribed to > wxPython-dev-subscribe@lists.wxwindows.org. > > 2. I will go back to making prerelease binaries (and source > snapshots) for a limited number of platforms and Python versions > (probably only one or two binaries at a time) before making an > official build and release. These will be announced on the > wxPython-dev mail list, and issues from these should be reported back > to the -dev group also. > > 3. I am especially interested in getting folks on board who are not > afraid of getting sources from CVS and doing trial builds themselves > on whatever platforms they have available. It would be nice if these > people can also assist with making and testing the final binaries to > help reduce the load on me at release time. > > 4. Final releases will be announced on wxPython-dev first just in > case there are some last minute problems, then a day later on > wxPython-users and then a day or two after that on forums outside of > the community such as python-announce, FreshMeat, etc. > > 5. I promise to start using the spell checker in my mail software > before sending release announcements! > > -- > Robin Dunn > Software Craftsman > http://wxPython.org Java give you jitters? Relax with wxPython! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org > For additional commands, e-mail: > wxPython-users-help@lists.wxwindows.org > > From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 839 invoked from network); 15 Mar 2003 03:36:30 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 15 Mar 2003 03:36:30 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.81] by sunsite.dk (MessageWall 1.0.8) with SMTP; 15 Mar 2003 3:36:29 -0000 Received: from dellPC (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-2.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id ASV11751; Fri, 14 Mar 2003 19:36:23 -0800 (PST) Message-ID: <008001c2eaa4$152e57d0$6701a8c0@dellPC> From: "Kevin Ollivier" To: Date: Fri, 14 Mar 2003 19:36:36 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: SWIG and dtors Hi all, I've created a .i file for wxMozilla and SWIGged it successfully. However, I've noticed that I get an access violation on shutdown when I add the ~wxMozillaBrowser dtor to the interface. (it happens when 'delete_wxMozillaBrowser(_arg0) is called) If I leave it out, everything seems to work fine. Looking over some of the other SWIG .i files for wxPython I've noticed that some modules do have their dtors listed, others don't. It seems that when shutting down, wxWindows calls the dtors for all child objects itself. (I noticed in the crash log that DeletePendingObjects was called before the crash.) Should dtors always be added to the SWIG interface files, or should this be omitted in most cases? I just want to make sure I'm not doing something really bad by leaving out the dtor. =) The good news is that up until shutdown, wxMozilla behaves just like it's wxWindows counterpart. :-) Thanks, Kevin From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 10734 invoked from network); 18 Mar 2003 21:40:54 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 18 Mar 2003 21:40:54 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 18 Mar 2003 21:40:53 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 037A64F55 for ; Tue, 18 Mar 2003 16:40:49 -0500 (EST) Message-ID: <3E779260.9080705@alldunn.com> Date: Tue, 18 Mar 2003 13:40:48 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <008001c2eaa4$152e57d0$6701a8c0@dellPC> In-Reply-To: <008001c2eaa4$152e57d0$6701a8c0@dellPC> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] SWIG and dtors Kevin Ollivier wrote: > Hi all, > > I've created a .i file for wxMozilla and SWIGged it successfully. However, > I've noticed that I get an access violation on shutdown when I add the > ~wxMozillaBrowser dtor to the interface. (it happens when > 'delete_wxMozillaBrowser(_arg0) is called) If I leave it out, everything > seems to work fine. > > Looking over some of the other SWIG .i files for wxPython I've noticed that > some modules do have their dtors listed, others don't. It seems that when > shutting down, wxWindows calls the dtors for all child objects itself. Yep. When a wxWindow is destroyed then it first destroys all it's children. In other words, the window "owns" the objects for the child windows and so it manages their lifetime. The python reference doesn't own the object any more so the easiest way to not have it deleted when the python object is destroyed is no not specify the C++ dtor to SWIG. > (I > noticed in the crash log that DeletePendingObjects was called before the > crash.) Should dtors always be added to the SWIG interface files, or should > this be omitted in most cases? I just want to make sure I'm not doing > something really bad by leaving out the dtor. =) Nope. Only specify them if there is no other object that will "own" the instances of a class. > > The good news is that up until shutdown, wxMozilla behaves just like it's > wxWindows counterpart. :-) Cool! -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 2414 invoked from network); 19 Mar 2003 02:21:02 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 19 Mar 2003 02:21:02 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.78] by sunsite.dk (MessageWall 1.0.8) with SMTP; 19 Mar 2003 2:21:2 -0000 Received: from tulane.edu (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-1.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id AVC94735; Tue, 18 Mar 2003 17:45:53 -0800 (PST) Date: Tue, 18 Mar 2003 17:46:06 -0800 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Kevin Ollivier To: wxpython-dev@lists.wxwindows.org Content-Transfer-Encoding: 7bit Message-Id: <8CC5EF8A-59AC-11D7-91BB-000393CB1C86@tulane.edu> X-Mailer: Apple Mail (2.551) Subject: Creating wxPython Installer Now that I know my SWIG dtor fix was a sound decision ;-), I'm gearing up to create an experimental "wxPython with wxMozilla" release to see how it fares in the wild. I'll probably confine it to Windows only at this point, just because even though the software is cross-platform, the process for building installers and makefiles is not. (Tools like cmake and tmake are starting to look VERY tempting...) So my question is: How is wxPython's Windows installer built at present? I played around with the various scripts in \distrib, and also tried using distutils but haven't been successful thus far. Before I tried to go any further on this, I thought I should first ask which method I should be using. ;-) Also, one related question to generating installers. Until I can figure out this dynamic loading business for Mozilla, on Windows at least I will need to add the GRE location to the user's PATH environment variable. (The GRE contains all the Mozilla DLLs and other files.) Is this considered a major no-no? I know it's not preferable, but I would be sure to add a note about it, of course. Any other solution would require DLLs to be distributed with wxPython and raise the package size by at least 2 MB. Thoughts? Thanks, Kevin P.S. for anyone who is interested, the real problem with dynamically loading Mozilla is the Netscape Portable Runtime. It is used internally by Mozilla to load helper DLLs, deal with memory allocation and threads, and do a bunch of other things. It's a large library (it has a 30 chapter manual on Mozilla.org) so I don't think any dynamic loading code will be trivial, especially since the NSPR is used extensively within Mozilla. (All approaches to dynamic loading I've seen require you to manually load each function you want to use.) I may take on this challenge one day, but right now my focus is on getting something that's usable for my own application, and hopefully for others' as well! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 3096 invoked from network); 19 Mar 2003 06:25:19 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 19 Mar 2003 06:25:19 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 19 Mar 2003 6:25:18 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id C204E4F55 for ; Wed, 19 Mar 2003 01:25:12 -0500 (EST) Message-ID: <3E780D48.8010507@alldunn.com> Date: Tue, 18 Mar 2003 22:25:12 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <8CC5EF8A-59AC-11D7-91BB-000393CB1C86@tulane.edu> In-Reply-To: <8CC5EF8A-59AC-11D7-91BB-000393CB1C86@tulane.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] Creating wxPython Installer Kevin Ollivier wrote: > > So my question is: How is wxPython's Windows installer built at present? Run the distrib/make_installer.py script. It builds some script files for InnoSetupExtensions and then runs it to make the installer. You can get ISX from http://www.wintax.nl/isx/, I am currently using version 2.0.18. I don't know if make_installer.py will be compatible with 3.x yet... -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 27925 invoked from network); 19 Mar 2003 17:39:25 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 19 Mar 2003 17:39:25 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.81] by sunsite.dk (MessageWall 1.0.8) with SMTP; 19 Mar 2003 17:39:25 -0000 Received: from tulane.edu (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-2.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id ATA57165; Wed, 19 Mar 2003 09:33:57 -0800 (PST) Date: Wed, 19 Mar 2003 09:34:13 -0800 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Kevin Ollivier To: wxPython-dev@lists.wxwindows.org Content-Transfer-Encoding: 7bit In-Reply-To: <3E780D48.8010507@alldunn.com> Message-Id: <0089B3CA-5A31-11D7-82C2-000393CB1C86@tulane.edu> X-Mailer: Apple Mail (2.551) Subject: Re: [wxPython-dev] Creating wxPython Installer On Tuesday, March 18, 2003, at 10:25 PM, Robin Dunn wrote: > Kevin Ollivier wrote: >> So my question is: How is wxPython's Windows installer built at >> present? > > Run the distrib/make_installer.py script. It builds some script files > for InnoSetupExtensions and then runs it to make the installer. You > can get ISX from http://www.wintax.nl/isx/, I am currently using > version 2.0.18. I don't know if make_installer.py will be compatible > with 3.x yet... I've been playing with it, and it's looking like the answer is no. :-( So far, the AlwaysCreateUninstallerIcon and CodeFile options are giving "undefined directive" errors. I think what I'll do is create a make_installer3.py script and see if I can get these issues resolved. Thanks, Kevin From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 210 invoked from network); 20 Mar 2003 07:11:46 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 07:11:46 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 7:11:45 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 148414F25 for ; Thu, 20 Mar 2003 02:11:36 -0500 (EST) Message-ID: <3E7969A6.60606@alldunn.com> Date: Wed, 19 Mar 2003 23:11:34 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: wxPython 2.4.0.7 preview Hi testers, I've put sources and a couple binaries of wxPython 2.4.0.7 p1 on SF in this group: http://sf.net/project/showfiles.php?group_id=10718&release_id=147616 Please download and test in a variety of situations. Other than the true/false thing and some other bug fixes nothing much has changed since .6 so I don't expect any new problems, but you never know... Here's the changes: 2.4.0.7 ------- Gave up on generating a warning upon the use of the old true/false or TRUE/FALSE values. Fixed wxGenericTreeCtrl (used on wxGTK and wxMac for wxTreeCtrl) so that it can successfully handle lots of nodes instead of overflowing when the virtual height of the widget overflowed a 16-bit value. Fixed the typemap that converts strings to wxColours to also accept unicode. Fixed problem where the wrong class name could sometimes be used for OOR. Fixed an interpreter lock problem in the __eq__ and __ne__ methods in wxSize and etc. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 1674 invoked from network); 20 Mar 2003 07:15:32 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 07:15:32 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 7:15:31 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 27CD74F25 for ; Thu, 20 Mar 2003 02:15:22 -0500 (EST) Message-ID: <3E796A89.70105@alldunn.com> Date: Wed, 19 Mar 2003 23:15:21 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <0089B3CA-5A31-11D7-82C2-000393CB1C86@tulane.edu> In-Reply-To: <0089B3CA-5A31-11D7-82C2-000393CB1C86@tulane.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] Creating wxPython Installer Kevin Ollivier wrote: > > On Tuesday, March 18, 2003, at 10:25 PM, Robin Dunn wrote: > >> Kevin Ollivier wrote: >> >>> So my question is: How is wxPython's Windows installer built at present? >> >> >> Run the distrib/make_installer.py script. It builds some script files >> for InnoSetupExtensions and then runs it to make the installer. You >> can get ISX from http://www.wintax.nl/isx/, I am currently using >> version 2.0.18. I don't know if make_installer.py will be compatible >> with 3.x yet... > > > I've been playing with it, and it's looking like the answer is no. :-( > So far, the AlwaysCreateUninstallerIcon and CodeFile options are giving > "undefined directive" errors. I think what I'll do is create a > make_installer3.py script and see if I can get these issues resolved. > Or I can send you the 2.0.18 version... -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 17924 invoked from network); 20 Mar 2003 15:12:10 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 15:12:10 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.78] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 15:12:10 -0000 Received: from tulane.edu (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-1.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id AVF60220; Thu, 20 Mar 2003 07:12:08 -0800 (PST) Date: Thu, 20 Mar 2003 07:12:22 -0800 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Kevin Ollivier To: wxPython-dev@lists.wxwindows.org Content-Transfer-Encoding: 7bit In-Reply-To: <3E796A89.70105@alldunn.com> Message-Id: <598ECFF2-5AE6-11D7-82C2-000393CB1C86@tulane.edu> X-Mailer: Apple Mail (2.551) Subject: Re: [wxPython-dev] Creating wxPython Installer On Wednesday, March 19, 2003, at 11:15 PM, Robin Dunn wrote: > Kevin Ollivier wrote: >> On Tuesday, March 18, 2003, at 10:25 PM, Robin Dunn wrote: >>> Kevin Ollivier wrote: >>> >>>> So my question is: How is wxPython's Windows installer built at >>>> present? >>> >>> >>> Run the distrib/make_installer.py script. It builds some script >>> files for InnoSetupExtensions and then runs it to make the >>> installer. You can get ISX from http://www.wintax.nl/isx/, I am >>> currently using version 2.0.18. I don't know if make_installer.py >>> will be compatible with 3.x yet... >> I've been playing with it, and it's looking like the answer is no. >> :-( So far, the AlwaysCreateUninstallerIcon and CodeFile options are >> giving "undefined directive" errors. I think what I'll do is create a >> make_installer3.py script and see if I can get these issues resolved. > > Or I can send you the 2.0.18 version... This would work too, if you don't mind. =) Thanks, Kevin From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 23224 invoked from network); 20 Mar 2003 17:18:47 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 17:18:47 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [63.231.195.112] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 17:18:47 -0000 Received: (qmail 30046 invoked by uid 0); 20 Mar 2003 17:18:44 -0000 Received: from unknown (63.231.195.1) by mpls-qmqp-01.inet.qwest.net with QMQP; 20 Mar 2003 17:18:44 -0000 Received: from gamer.semi-retired.com (HELO gamer) (63.225.95.173) by mpls-pop-01.inet.qwest.net with SMTP; 20 Mar 2003 17:18:42 -0000 Date: Thu, 20 Mar 2003 09:21:38 -0800 Message-ID: From: "Kevin Altis" To: wxPython-dev@lists.wxwindows.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3E7969A6.60606@alldunn.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 Subject: RE: [wxPython-dev] wxPython 2.4.0.7 preview So far I haven't seen any issues using Python 2.2.2 and wxPython 2.4.0.7 on Windows 2000. I no longer have Python 2.1.x, 2.2, or 2.2.1. I'm assuming that True/False problems would manifest themselves with 2.1.x and 2.2. One thing I'm wondering about is whether previous versions of 2.4.0.x should be hidden on the download page if in fact we have some API differences and behavior changes from 2.4.0.2. The large number of downloads of wxPythonGTK-py2.2-2.4.0.2-2.i386.rpm is most likely a SF reporting error or some sort of bot. Most of the downloads for that RPM occurred on February 22nd http://sourceforge.net/project/stats/index.php?report=last_30&group_id=10718 Anyway, it is important that 2.4.x be stable from now on. We've had a number of hiccups from my removal of import string which caused breakage for projects like Boa that assumed modules would be available because it used "from wxPython.wx import *" to the latest True/False changes. There were also some behavioral changes mentioned, at least on Linux, if I remember correctly. Comments? It would also be nice to document in one place the API and behavioral changes from 2.3.x to 2.4.x to encourage people to upgrade. We've taken the first steps to build trust in future releases of wxPython, so what else do we need to do? ka > -----Original Message----- > From: Robin Dunn [mailto:robin@alldunn.com] > Sent: Wednesday, March 19, 2003 11:12 PM > To: wxPython-dev@lists.wxwindows.org > Subject: [wxPython-dev] wxPython 2.4.0.7 preview > > > Hi testers, > > I've put sources and a couple binaries of wxPython 2.4.0.7 p1 on SF in > this group: > http://sf.net/project/showfiles.php?group_id=10718&release_id=147616 > > Please download and test in a variety of situations. Other than the > true/false thing and some other bug fixes nothing much has changed since > .6 so I don't expect any new problems, but you never know... > > Here's the changes: > > 2.4.0.7 > ------- > Gave up on generating a warning upon the use of the old true/false or > TRUE/FALSE values. > > Fixed wxGenericTreeCtrl (used on wxGTK and wxMac for wxTreeCtrl) so > that it can successfully handle lots of nodes instead of overflowing > when the virtual height of the widget overflowed a 16-bit value. > > Fixed the typemap that converts strings to wxColours to also accept > unicode. > > Fixed problem where the wrong class name could sometimes be used for > OOR. > > Fixed an interpreter lock problem in the __eq__ and __ne__ methods in > wxSize and etc. > > > > -- > Robin Dunn > Software Craftsman > http://wxPython.org Java give you jitters? Relax with wxPython! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org > For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org > > From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 12811 invoked from network); 20 Mar 2003 21:08:31 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 21:08:31 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.81] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 21:8:29 -0000 Received: from tulane.edu (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-2.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id ATD03115; Thu, 20 Mar 2003 13:07:14 -0800 (PST) Date: Thu, 20 Mar 2003 13:07:27 -0800 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Kevin Ollivier To: wxPython-dev@lists.wxwindows.org Content-Transfer-Encoding: 7bit In-Reply-To: <3E7969A6.60606@alldunn.com> Message-Id: X-Mailer: Apple Mail (2.551) Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview Hi Robin, I tested this release against the demo and my own app, and all seems OK. I used an old version of my app from November to ensure that I hadn't changed any of the true/false values, etc. Looks good from this end! Thanks, Kevin On Wednesday, March 19, 2003, at 11:11 PM, Robin Dunn wrote: > Hi testers, > > I've put sources and a couple binaries of wxPython 2.4.0.7 p1 on SF in > this group: > http://sf.net/project/showfiles.php?group_id=10718&release_id=147616 > > Please download and test in a variety of situations. Other than the > true/false thing and some other bug fixes nothing much has changed > since .6 so I don't expect any new problems, but you never know... > > Here's the changes: > > 2.4.0.7 > ------- > Gave up on generating a warning upon the use of the old true/false or > TRUE/FALSE values. > > Fixed wxGenericTreeCtrl (used on wxGTK and wxMac for wxTreeCtrl) so > that it can successfully handle lots of nodes instead of overflowing > when the virtual height of the widget overflowed a 16-bit value. > > Fixed the typemap that converts strings to wxColours to also accept > unicode. > > Fixed problem where the wrong class name could sometimes be used for > OOR. > > Fixed an interpreter lock problem in the __eq__ and __ne__ methods in > wxSize and etc. > > > > -- > Robin Dunn > Software Craftsman > http://wxPython.org Java give you jitters? Relax with wxPython! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org > For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org > > From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 29225 invoked from network); 20 Mar 2003 21:43:56 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 21:43:56 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.74] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 21:43:55 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18w7pK-0002KS-00 for wxPython-dev@lists.wxwindows.org; Thu, 20 Mar 2003 13:43:54 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id AC0C04E84; Thu, 20 Mar 2003 15:44:42 -0600 (CST) To: wxPython-dev@lists.wxwindows.org References: <3E7969A6.60606@alldunn.com> From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 20 Mar 2003 15:44:42 -0600 In-Reply-To: <3E7969A6.60606@alldunn.com> Message-ID: Lines: 22 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview Robin Dunn writes: > Here's the changes: > > 2.4.0.7 > ------- > Gave up on generating a warning upon the use of the old true/false or > TRUE/FALSE values. > > Fixed wxGenericTreeCtrl (used on wxGTK and wxMac for wxTreeCtrl) so > that it can successfully handle lots of nodes instead of overflowing > when the virtual height of the widget overflowed a 16-bit value. I like being able to scroll through the whole wx namespace in the PyFilling tree. Nice fix! -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 12052 invoked from network); 20 Mar 2003 22:14:05 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 22:14:05 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 22:14:4 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 75EE74EA2 for ; Thu, 20 Mar 2003 17:13:52 -0500 (EST) Message-ID: <3E7A3D20.6040509@alldunn.com> Date: Thu, 20 Mar 2003 14:13:52 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview Kevin Ollivier wrote: > Hi Robin, > > I tested this release against the demo and my own app, and all seems OK. > I used an old version of my app from November to ensure that I hadn't > changed any of the true/false values, etc. Looks good from this end! > Unless somebody comes up with a showstopper in the meantime I plan on starting to build final binaries tomorrow. Are there any contribs that still need to be updated? Patrick has there been any changes to PyCrust since the version I have now (0.9b I think)? BTW, I don't know if Roman is on this list or not, but I just got some updates for XRCed that are real awesome! Good job! -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 21606 invoked from network); 20 Mar 2003 22:34:34 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 22:34:34 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [63.231.195.114] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 22:34:34 -0000 Received: (qmail 99566 invoked by uid 0); 20 Mar 2003 22:33:55 -0000 Received: from mpls-pop-03.inet.qwest.net (63.231.195.3) by mpls-qmqp-03.inet.qwest.net with QMQP; 20 Mar 2003 22:33:55 -0000 Received: from gamer.semi-retired.com (HELO gamer) (63.225.95.173) by mpls-pop-03.inet.qwest.net with SMTP; 20 Mar 2003 22:34:32 -0000 Date: Thu, 20 Mar 2003 14:37:28 -0800 Message-ID: From: "Kevin Altis" To: wxPython-dev@lists.wxwindows.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <3E7A3D20.6040509@alldunn.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 Subject: RE: [wxPython-dev] wxPython 2.4.0.7 preview > From: Robin Dunn [mailto:robin@alldunn.com] > > Kevin Ollivier wrote: > > Hi Robin, > > > > I tested this release against the demo and my own app, and all > seems OK. > > I used an old version of my app from November to ensure that I hadn't > > changed any of the true/false values, etc. Looks good from this end! > > > > Unless somebody comes up with a showstopper in the meantime I plan on > starting to build final binaries tomorrow. Just as a logistical point it seems like it would be best if the installers we test are the actual distributions that will be made public, only the name of the actual installer file should be different and maybe not even that. If you end up having to make yet another build after initial tests then that is more work for you, it introduces the possibility of changes and errors and it introduces at least another day in the release process without any real benefits. Once you freeze a release for testing there shouldn't be any changes to cvs in the release tree until the public release unless a bug is identified and fixed which would start the pre-release check process over. It is partly the "minor tweaks" that got us into trouble earlier. Does that make sense? > Are there any contribs that still need to be updated? Patrick has there > been any changes to PyCrust since the version I have now (0.9b I think)? > > BTW, I don't know if Roman is on this list or not, but I just got some > updates for XRCed that are real awesome! Good job! Only Patrick, Kevin, and I reported in. Are we the only ones besides Robin doing any checks? ka From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 28103 invoked from network); 20 Mar 2003 22:50:40 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 22:50:40 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.126] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 22:50:40 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by turkey.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18w8ru-0001d2-00 for wxPython-dev@lists.wxwindows.org; Thu, 20 Mar 2003 14:50:38 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id B55024E84; Thu, 20 Mar 2003 16:51:22 -0600 (CST) To: wxPython-dev@lists.wxwindows.org References: <3E7A3D20.6040509@alldunn.com> From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 20 Mar 2003 16:51:22 -0600 In-Reply-To: <3E7A3D20.6040509@alldunn.com> Message-ID: Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview Robin Dunn writes: > Are there any contribs that still need to be updated? Patrick has > there been any changes to PyCrust since the version I have now (0.9b I > think)? Yes, including some changes to keep compatible with Python 2.1. So get the latest from CVS. Actually, since this may be a stable release for a while, I may drop the letter from the version and consider this 0.9 final. In fact, I just did and I also tagged the files: cvs tag PyCrust-0-9 Thanks. -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 29085 invoked from network); 20 Mar 2003 22:52:26 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 22:52:26 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.46] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 22:52:25 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by grebe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18w8qH-0004Mr-00 for wxPython-dev@lists.wxwindows.org; Thu, 20 Mar 2003 14:48:57 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id 375CA4E84; Thu, 20 Mar 2003 16:49:41 -0600 (CST) To: wxPython-dev@lists.wxwindows.org References: From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 20 Mar 2003 16:49:41 -0600 In-Reply-To: Message-ID: Lines: 52 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview "Kevin Altis" writes: > > From: Robin Dunn [mailto:robin@alldunn.com] > > > > Unless somebody comes up with a showstopper in the meantime I plan on > > starting to build final binaries tomorrow. > > Just as a logistical point it seems like it would be best if the installers > we test are the actual distributions that will be made public, only the name > of the actual installer file should be different and maybe not even that. If > you end up having to make yet another build after initial tests then that is > more work for you, it introduces the possibility of changes and errors and > it introduces at least another day in the release process without any real > benefits. > > Once you freeze a release for testing there shouldn't be any changes to cvs > in the release tree until the public release unless a bug is identified and > fixed which would start the pre-release check process over. > > It is partly the "minor tweaks" that got us into trouble earlier. > > Does that make sense? Yes, and I agree. Here is what I'd like to see happen. I'd like to see a message saying you intend to do a release and we have X amount of time (one day?) to submit any changes. That gives me time to finalize any PyCrust stuff and make sure it is clean and ready to ship. I also like to tag the files in CVS with the version number. For example, I just did this: cvs tag PyCrust-0-9 That gives you a marker to work with and lets me know exactly what version of the files are going into wxPython. At the appointed hour you build the release and let us know about it. We download and test it. After some period of time without problems, you make a simple name change and release it to the wxPython community at large. If there are problems, we repeat this process. I also plan to rig CVS to send email to a PyCrust-cvs list so that you and others have a better idea when commits take place in the PyCrust CVS repository. How does that sound? (Hopefully not too burdensome.) -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 2586 invoked from network); 20 Mar 2003 22:58:19 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 22:58:19 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 22:58:18 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 813C24EA2 for ; Thu, 20 Mar 2003 17:58:06 -0500 (EST) Message-ID: <3E7A477E.1090807@alldunn.com> Date: Thu, 20 Mar 2003 14:58:06 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview Kevin Altis wrote: > > Just as a logistical point it seems like it would be best if the installers > we test are the actual distributions that will be made public, only the name > of the actual installer file should be different and maybe not even that. If > you end up having to make yet another build after initial tests then that is > more work for you, it introduces the possibility of changes and errors and > it introduces at least another day in the release process without any real > benefits. That thought crossed my mind too, but for the most part my build scripts get the version number for the file names from the same place that wxPython gets it from, setup.py. That can be changed for some of them, but the RPMs need to use the real version number. So what I decided to do instead is use the p1,p2,... suffix on the preview releases and then the release cantidate (only one of them if all goes well) will use the real version number. The release cantidate will have all binaries built, but the previews will just be one or two binaries to help reduce the load. Since the builds are almost fully automated doing a rebuild with only a version number change should result in an otherwise identical binary. > > Once you freeze a release for testing there shouldn't be any changes to cvs > in the release tree until the public release unless a bug is identified and > fixed which would start the pre-release check process over. Yep. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 13448 invoked from network); 20 Mar 2003 23:19:00 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 23:19:00 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [63.231.195.112] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 23:19:0 -0000 Received: (qmail 49723 invoked by uid 0); 20 Mar 2003 23:18:59 -0000 Received: from unknown (63.231.195.1) by mpls-qmqp-01.inet.qwest.net with QMQP; 20 Mar 2003 23:18:59 -0000 Received: from gamer.semi-retired.com (HELO gamer) (63.225.95.173) by mpls-pop-01.inet.qwest.net with SMTP; 20 Mar 2003 23:18:58 -0000 Date: Thu, 20 Mar 2003 15:21:54 -0800 Message-ID: From: "Kevin Altis" To: wxPython-dev@lists.wxwindows.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <3E7A477E.1090807@alldunn.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 Subject: RE: [wxPython-dev] wxPython 2.4.0.7 preview > From: Robin Dunn > > Kevin Altis wrote: > > > > Just as a logistical point it seems like it would be best if > the installers > > we test are the actual distributions that will be made public, > only the name > > of the actual installer file should be different and maybe not > even that. If > > you end up having to make yet another build after initial tests > then that is > > more work for you, it introduces the possibility of changes and > errors and > > it introduces at least another day in the release process > without any real > > benefits. > > That thought crossed my mind too, but for the most part my build scripts > get the version number for the file names from the same place that > wxPython gets it from, setup.py. That can be changed for some of them, > but the RPMs need to use the real version number. > > So what I decided to do instead is use the p1,p2,... suffix on the > preview releases and then the release cantidate (only one of them if all > goes well) will use the real version number. The release cantidate will > have all binaries built, but the previews will just be one or two > binaries to help reduce the load. > > Since the builds are almost fully automated doing a rebuild with only a > version number change should result in an otherwise identical binary. Hmm, that isn't giving me a warm fuzzy feeling. So what if you just use the real numbers, and only make the binaries available from the alldunn.com server? There will never be p1, p2, etc. suffixes. If we need to tell the difference between a 2.4.0.7 made yesterday and another today (after a bug fix), the file size as well as a MD5 or other signature would let us testing fools know what we're dealing with. ka From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 13793 invoked from network); 20 Mar 2003 23:19:59 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 23:19:59 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [209.184.81.195] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 23:19:58 -0000 Received: from ganymede ([10.144.8.102]) by jfadev.ntdomain.us.tpnet.intra (8.12.8/8.12.8) with SMTP id h2KNK5ko008896 for ; Thu, 20 Mar 2003 17:20:06 -0600 Message-ID: <085701c2ef37$5e8cf110$5408900a@ganymede> From: "Riaan Booysen" To: References: <3E7969A6.60606@alldunn.com> Date: Thu, 20 Mar 2003 17:20:59 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview Hi Robin and wxPy-Devers, > Hi testers, > > I've put sources and a couple binaries of wxPython 2.4.0.7 p1 on SF in > this group: > http://sf.net/project/showfiles.php?group_id=10718&release_id=147616 > > Please download and test in a variety of situations. Other than the > true/false thing and some other bug fixes nothing much has changed since > .6 so I don't expect any new problems, but you never know... I've been using 2.4.0.7p1 with Boa the whole of today and everything works great for me too so far. I can also confirm that the typemap issues are fixed. Thanks, Riaan. From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 21656 invoked from network); 20 Mar 2003 23:35:55 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 20 Mar 2003 23:35:55 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.123] by sunsite.dk (MessageWall 1.0.8) with SMTP; 20 Mar 2003 23:35:54 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by swan.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18w9Zh-00016x-00 for wxPython-dev@lists.wxwindows.org; Thu, 20 Mar 2003 15:35:53 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id 429BF4E84; Thu, 20 Mar 2003 17:36:36 -0600 (CST) To: wxPython-dev@lists.wxwindows.org References: From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 20 Mar 2003 17:36:36 -0600 In-Reply-To: Message-ID: Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview pobrien@orbtech.com (Patrick K. O'Brien) writes: > I also plan to rig CVS to send email to a PyCrust-cvs list so that you > and others have a better idea when commits take place in the PyCrust > CVS repository. This is done. The list info is available here: http://lists.sourceforge.net/lists/listinfo/pycrust-cvs Please subscribe if you want to be notified of PyCrust cvs commits. -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 9763 invoked from network); 21 Mar 2003 00:20:37 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 00:20:37 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 0:20:37 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 0E5734EA2 for ; Thu, 20 Mar 2003 19:20:25 -0500 (EST) Message-ID: <3E7A5AC8.7020503@alldunn.com> Date: Thu, 20 Mar 2003 16:20:24 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview Kevin Altis wrote: >>That thought crossed my mind too, but for the most part my build scripts >>get the version number for the file names from the same place that >>wxPython gets it from, setup.py. That can be changed for some of them, >>but the RPMs need to use the real version number. >> >>So what I decided to do instead is use the p1,p2,... suffix on the >>preview releases and then the release cantidate (only one of them if all >>goes well) will use the real version number. The release cantidate will >>have all binaries built, but the previews will just be one or two >>binaries to help reduce the load. >> >>Since the builds are almost fully automated doing a rebuild with only a >>version number change should result in an otherwise identical binary. > > > Hmm, that isn't giving me a warm fuzzy feeling. So what if you just use the > real numbers, and only make the binaries available from the alldunn.com > server? There will never be p1, p2, etc. suffixes. If we need to tell the > difference between a 2.4.0.7 made yesterday and another today (after a bug > fix), the file size as well as a MD5 or other signature would let us testing > fools know what we're dealing with. My one worry with this is that after the final release there will be no way to tell at runtime the difference between the final release and an eary preview release (other than the bugs that were fixed for the final.) I expect that it could lead to unnecessary confusion. Perhaps another possibility is to always increment the micro-micro (or is it "nano"? :-) number for each build, preview and final. So the build I do tomorrow will be 2.4.0.8, will get put on alldunn.com and then will go up to SF if no problems are reported. Any other ideas? -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 17577 invoked from network); 21 Mar 2003 00:41:14 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 00:41:14 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.50] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 0:41:13 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18wAau-00021a-00 for wxPython-dev@lists.wxwindows.org; Thu, 20 Mar 2003 16:41:12 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id CA9DF4E84; Thu, 20 Mar 2003 18:41:52 -0600 (CST) To: wxPython-dev From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 20 Mar 2003 18:41:52 -0600 Message-ID: Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: wx package What would you say to the idea of distributing my wx package with wxPython? My thinking is this. If we want to post examples of the new syntax, or convert the demo, or convert PyCrust, we need users to have the new wx package installed. If wxPython installs it automatically, they don't have to do a thing. And it won't conflict with existing code. Sure, it's a tiny bit slower because it's creating the new namespace dynamically, but it's simple, it works, it's complete, and it's available now. Apparently there was a recent discussion among the wxWindows folks and it looks like their plan is to have one big wx namespace with the wx prefix dropped. So our new package is a perfect transition. Thoughts? -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 18576 invoked from network); 21 Mar 2003 00:44:44 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 00:44:44 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 0:44:44 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id B076D4EA2 for ; Thu, 20 Mar 2003 19:44:31 -0500 (EST) Message-ID: <3E7A606F.2060509@alldunn.com> Date: Thu, 20 Mar 2003 16:44:31 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] wx package Patrick K. O'Brien wrote: > What would you say to the idea of distributing my wx package with > wxPython? My thinking is this. If we want to post examples of the new > syntax, or convert the demo, or convert PyCrust, we need users to have > the new wx package installed. If wxPython installs it automatically, > they don't have to do a thing. And it won't conflict with existing > code. Sure, it's a tiny bit slower because it's creating the new > namespace dynamically, but it's simple, it works, it's complete, and > it's available now. > > Apparently there was a recent discussion among the wxWindows folks and > it looks like their plan is to have one big wx namespace with the wx > prefix dropped. So our new package is a perfect transition. > > Thoughts? > My current plan is to discuss it one more time on the -users list and then add it to the release after this one. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 22541 invoked from network); 21 Mar 2003 00:56:42 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 00:56:42 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.62] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 0:56:41 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by snipe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18wAps-0001eh-00 for wxPython-dev@lists.wxwindows.org; Thu, 20 Mar 2003 16:56:40 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id 2F1E64E84; Thu, 20 Mar 2003 18:57:18 -0600 (CST) To: wxPython-dev@lists.wxwindows.org References: <3E7A606F.2060509@alldunn.com> From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 20 Mar 2003 18:57:18 -0600 In-Reply-To: <3E7A606F.2060509@alldunn.com> Message-ID: Lines: 33 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [wxPython-dev] wx package Robin Dunn writes: > Patrick K. O'Brien wrote: > > What would you say to the idea of distributing my wx package with > > wxPython? My thinking is this. If we want to post examples of the new > > syntax, or convert the demo, or convert PyCrust, we need users to have > > the new wx package installed. If wxPython installs it automatically, > > they don't have to do a thing. And it won't conflict with existing > > code. Sure, it's a tiny bit slower because it's creating the new > > namespace dynamically, but it's simple, it works, it's complete, and > > it's available now. > > Apparently there was a recent discussion among the wxWindows folks > > and > > it looks like their plan is to have one big wx namespace with the wx > > prefix dropped. So our new package is a perfect transition. > > Thoughts? > > > > My current plan is to discuss it one more time on the -users list and > then add it to the release after this one. Okay, good. (I can't wait to see how much "concern" that stirs up.) BTW, when your code is going to appear in a book that limits you to a width of 68 characters you really start to appreciate not having the wx prefix. ;-) -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 2516 invoked from network); 21 Mar 2003 01:25:43 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 01:25:43 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.81] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 1:25:43 -0000 Received: from dellPC (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-2.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id ATD40030; Thu, 20 Mar 2003 17:23:50 -0800 (PST) Message-ID: <013c01c2ef48$8af63430$6701a8c0@dellPC> From: "Kevin Ollivier" To: References: <3E7A5AC8.7020503@alldunn.com> Date: Thu, 20 Mar 2003 17:23:56 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview ----- Original Message ----- From: "Robin Dunn" To: Sent: Thursday, March 20, 2003 4:20 PM Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview > Kevin Altis wrote: [snip] > > Hmm, that isn't giving me a warm fuzzy feeling. So what if you just use the > > real numbers, and only make the binaries available from the alldunn.com > > server? There will never be p1, p2, etc. suffixes. If we need to tell the > > difference between a 2.4.0.7 made yesterday and another today (after a bug > > fix), the file size as well as a MD5 or other signature would let us testing > > fools know what we're dealing with. > > My one worry with this is that after the final release there will be no > way to tell at runtime the difference between the final release and an > eary preview release (other than the bugs that were fixed for the > final.) I expect that it could lead to unnecessary confusion. > > Perhaps another possibility is to always increment the micro-micro (or > is it "nano"? :-) number for each build, preview and final. So the > build I do tomorrow will be 2.4.0.8, will get put on alldunn.com and > then will go up to SF if no problems are reported. > > Any other ideas? I personally like the p1, p2 approach best, because the different naming scheme highlights that it is a preview release. I think whatever system we choose, there should be some easy and consistent way to differentiate between preview and final releases. I think incrementing the microscopic ;-) build number could confuse people not familiar with the build system, as (for example) 2.4.0.8-10 could be previews, and 2.4.0.11 could be a final. Just looking at the number does not give a clear indication of what type of build it is. I think that as long as any "final-final" release gets a quick runthrough by testers before it is made official, there is very little chance of surprises getting introduced into a final release. I personally have found that having someone else look at my code before sending it to 'the presses' uncovers most problems rather quickly (especially if you have change notes for people to review when testing), and any bug that cannot be uncovered by these tests probably is rare enough that it will take a very specific set of circumstances to uncover it. I think even our current approach of peer review makes great strides towards ensuring that no unexpected surprises make it into the final builds. My only concern is if we're getting a good coverage of the different platforms at this point. Kevin A and I are both testing on Windows (2000 and XP), and I'm not sure what platforms the other two testers have been working on. Thanks, Kevin From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 7722 invoked from network); 21 Mar 2003 01:40:29 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 01:40:29 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.120] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 1:40:28 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by albatross.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18wBWD-0005ui-00 for wxPython-dev@lists.wxwindows.org; Thu, 20 Mar 2003 17:40:25 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id 176C94E84; Thu, 20 Mar 2003 19:41:03 -0600 (CST) To: wxPython-dev@lists.wxwindows.org References: <3E7A5AC8.7020503@alldunn.com> <013c01c2ef48$8af63430$6701a8c0@dellPC> From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 20 Mar 2003 19:41:03 -0600 In-Reply-To: <013c01c2ef48$8af63430$6701a8c0@dellPC> Message-ID: Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview "Kevin Ollivier" writes: > I think even our current approach of peer review makes great strides towards > ensuring that no unexpected surprises make it into the final builds. My only > concern is if we're getting a good coverage of the different platforms at > this point. Kevin A and I are both testing on Windows (2000 and XP), and I'm > not sure what platforms the other two testers have been working on. My daily platform is Python 2.2.2 on Mandrake 9.0. Sometimes I boot into Win98 and test with Python 2.2.2 and 2.1.3. But I'm growing tired of maintaining compatibility with Python 2.1.3 and look forward to the day I can drop it. Any idea how many Python 2.1 users we've got versus 2.2 users? -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 11720 invoked from network); 21 Mar 2003 01:50:38 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 01:50:38 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 1:50:37 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 088704EC0 for ; Thu, 20 Mar 2003 20:50:25 -0500 (EST) Message-ID: <3E7A6FE0.5000509@alldunn.com> Date: Thu, 20 Mar 2003 17:50:24 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <3E7A5AC8.7020503@alldunn.com> <013c01c2ef48$8af63430$6701a8c0@dellPC> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview Patrick K. O'Brien wrote: > My daily platform is Python 2.2.2 on Mandrake 9.0. Sometimes I boot > into Win98 and test with Python 2.2.2 and 2.1.3. But I'm growing tired > of maintaining compatibility with Python 2.1.3 and look forward to the > day I can drop it. When 2.3 is released > > Any idea how many Python 2.1 users we've got versus 2.2 users? > A very quick guess based on download stats, 2.1 has roughly 10-20% the numbers of 2.2. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 8337 invoked from network); 21 Mar 2003 14:41:47 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 14:41:47 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.176.167.10] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 14:41:46 -0000 Received: from chl0151.edmonton.computronix.com (CHL0151 [206.75.5.250]) by ALPHA.computronix.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id HKCKRM5Y; Fri, 21 Mar 2003 07:42:12 -0700 From: Anthony Tuininga To: wxPython-dev@lists.wxwindows.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 21 Mar 2003 07:43:48 -0700 Message-Id: <1048257829.24815.125.camel@chl0151.edmonton.computronix.com> Mime-Version: 1.0 Subject: Re: [wxPython-dev] wx package Sounds good to me. It provides a means for people to try out the new method in the 2.4 series without breaking any existing code. About the question of incrementing the 4th position for each preview release: it sounds like a good idea to me. In fact, the very fact that the numbers to the general public will look like this 2.4.0.6 2.4.0.8 2.4.0.12 or something similar will let people know how many releases they didn't even have to bother installing.... :-) In other words, it lets people know that the stability issue is important. My 2 cents... :-) On Thu, 2003-03-20 at 17:41, Patrick K. O'Brien wrote: > What would you say to the idea of distributing my wx package with > wxPython? My thinking is this. If we want to post examples of the new > syntax, or convert the demo, or convert PyCrust, we need users to have > the new wx package installed. If wxPython installs it automatically, > they don't have to do a thing. And it won't conflict with existing > code. Sure, it's a tiny bit slower because it's creating the new > namespace dynamically, but it's simple, it works, it's complete, and > it's available now. > > Apparently there was a recent discussion among the wxWindows folks and > it looks like their plan is to have one big wx namespace with the wx > prefix dropped. So our new package is a perfect transition. > > Thoughts? > > -- > Patrick K. O'Brien > Orbtech http://www.orbtech.com/web/pobrien > ----------------------------------------------- > "Your source for Python programming expertise." > ----------------------------------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org > For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org -- Anthony Tuininga anthony@computronix.com Computronix Distinctive Software. Real People. Suite 200, 10216 - 124 Street NW Edmonton, AB, Canada T5N 4A3 Phone: (780) 454-3700 Fax: (780) 454-3838 http://www.computronix.com From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 11267 invoked from network); 21 Mar 2003 14:46:49 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 14:46:49 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.176.167.10] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 14:46:48 -0000 Received: from chl0151.edmonton.computronix.com (CHL0151 [206.75.5.250]) by ALPHA.computronix.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id HKCKRM6H; Fri, 21 Mar 2003 07:47:15 -0700 From: Anthony Tuininga To: wxPython-dev@lists.wxwindows.org In-Reply-To: <013c01c2ef48$8af63430$6701a8c0@dellPC> References: <3E7A5AC8.7020503@alldunn.com> <013c01c2ef48$8af63430$6701a8c0@dellPC> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 21 Mar 2003 07:48:51 -0700 Message-Id: <1048258132.24815.130.camel@chl0151.edmonton.computronix.com> Mime-Version: 1.0 Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview On Thu, 2003-03-20 at 18:23, Kevin Ollivier wrote: > > ----- Original Message ----- > From: "Robin Dunn" > To: > Sent: Thursday, March 20, 2003 4:20 PM > Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview > > > > Kevin Altis wrote: > [snip] > > > > Hmm, that isn't giving me a warm fuzzy feeling. So what if you just use > the > > > real numbers, and only make the binaries available from the alldunn.com > > > server? There will never be p1, p2, etc. suffixes. If we need to tell > the > > > difference between a 2.4.0.7 made yesterday and another today (after a > bug > > > fix), the file size as well as a MD5 or other signature would let us > testing > > > fools know what we're dealing with. > > > > My one worry with this is that after the final release there will be no > > way to tell at runtime the difference between the final release and an > > eary preview release (other than the bugs that were fixed for the > > final.) I expect that it could lead to unnecessary confusion. > > > > Perhaps another possibility is to always increment the micro-micro (or > > is it "nano"? :-) number for each build, preview and final. So the > > build I do tomorrow will be 2.4.0.8, will get put on alldunn.com and > > then will go up to SF if no problems are reported. > > > > Any other ideas? > > I personally like the p1, p2 approach best, because the different naming > scheme highlights that it is a preview release. I think whatever system we > choose, there should be some easy and consistent way to differentiate > between preview and final releases. I think incrementing the microscopic ;-) > build number could confuse people not familiar with the build system, as > (for example) 2.4.0.8-10 could be previews, and 2.4.0.11 could be a final. > Just looking at the number does not give a clear indication of what type of > build it is. Well, the whole question is: when do you know that you have a final? And how do you differentiate between three different "what we thought were finals" which turned out not to be? Do you have to rebuild everything with a different "branding"? At my work we have gone through the same issues for our product and have decided that a build # or timestamp is needed for differentiating between different versions and the number (2.4.0.8) for example is kept the same throughout the release. Perhaps that is another idea? 2.4.0.7 (Build #4) 2.4.0.7 (Built 2003-03-21 07:44:25) Or some variation of that? > I think that as long as any "final-final" release gets a quick runthrough by > testers before it is made official, there is very little chance of surprises > getting introduced into a final release. I personally have found that having > someone else look at my code before sending it to 'the presses' uncovers > most problems rather quickly (especially if you have change notes for people > to review when testing), and any bug that cannot be uncovered by these tests > probably is rare enough that it will take a very specific set of > circumstances to uncover it. > > I think even our current approach of peer review makes great strides towards > ensuring that no unexpected surprises make it into the final builds. My only > concern is if we're getting a good coverage of the different platforms at > this point. Kevin A and I are both testing on Windows (2000 and XP), and I'm > not sure what platforms the other two testers have been working on. > > Thanks, > > Kevin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org > For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org -- Anthony Tuininga anthony@computronix.com Computronix Distinctive Software. Real People. Suite 200, 10216 - 124 Street NW Edmonton, AB, Canada T5N 4A3 Phone: (780) 454-3700 Fax: (780) 454-3838 http://www.computronix.com From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 21207 invoked from network); 21 Mar 2003 16:18:41 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 16:18:41 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.78] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 16:18:41 -0000 Received: from dellPC (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-1.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id AVH03760; Fri, 21 Mar 2003 08:18:38 -0800 (PST) Message-ID: <018701c2efc5$8cbeb760$6701a8c0@dellPC> From: "Kevin Ollivier" To: References: <3E7A5AC8.7020503@alldunn.com> <013c01c2ef48$8af63430$6701a8c0@dellPC> <1048258132.24815.130.camel@chl0151.edmonton.computronix.com> Date: Fri, 21 Mar 2003 08:18:46 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview ----- Original Message ----- From: "Anthony Tuininga" To: Sent: Friday, March 21, 2003 6:48 AM Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview > On Thu, 2003-03-20 at 18:23, Kevin Ollivier wrote: > > > > ----- Original Message ----- > > From: "Robin Dunn" > > To: > > Sent: Thursday, March 20, 2003 4:20 PM > > Subject: Re: [wxPython-dev] wxPython 2.4.0.7 preview [snip] > > Well, the whole question is: when do you know that you have a final? And > how do you differentiate between three different "what we thought were > finals" which turned out not to be? Do you have to rebuild everything > with a different "branding"? At my work we have gone through the same > issues for our product and have decided that a build # or timestamp is > needed for differentiating between different versions and the number > (2.4.0.8) for example is kept the same throughout the release. Perhaps > that is another idea? > > 2.4.0.7 (Build #4) > 2.4.0.7 (Built 2003-03-21 07:44:25) > > Or some variation of that? Well, you have a final when there is no longer a 'p1, p2' etc. tag. A p tag should be used for any release in which a new bug fix was added. This same strategy is used for alpha and beta release testing in many open source projects, and it is thus easily recognizable by users. (Using a beta marker would be fine with me as well, BTW.) Testing on the final version should happen only as an extra precaution in case somehow a change makes its way in between the last preview and the final build, but that could be avoided I think. (Especially if Robin, like Patrick, is tagging the CVS version that will be released.) I'm just concerned about Joe Public somehow getting ahold of one of the preview builds. Under the other approaches mentioned, there'd be no clear way to tell for 'Joe' to tell if he's got a preview or final release, unless he's familiar with our build system. I think he'd be likely to assume he's got a final, since there is nothing to tell him otherwise. However, having said all that, if others do not feel that this will be a problem, then I could go along with any of the other suggestions heard so far. Thanks, Kevin From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 29005 invoked from network); 21 Mar 2003 22:58:38 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 22:58:38 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [140.90.119.204] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 22:58:38 -0000 Received: from noaa.gov ([161.55.66.168]) by hermes.nos.noaa.gov (Netscape Messaging Server 4.15) with ESMTP id HC4FTP00.9J5 for ; Fri, 21 Mar 2003 17:58:37 -0500 Sender: cbarker Message-ID: <3E7B959F.DD493032@noaa.gov> Date: Fri, 21 Mar 2003 14:43:43 -0800 From: Chris Barker X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <3E7A3D20.6040509@alldunn.com> Content-Type: multipart/mixed; boundary="------------1D21FA1D72E8F80AEDF3A19D" Subject: Font size change bug on wxGTK --------------1D21FA1D72E8F80AEDF3A19D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, I'm trying to use a StaticText that has a font twice the size of the default font. I do this like so: Label2 = wxStaticText(self, -1, "Label 2", wxDefaultPosition, wxDefaultSize) Font = Label2.GetFont() Font.SetPointSize(Font.GetPointSize() * 2) Label2.SetFont(Font) Frankly that seems pretty clunky, but it should work, and it used to, but when I upgraded to 2.4.0, I got a weird result. I got what looks like Chinese characters to me, apparently a different font altogether. If I only multiply the font size by 1.5, it works OK. I've enclosed a screen shot of a test, where I create 3 StaticTexts, one normal, one with the font 1.5 times normal, and one with it twice. You can see the problem. In the code I printed out some font properties: Font info: Label1 GetFaceName : GetFamily : 74 GetNativeFontInfoDesc: 0;-*-*-*-*-*--*-*-*-*-*-*-*-* GetPointSize : 12 GetStyle : 90 Font info: Label2 Font info GetFaceName : GetFamily : 74 GetNativeFontInfoDesc: 0;-*-*-*-*-*--*-180-*-*-*-*-*-* GetPointSize : 18 GetStyle : 90 Font info: Label2 Font info GetFaceName : GetFamily : 74 GetNativeFontInfoDesc: 0;-*-*-*-*-*--*-240-*-*-*-*-*-* GetPointSize : 24 GetStyle : 90 Reading X font specifications is a little beyond me, but it looks like it should have gone from default to 180 to 240 in size, and the GetPointsize value looks fine. I'm also not getting any value from GetFaceName(), which is a little odd. I've also enclosed the code, any hints would be great. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov --------------1D21FA1D72E8F80AEDF3A19D Content-Type: image/gif; name="fontTest.gif" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="fontTest.gif" R0lGODdhsgHoAPcAAAAAAG5uboCAgJaWlqampre3t7m5ub6+vsPDw8nJyc7OztTU1NbW1tnZ 2dzc3N7e3uTk5Onp6frw5v///9AEoMcAmxUAEQgACFyoEQLBAAAVAAAIAFQnchFQyysEBUBA QIDMLhrJAxEVAAgIACAQFPTzAP//AL+/ADgEAfQAAf8AAL8AAP1hMvtOXQUEBEgAoNAEE8cA ABUAAAgAAFyoHNAnavtQAAUEAEBAAAEgDYDPAK0VAPsIAMAEZx0AACsAAEAAAACoWADB8gAV /wAIvxQnZIdQhxAEB0BACKjMqMHIwRUVFQgICGtAhgDzAAD/gAC/AlgEqPQA//8AFb8ACOFh avpOAKgAEMEAAAAAaMiQaPTz8r+/vzcUWGqHjggQBwhACDgEYM8A8AwAFACoAQDBAHiIaMMc MHxTjgQEB6ioAMHBABUVACWosgL/m4AVEQIICEyMiALJ8oAV/wIIv56+zXxSgQAA8AAAQgAA EwAACAAEAAAA+AAA/wAAv8ioqPTB9f8V/78Ivw0UANeHAAUQAAhAAKgE4MEA7RUAFEyoAALB +AC4qADz9QD//wC/vwkcoQBTigAEBQBACCWoDQGoAAD/AACMAQDIAAC+AABSAABAAFQEAPUA AAD0BAHJAAjcqPWYwf8MFb8ICPQUAKGHAAcQAAiAAGAAADQAALLoAAHzAAC/AAAiAABg+AAE /wBAv1SoAPXBAP8VAL8IAAioAGD/ADQVAEAIAAgUAfWHAP8QAL9AADQ2DaK8/wcHAAgDA7LQ BAHHAOhcqAACwQAAFfhWJ/SVUP8fBL9AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAsgHoAAAI/gAJABhIsKDBgwgTKlzIsKHD hxAjSpxIsaLFixgzatzIseNGCQAmiBxJsqTJkyhTqlzJsqXLlzBjypxJs6bNmzhz6tw5IQDP mwEGTnBAtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat3KtWuArlqDhgRLtqzZs2jTql3Ltm3U rwXiyp1LdwLdu3Pt4sU71IHYvg4EEFwKwK3hw4gTK17M+CrcAJAjS5Zsd7LlyJUvW+771yhB AUkBgG5MurTp06hTM328soBP161f+1QJm2hnzwNHFxWtdODRwqqDCx9OvDhS1hGSK18OG/by 5xGa+4TO3KdtoUcF+94NPPSE7tu5/heMGl68QfLdjatfz74tawjw48uXPgFCQgj04QOQvx+/ db/YZTdYYOkhFdJ3QhVYHnqEFfjUgu1FKOGEVrH2wIUYZkjfAwk9sCFBF4JYG4BjGZibYEeZ BEABdrWo4Ivb+RbjgCbiFt54DuBI4Y489nicA7A1IGRBQjZAXwMDFYkkAEbKNsGQBgk54m01 OnjXii2y+CJuRMnoZZcOcidmjoXNCKaPaKZJIWsLtFlQmwvQt8BAcM4JQJxOwvlmm1MGaCCZ JhoU14qE/jaemWYC2ht4wHm5pZqQRkocawpUWlClCtCnwECYbgpApk5iemmlfZb4mwDahelZ AQcZyiWg/olCOCaZOtIoq6S45poYawn0WlCvCdCXwEDADgtAsE76alCvpQK222ifMWXro2fC 2ui1Dc5qKLa6duutYawhIO645NKHQEIImEuQuOs2e6qNutXomatjfqmojKExemasZX7r779l sXbAwAQXTN8BCR1wMMIFAzCwu0WhaFSqWC2IY6KKygvmjTRmDPDHIFfFmgEkl2wyfSanbADK KpcMMYFJURzyzDR//Nhec8mGs1w67/yyqrTGW/PQRKv5mGaTZYY0Zq4tjdl1phYt9dTffvXT TFAr7fTWXHft9ddghy322GSXbfbZaKet9tpst+01iZUxIPfcdNdt99145633/t589+3334AH LvjghBdu+OGIJ6744owT/tVfrjEwwOSUV2755ZhnrvnmnHfu+eeghy766KSXbvrpqKeu+uqs tz46A48LFfkAHtVu++2456777rz37vvvCU0AO9yzA9D48cgnr/zyzDfv/PPQR3+38LGHVLz0 2Gev/fbcd+/994BTT3wAkhsP/vnop6/++ux/Lz7k5NPe/vz012///fgz8L7s8Zuf//8ADKAA B0i4/VmvfwRMoAIXyED7GTBu8mugBCdIwQoy74HXs6AGN8jBDuoNgwj0oAhHSEIGgrB8JUyh CldIvxNGkIUwjKEMpedC/83whjjMIeJqqMMe+vCH/nvjIRCHSMQeCrGISEziCo+oxCY6cYNM fKIUp6jAKFLxili83wMBEMIsevGL7DNgYboIxjKakXsP9AsKz8jGNkIvjWR0oxznuDg4rpGO eMxjAYfXmTjqEXw2zFsg8TZIuRXyj+Cz4wsRCci+HbJugyQII9enyEdOEnuFlKQhGTAQummS k4S8ZPoqKcrvRXJu5uskKFe5ykNaspQ05CN2/AhL6VkylajcpC5dWUv3yXIstOzl8zKpSf+l siC6tNsrhdk8UjITk8rMJStxCclQPlN7zrwm9E65S2oaM5nV1Cb2sinO5hkElZ00njpt+Ele ljN65HynPJMYz3naE4j1/rynPnOYz336M4b9/KdAUxjQgRrUgwU9qEItmNCFBu6TgkPm4CTq ULo19J8HARxEH7pRR2a0onO7qD8/+jdVFs6kfkMpSisqUow+8pzo5GRHYarMZUKSnTb1Z0tH SkySJgSdJI2p4Tq60J3qc6VCNaQxTSpJiG4UqRqFalF/OZRgKlSqNU2qUmWaVU/m9G5EdahR 76nSY34UqQ7xKuHCylKqqnGRFV0pQ7Sq1LnSNaVYbWv1qnpHkJaVq2qtq1rzele+sRWkY33n QmT608UylqY/9WhQQao/t1pVoAoBajo3u065+hQheJ0sYi3bV8qa1oSkhetpVzvAxLL2tedz /i1sZ4vG1H6Vtrjtnmxzy1vn7daetwWrIHubuN/Os51gdSVUD0tcvhlXnmXNbFen29zBPVex OKVuYLVb3fDZdrZ/vSkhlbvd7gbxu7BNZ11Bm9z12tW8H0TvaRsbyVMSlbDwnZ58WRve8m5S veLNr3f3+tbgutS/gPUkVz0r4AHDrcDgxWlkYwrg7Rq4udctJ4AzmVWmvrfB+iXwZR3K3K12 M5wIBrFF9ztfzqbVv/VVcd4y/EyaBlhvaE2xjOVG4xoneJrLzHFhd1xZEZe2xV5dp4m528oL V7fH1wwve2+s4B8TecVGVq1ppRxk5Tr5ySxG8pLxK9USqxjKNV7q/pBTvNkrh/jBI16oKjfc 5emaOb9oriVMlypdraKVokTOcy/nfFPRAhar+MVzmClLzYla2c3nzfKXIQ1pQVO6u5a+NIYX relOv7mPR/a0qLEM51CPetSZPvVsU63q17K61at9NaxNK+tZj1bStj51rXM9VVzz2tO7/rVB gy1sgRK72DrlNLLPrOxlN/jYzrYntKMtz2lTu5zWvrY2s63tZ3K728L8NrhrKe5xl7Lc5r4k utPNyHWz+4/ufnce4y1vOtK73nK8N77bqO99n7Hf/i4jwAP+xYETPIsGP/gVE67wKTK84U98 OMSbKPGJ07PZFldoxTNOxI1zHJ8Y/7ix/kMu8mT7uuR6LbWWUT5Qj7Mchy5/+QxjLnOAkrzm 76Q5zpd4851vu+c+9zbQgx7uoROd3EY/+rmTrnR1M73p7X461OEt9anPu+pWtzfWs57vrXOd 317/+r/DLnaBk73sBT872hGu9rUvvO1udzjc4x7xudOd4na/+8VPrnen873vUf874Kku+MFf vfCG1zriE9/1xTMe7I5//NgjL3mzU77yab885tmu+c2/vfOelzvoQ1/30ZMe76Y//d5VPmnV gzz1ru943mNP0NnTnoQ6v70vYa97I9q+9x3MPfC3J/zhZ6/4xo8l75MvQ+Qz/3nOf34zfy99 CUa/+sq7PvaR96f97Teu+96vI/XDT0Dwk3+H4z9/AM2v/sKxv/3WTT/88ff++TsY1Cu3PwwV ebX++///ABiAAjiABFiABkiApKV/QCRibtOADviAEBiBEjiBFFiBFug2cCMTs3GAHNiBHviB IBiCIvh/GwgTkOMzd/EaKLiCLNiCLviCMBiDMjiDNFiDNniDOJiDOriDMqiCLniCP6gXPDiE RFiERniESJiESriETMgzQtiCQAiFT9iEVFiFVniFWJiFWsiDPgiFsvOCXbiFYjiGZFiGZniG NBiGKygWF9iGbviGcBiHcjiHdBg2AAASwJOHeriHfNiHfviHgPgRAQEAOw== --------------1D21FA1D72E8F80AEDF3A19D Content-Type: text/plain; charset=us-ascii; name="FontTest.py" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="FontTest.py" #!/usr/bin/env python2.2 from wxPython.wx import * class TestPanel(wxPanel): def __init__(self, parent, id): wxPanel.__init__(self, parent, id, wxDefaultPosition,style=wxSUNKEN_BORDER) OuterBox = wxBoxSizer(wxVERTICAL) OuterBox.Add(20,20,0) Label1 = wxStaticText(self, -1, "Label 1", wxDefaultPosition, wxDefaultSize) Font = Label1.GetFont() print "Font info: Label1" print "GetFaceName : ", Font.GetFaceName() print "GetFamily : ", Font.GetFamily() print "GetNativeFontInfoDesc: ", Font.GetNativeFontInfoDesc() print "GetPointSize : ", Font.GetPointSize() print "GetStyle : ", Font.GetStyle() Label1.SetFont(Font) Label2 = wxStaticText(self, -1, "Label 2", wxDefaultPosition, wxDefaultSize) Font = Label2.GetFont() Font.SetPointSize(int(Font.GetPointSize() * 1.5)) print "Font info: Label2" print "Font info" print "GetFaceName : ", Font.GetFaceName() print "GetFamily : ", Font.GetFamily() print "GetNativeFontInfoDesc: ", Font.GetNativeFontInfoDesc() print "GetPointSize : ", Font.GetPointSize() print "GetStyle : ", Font.GetStyle() Label2.SetFont(Font) Label3 = wxStaticText(self, -1, "Label 3", wxDefaultPosition, wxDefaultSize) Font = Label3.GetFont() Font.SetPointSize(int(Font.GetPointSize() * 2)) print "Font info: Label2" print "Font info" print "GetFaceName : ", Font.GetFaceName() print "GetFamily : ", Font.GetFamily() print "GetNativeFontInfoDesc: ", Font.GetNativeFontInfoDesc() print "GetPointSize : ", Font.GetPointSize() print "GetStyle : ", Font.GetStyle() Label3.SetFont(Font) OuterBox.Add(Label1,0,wxALIGN_CENTER) OuterBox.Add(Label2,0,wxALIGN_CENTER) OuterBox.Add(Label3,0,wxALIGN_CENTER) OuterBox.Layout() self.SetAutoLayout(True) self.SetSizer(OuterBox) self.Fit() class TestFrame(wxFrame): def __init__(self,parent, id,title,position,size): wxFrame.__init__(self,parent, id,title,position, size) self.Panel = TestPanel(self,-1) self.Show(True) class App(wxApp): def OnInit(self): Frame = TestFrame(NULL, -1, "Font Test", wxDefaultPosition, wxDefaultSize) self.SetTopWindow(Frame) return True if __name__ == "__main__": app = App(0) app.MainLoop() --------------1D21FA1D72E8F80AEDF3A19D-- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 642 invoked from network); 21 Mar 2003 23:02:06 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 23:02:06 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [140.90.119.204] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 23:2:6 -0000 Received: from noaa.gov ([161.55.66.168]) by hermes.nos.noaa.gov (Netscape Messaging Server 4.15) with ESMTP id HC4FZH00.0I4 for ; Fri, 21 Mar 2003 18:02:05 -0500 Sender: cbarker Message-ID: <3E7B966F.DC742609@noaa.gov> Date: Fri, 21 Mar 2003 14:47:11 -0800 From: Chris Barker X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <3E7A3D20.6040509@alldunn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Another font size question HI all, I"ve noticed that on my Linux box and Windows, I get very different sizes of fonts, when specifying the same size. I suspect that the problem is that GTK and Windows have different ideas as to how many pixels-per-inch my screen is. Personally, I'd much rather specify fonts in pixel sizes, rather than points, but so be it. My question is: can I find out how many ppi wxWindows thinks the screen is, so I can choose the appropriate font size to give me the pixel size I know I want? -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 3334 invoked from network); 21 Mar 2003 23:07:02 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 23:07:02 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.81] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 23:7:2 -0000 Received: from dellPC (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-2.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id ATE55497; Fri, 21 Mar 2003 15:06:18 -0800 (PST) Message-ID: <01ef01c2effe$83935e00$6701a8c0@dellPC> From: "Kevin Ollivier" To: References: <0089B3CA-5A31-11D7-82C2-000393CB1C86@tulane.edu> <3E796A89.70105@alldunn.com> Date: Fri, 21 Mar 2003 15:06:27 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: wxPython HTMLHelp Docs Hi all, While trying to build a wxPython installer using the make_installer.py script, I noticed it is looking for wx.chm and ogl.chm, which aren't included in the source distros for wxWindows and wxPython. I can of course copy these files from my current wxPython installation or from the wxMSW package, but I was curious if there is some script or automated process for building these docs. I saw some Unix scripts for making ZIP files of the help docs, but nothing for HTML Help. Thanks, Kevin From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 9998 invoked from network); 21 Mar 2003 23:23:01 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 23:23:01 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.54] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 23:23:1 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18wVqm-00065K-00 for wxPython-dev@lists.wxwindows.org; Fri, 21 Mar 2003 15:23:00 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id 53C304F5C; Fri, 21 Mar 2003 17:23:43 -0600 (CST) To: wxPython-dev@lists.wxwindows.org References: <3E7A3D20.6040509@alldunn.com> <3E7B959F.DD493032@noaa.gov> From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 21 Mar 2003 17:23:43 -0600 In-Reply-To: <3E7B959F.DD493032@noaa.gov> Message-ID: Lines: 38 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [wxPython-dev] Font size change bug on wxGTK Chris Barker writes: > Hi all, > > I'm trying to use a StaticText that has a font twice the size of the > default font. I do this like so: > > > Label2 = wxStaticText(self, -1, "Label 2", wxDefaultPosition, > wxDefaultSize) > Font = Label2.GetFont() > Font.SetPointSize(Font.GetPointSize() * 2) > Label2.SetFont(Font) > > Frankly that seems pretty clunky, but it should work, and it used to, > but when I upgraded to 2.4.0, I got a weird result. I got what looks > like Chinese characters to me, apparently a different font altogether. > If I only multiply the font size by 1.5, it works OK. I've enclosed a > screen shot of a test, where I create 3 StaticTexts, one normal, one > with the font 1.5 times normal, and one with it twice. You can see the > problem. In the code I printed out some font properties: I've seen a similar problem with the StyledTextCtrl. I added code to PyCrust so you can type Ctrl-] to make the font bigger, Ctrl-[ to make it smaller, and Ctrl-= to return to the default (useful when making presentations). When I first was working on the code I'd sometimes see a foreign language font for some of the larger sizes. Then the problem went away and I moved on to other things. But it sounds like the same basic issue you are facing, so it isn't limited to StaticText. But Linux fonts are still mysterious to me as well. -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 14913 invoked from network); 21 Mar 2003 23:36:00 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Mar 2003 23:36:00 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [140.90.119.204] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Mar 2003 23:36:0 -0000 Received: from noaa.gov ([161.55.66.168]) by hermes.nos.noaa.gov (Netscape Messaging Server 4.15) with ESMTP id HC4HJZ00.KKQ for ; Fri, 21 Mar 2003 18:35:59 -0500 Sender: cbarker Message-ID: <3E7B9E5E.8573C90F@noaa.gov> Date: Fri, 21 Mar 2003 15:21:02 -0800 From: Chris Barker X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <3E7A3D20.6040509@alldunn.com> <3E7B959F.DD493032@noaa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] Font size change bug on wxGTK "Patrick K. O'Brien" wrote: > I've seen a similar problem with the StyledTextCtrl. I added code to > PyCrust so you can type Ctrl-] to make the font bigger, Ctrl-[ to make > it smaller, and Ctrl-= to return to the default (useful when making > presentations). When I first was working on the code I'd sometimes see > a foreign language font for some of the larger sizes. Then the problem > went away and I moved on to other things. But it sounds like the same > basic issue you are facing, so it isn't limited to StaticText. I didn't suspect that it was, that's just how I used it. Did you try my code? did it work for you? In any case, I understand Robin is on the verge of supporting a new version of GTK, so maybe that will solve it. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 25008 invoked from network); 22 Mar 2003 01:04:54 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 22 Mar 2003 01:04:54 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 22 Mar 2003 1:4:53 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id E21964F9A for ; Fri, 21 Mar 2003 20:04:51 -0500 (EST) Message-ID: <3E7BB6B3.5040203@alldunn.com> Date: Fri, 21 Mar 2003 17:04:51 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <0089B3CA-5A31-11D7-82C2-000393CB1C86@tulane.edu> <3E796A89.70105@alldunn.com> <01ef01c2effe$83935e00$6701a8c0@dellPC> In-Reply-To: <01ef01c2effe$83935e00$6701a8c0@dellPC> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] wxPython HTMLHelp Docs Kevin Ollivier wrote: > Hi all, > > While trying to build a wxPython installer using the make_installer.py > script, I noticed it is looking for wx.chm and ogl.chm, which aren't > included in the source distros for wxWindows and wxPython. I can of course > copy these files from my current wxPython installation or from the wxMSW > package, but I was curious if there is some script or automated process for > building these docs. I saw some Unix scripts for making ZIP files of the > help docs, but nothing for HTML Help. For what you are attempting it would definitly be easier to just copy the .chm's that you already have. To build the docs yourself you need to build tex2rtf in wxWindows/utils and put it on the PATH, and then install a copy of MS HTMLHelp Workshop and make sure that it is on the PATH so the command line tools can be found. Then in the wxWindows/src/msw do "nmake -f makefile.vc htmlhelp" (or something like that.) -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 6904 invoked from network); 22 Mar 2003 01:34:45 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 22 Mar 2003 01:34:45 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 22 Mar 2003 1:34:45 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 835DF4F9C for ; Fri, 21 Mar 2003 20:34:43 -0500 (EST) Message-ID: <3E7BBDB3.3030302@alldunn.com> Date: Fri, 21 Mar 2003 17:34:43 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: wxPython 2.4.0.7 rc1 Since we havn't come up with a good plan yet about the version numbers I went ahead and named this one 2.4.0.7 (The preview had "p1 afterall.) You can get it at http://alldunn.com/wxPython/preview/2.4.0.7/rc1/ This is on my DSL with a 256k uplink speed so try not to swamp it too badly. 2.4.0.7 ------- Gave up on generating a warning upon the use of the old true/false or TRUE/FALSE values. Fixed wxGenericTreeCtrl (used on wxGTK and wxMac for wxTreeCtrl) so that it can successfully handle lots of nodes instead of overflowing when the virtual height of the widget overflowed a 16-bit value. Fixed the typemap that converts strings to wxColours to also accept unicode. Fixed problem where the wrong class name could sometimes be used for OOR. Fixed an interpreter lock problem in the __eq__ and __ne__ methods in wxSize and etc. Updated PyCrust to version 0.9 Instead of always logging C++ assertions, added wxPYAPP_ASSERT_LOG flag to turn it on. In most cases turning it into an exception (the default behavior) is enough. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 20841 invoked from network); 22 Mar 2003 03:43:04 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 22 Mar 2003 03:43:04 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.81] by sunsite.dk (MessageWall 1.0.8) with SMTP; 22 Mar 2003 3:43:4 -0000 Received: from tulane.edu (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-2.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id ATE84374; Fri, 21 Mar 2003 19:43:02 -0800 (PST) Date: Fri, 21 Mar 2003 19:43:12 -0800 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Kevin Ollivier To: wxPython-dev@lists.wxwindows.org Content-Transfer-Encoding: 7bit In-Reply-To: <3E7BB6B3.5040203@alldunn.com> Message-Id: <68017F8C-5C18-11D7-82C2-000393CB1C86@tulane.edu> X-Mailer: Apple Mail (2.551) Subject: Re: [wxPython-dev] wxPython HTMLHelp Docs On Friday, March 21, 2003, at 05:04 PM, Robin Dunn wrote: > Kevin Ollivier wrote: >> Hi all, >> While trying to build a wxPython installer using the make_installer.py >> script, I noticed it is looking for wx.chm and ogl.chm, which aren't >> included in the source distros for wxWindows and wxPython. I can of >> course >> copy these files from my current wxPython installation or from the >> wxMSW >> package, but I was curious if there is some script or automated >> process for >> building these docs. I saw some Unix scripts for making ZIP files of >> the >> help docs, but nothing for HTML Help. > > For what you are attempting it would definitly be easier to just copy > the .chm's that you already have. > > To build the docs yourself you need to build tex2rtf in > wxWindows/utils and put it on the PATH, and then install a copy of MS > HTMLHelp Workshop and make sure that it is on the PATH so the command > line tools can be found. Then in the wxWindows/src/msw do "nmake -f > makefile.vc htmlhelp" (or something like that.) Hmmm... I think I like the copying option. Copying's good. =) This is actually very useful, though, as I will need to write up some docs for wxMozilla, which I should probably try to do in the TeX format. I have managed to successfully make a binary, BTW. I've also got the wxMozilla GRE installer running smoothly. The next step will be to add in the wxMozilla files to the wxPython installer package and rebuild. After that, I should be ready to try it on an unsuspecting Windows machine, which will probably break everything and send me back to the drawing board. ^_- Will keep you posted! Thanks, Kevin From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 25120 invoked from network); 23 Mar 2003 17:36:14 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 23 Mar 2003 17:36:14 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [12.247.235.184] by sunsite.dk (MessageWall 1.0.8) with SMTP; 23 Mar 2003 17:36:14 -0000 Received: by neo.dave.dribin.org (Postfix, from userid 500) id 3DDDC600F; Sun, 23 Mar 2003 12:36:15 -0500 (EST) Date: Sun, 23 Mar 2003 11:36:15 -0600 From: Dave Dribin To: wxPython-dev@lists.wxwindows.org Message-ID: <20030323173614.GD17372@neo.attbi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: Swig, wxWizard, and Java Hi All, Yes, I *do* know this is the wxPython dev list, but this seems to be the most likely place where people would know what I am talking about. :) For the last couple of days, I've been working on Java bindings to wxWindows. I have taken a clue from wxPython and also decided to use Swig to generate the glue. I've gotten the basics to work: wxFrame, wxPanel, wxButton, wxMenu, wxMenuBar, initialization, and event handling. But then I decided to tackle wxWizard et al. I am seeing some strange behavior when creating Java subclasses of wxWizardPageSimple. Sometimes the widgets added to the wizard page are not drawn, and sometimes the "Next" button is incorrectly labeled as "Finish". Anyhow, I guess my questions is, did you guys find any gotchas with either Swig or wxWindows on any of the wizard classes? I may need to consult wx-dev, but at the moment I suspect this is a problem wrapping wx with Swig. Please note that I am new to both Swig and wxWindows. Thanks, -Dave From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 14164 invoked from network); 24 Mar 2003 00:14:27 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 24 Mar 2003 00:14:27 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.78] by sunsite.dk (MessageWall 1.0.8) with SMTP; 24 Mar 2003 0:14:27 -0000 Received: from dellPC (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-1.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with SMTP id AVJ46097; Sun, 23 Mar 2003 14:57:50 -0800 (PST) Message-ID: <002201c2f18f$aa934230$6701a8c0@dellPC> From: "Kevin & Masako Ollivier" To: Cc: , Date: Sun, 23 Mar 2003 14:58:05 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [MSW] wxPython with wxMozilla prototype Hi all, I've created a prototype release of wxPython with wxMozilla included and uploaded it to http://www.theolliviers.com/wxMozilla. (Note that it requires Python 2.2.) The current prototype is Windows only, but I hope to have prototypes for other platforms available soon. All you need to do to run the prototype is download and install both the wxMozilla GRE ("Gecko Runtime Environment") and the wxPython with wxMozilla package. Then start the demo, and select wxMozilla from the 'what's new' section! I've tested on Windows 2000 and XP with good results so far. Note that this is not feature complete yet, so don't expect too much! If it works on people's machines I'll be more than happy. ;-) If you want to see editing support, there is a "wxMozillaEditor.py" file in the wxPython\demo folder. Run that to see the *very* primitive editor. =) (Also, note that the editor seems to freeze with thread errors on shutdown - am looking into this.) I also uploaded a new wxMozilla source package for Windows. It should be pretty easy to build wxMozilla now - just install the wxMozilla GRE and follow the instructions in BUILD.Win32.txt. Or, you can also use the MSVC .dsp project files that Dave Fancella has added (in the root and demo directories). Everything not included in the GRE is in the source package, so it doesn't require users to build Mozilla. I also included the changes to wxPython in the wxPython subfolder of the source package. Any comments/bug reports/suggestions are greatly appreciated! =) Thanks, Kevin From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 16583 invoked from network); 24 Mar 2003 18:11:15 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 24 Mar 2003 18:11:15 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 24 Mar 2003 18:11:14 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 0BD5F4E6F for ; Mon, 24 Mar 2003 13:11:03 -0500 (EST) Message-ID: <3E7F4A36.6050802@alldunn.com> Date: Mon, 24 Mar 2003 10:11:02 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <20030323173614.GD17372@neo.attbi.com> In-Reply-To: <20030323173614.GD17372@neo.attbi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] Swig, wxWizard, and Java Dave Dribin wrote: > But then I decided to tackle wxWizard et al. I am seeing some strange > behavior when creating Java subclasses of wxWizardPageSimple. > Sometimes the widgets added to the wizard page are not drawn, and > sometimes the "Next" button is incorrectly labeled as "Finish". > Anyhow, I guess my questions is, did you guys find any gotchas with > either Swig or wxWindows on any of the wizard classes? No, but you do need to provide a way for calls to virtual C++ methods to be reflected to methods in the derived Java class, if they are present in the derived class. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 16640 invoked from network); 24 Mar 2003 18:11:18 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 24 Mar 2003 18:11:18 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [208.151.246.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 24 Mar 2003 18:11:18 -0000 Received: from alldunn.com (localhost.localdomain [127.0.0.1]) by xavier.alldunn.com (Postfix) with ESMTP id 4D6D64E6F for ; Mon, 24 Mar 2003 13:11:06 -0500 (EST) Message-ID: <3E7F4A3A.6070709@alldunn.com> Date: Mon, 24 Mar 2003 10:11:06 -0800 From: Robin Dunn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: wxPython-dev@lists.wxwindows.org References: <3E7BBDB3.3030302@alldunn.com> In-Reply-To: <3E7BBDB3.3030302@alldunn.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [wxPython-dev] wxPython 2.4.0.7 rc1 Robin Dunn wrote: > Since we havn't come up with a good plan yet about the version numbers I > went ahead and named this one 2.4.0.7 (The preview had "p1 afterall.) > You can get it at > > http://alldunn.com/wxPython/preview/2.4.0.7/rc1/ > Anybody have any comments on 2.4.0.7 before I start uploading to SF? -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython! From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 16797 invoked from network); 24 Mar 2003 19:06:46 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 24 Mar 2003 19:06:46 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [207.217.120.46] by sunsite.dk (MessageWall 1.0.8) with SMTP; 24 Mar 2003 19:6:45 -0000 Received: from cc4-24.207.137.58.charter-stl.com ([24.207.137.58] helo=localhost.localdomain) by grebe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18xXHO-0003gN-00 for wxPython-dev@lists.wxwindows.org; Mon, 24 Mar 2003 11:06:42 -0800 Received: by localhost.localdomain (Postfix, from userid 501) id E55824E84; Mon, 24 Mar 2003 13:07:16 -0600 (CST) To: wxPython-dev@lists.wxwindows.org References: <3E7BBDB3.3030302@alldunn.com> <3E7F4A3A.6070709@alldunn.com> From: pobrien@orbtech.com (Patrick K. O'Brien) Date: 24 Mar 2003 13:07:16 -0600 In-Reply-To: <3E7F4A3A.6070709@alldunn.com> Message-ID: Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [wxPython-dev] wxPython 2.4.0.7 rc1 Robin Dunn writes: > Robin Dunn wrote: > > Since we havn't come up with a good plan yet about the version > > numbers I went ahead and named this one 2.4.0.7 (The preview had "p1 > > afterall.) You can get it at > > http://alldunn.com/wxPython/preview/2.4.0.7/rc1/ > > > > Anybody have any comments on 2.4.0.7 before I start uploading to SF? So far it looks fine to me. -- Patrick K. O'Brien Orbtech http://www.orbtech.com/web/pobrien ----------------------------------------------- "Your source for Python programming expertise." ----------------------------------------------- From nobody Thu Mar 20 17:04:42 2008 Return-Path: Mailing-List: contact wxPython-dev-help@lists.wxwindows.org; run by ezmlm Delivered-To: mailing list wxPython-dev@lists.wxwindows.org Received: (qmail 20615 invoked from network); 24 Mar 2003 21:59:46 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 24 Mar 2003 21:59:46 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [24.234.0.78] by sunsite.dk (MessageWall 1.0.8) with SMTP; 24 Mar 2003 21:59:46 -0000 Received: from dellPC (cm081.148.120.24.lvcm.com [24.120.148.81]) by 100m.mpr200-1.esr.lvcm.net (Mirapoint Messaging Server MOS 2.9.3.5) with ESMTP id AVK87154; Mon, 24 Mar 2003 13:59:38 -0800 (PST) Message-ID: <000701c2f250$b519af20$6701a8c0@dellPC> From: "Kevin Ollivier" To: References: <3E7BBDB3.3030302@alldunn.com> <3E7F4A3A.6070709@alldunn.com> Date: Mon, 24 Mar 2003 13:59:56 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000