From: Bruce S. <Bru...@nc...> - 2012-12-21 17:52:37
|
VPython-wx can now run all the standard VPython demos. The only remaining piece of platform-dependent code is tiny routines for something called GetProcAddress. Threads have been eliminated from the C++ code. Eliminating threads and platform-dependent C++ code should make it much easier to maintain and extend VPython in the future. Of immediate importance is that VPython-wx runs on 64-bit Python on the Mac, using Cocoa, which was impossible with the old VPython architecture. Steve Spicklemire has been providing great support in this effort. He got mouse zoom and rotate working correctly, and he has been developing distutils machinery for easy building on Windows/Mac/Linux. He is investigating various options for building user installers (the distinction is that to build you need a C++ compiler, whereas Windows and Mac users need binary installers; most Windows users don't have a compiler installed, and a compiler is no longer included in the standard Mac installation). Steve has also been testing VPython-wx on Mac and Linux, while I concentrated on Windows. Thanks so much, Steve! The wxPython fonts look quite ugly in label objects, and I've asked the wxPython community about this. I hope they'll tell me that I'm doing something wrong. Next priorities are wider testing by Steve and me, and installers for all platforms to make it easy for adventurers to try it out. After that, it is intended to make it easy to place a VPython canvas in a wxPython window and add buttons, sliders, etc. to other locations in the window, as well as adding standard menus. In the longer run the current emphasis on CPU OpenGL graphics should be replaced by using GPUs on the graphics card. Bruce Sherwood P.S. In other news, there is a new project Brython (www.brython.info) whose developer is creating a Python-to-JavaScript compiler, which means one could run Python programs in a browser. GlowScript (glowscript.org, the browser-based 3D programming environment I'm developing that is similar to VPython) already lets you write your programs in either JavaScript or in CoffeeScript, which compiles to JavaScript. Maybe it will be possible to use Brython to let GlowScript programs be written in Python, which I feel is a significantly better language for the purpose than either JavaScript or CoffeeScript. |
From: Bruce S. <Bru...@nc...> - 2012-12-22 03:12:17
|
Now fixed. As has happened a number of times in the past, someone in the wxPython community immediately pointed out the (dumb) mistake I'd made. The label fonts now look fine, and there are no major errors visible in the standard demo suite. Bruce Sherwood On Fri, Dec 21, 2012 at 10:52 AM, Bruce Sherwood <Bru...@nc...>wrote: > The wxPython fonts look quite ugly in label objects, and I've asked the > wxPython community about this. I hope they'll tell me that I'm doing > something wrong. |
From: K.-Michael A. <kmi...@gm...> - 2012-12-22 03:18:21
|
Could you briefly describe the mistake you made, so that we learn something about what can go wrong with wxpython? Happy holidays! PS.: As I am a Mac user, I offer to test the stuff on my Mac, shall I report via github issues or here in the mailing list? On Dec 21, 2012, w52, at 7:12 PM, Bruce Sherwood <Bru...@nc...> wrote: > Now fixed. As has happened a number of times in the past, someone in the wxPython community immediately pointed out the (dumb) mistake I'd made. The label fonts now look fine, and there are no major errors visible in the standard demo suite. > > Bruce Sherwood > > On Fri, Dec 21, 2012 at 10:52 AM, Bruce Sherwood <Bru...@nc...> wrote: > The wxPython fonts look quite ugly in label objects, and I've asked the wxPython community about this. I hope they'll tell me that I'm doing something wrong. > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d_______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Bruce S. <Bru...@nc...> - 2012-12-22 04:08:16
|
The mistake I made is so arcane as to be of little value to others. I used DrawText to create an RGB bitmap to be used as a texture on an OpenGL quad in C++ to form the label object. Part of the bitmap is background pixels which by C++ program will be assigned opacity values of 0 to let the background quad show through. For subtle antialiasing issues in the preparation of the bitmap I used not the label background color but a color very similar to the foreground color. This led to a spreading of the text strokes which uglified the text. The cure was simply to use the label background color as the background color in the preparation of the bitmap using DrawText, an approach I had tried early on but abandoned when I ran into difficulties, difficulties that later were removed by other developments. Sorry you asked? I guess we should do the experiment of using the github machinery for the reporting of bugs. I encourage everyone to wait a short time before trying VPython-wx because Steve Spicklemire is in the process of finalizing the machinery for creating easy-to-use installers. Bruce Sherwood On Fri, Dec 21, 2012 at 8:18 PM, K.-Michael Aye <kmi...@gm...>wrote: > Could you briefly describe the mistake you made, so that we learn > something about what can go wrong with wxpython? > > Happy holidays! > > PS.: As I am a Mac user, I offer to test the stuff on my Mac, shall I > report via github issues or here in the mailing list? > > > On Dec 21, 2012, w52, at 7:12 PM, Bruce Sherwood <Bru...@nc...> > wrote: > > > Now fixed. As has happened a number of times in the past, someone in the > wxPython community immediately pointed out the (dumb) mistake I'd made. The > label fonts now look fine, and there are no major errors visible in the > standard demo suite. > > > > Bruce Sherwood > > > > On Fri, Dec 21, 2012 at 10:52 AM, Bruce Sherwood < > Bru...@nc...> wrote: > > The wxPython fonts look quite ugly in label objects, and I've asked the > wxPython community about this. I hope they'll tell me that I'm doing > something wrong. > > > > > ------------------------------------------------------------------------------ > > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > > Remotely access PCs and mobile devices and provide instant support > > Improve your efficiency, and focus on delivering more value-add services > > Discover what IT Professionals Know. Rescue delivers > > > http://p.sf.net/sfu/logmein_12329d2d_______________________________________________ > > Visualpython-users mailing list > > Vis...@li... > > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > |
From: K.-Michael A. <kmi...@gm...> - 2012-12-22 04:44:52
|
On Dec 21, 2012, at 20:08, Bruce Sherwood <Bru...@nc...> wrote: > The mistake I made is so arcane as to be of little value to others. I used DrawText to create an RGB bitmap to be used as a texture on an OpenGL quad in C++ to form the label object. Part of the bitmap is background pixels which by C++ program will be assigned opacity values of 0 to let the background quad show through. For subtle antialiasing issues in the preparation of the bitmap I used not the label background color but a color very similar to the foreground color. This led to a spreading of the text strokes which uglified the text. The cure was simply to use the label background color as the background color in the preparation of the bitmap using DrawText, an approach I had tried early on but abandoned when I ran into difficulties, difficulties that later were removed by other developments. Sorry you asked? > > I guess we should do the experiment of using the github machinery for the reporting of bugs. I encourage everyone to wait a short time before trying VPython-wx because Steve Spicklemire is in the process of finalizing the machinery for creating easy-to-use installers. > Oh, I wanted to comment on that: Xcode is still freely available via App Store and with it come the compilers that should be able to build everything. So I'm not sure the requirement of building complete binary installers for Mac is really THAT stringent? Alternatively the 'brew' system delivers a lot of command line tools without much hassle so maybe I should give it a go with a trial of compilations? Michael > Bruce Sherwood > > > On Fri, Dec 21, 2012 at 8:18 PM, K.-Michael Aye <kmi...@gm...> wrote: >> Could you briefly describe the mistake you made, so that we learn something about what can go wrong with wxpython? >> >> Happy holidays! >> >> PS.: As I am a Mac user, I offer to test the stuff on my Mac, shall I report via github issues or here in the mailing list? >> >> >> On Dec 21, 2012, w52, at 7:12 PM, Bruce Sherwood <Bru...@nc...> wrote: >> >> > Now fixed. As has happened a number of times in the past, someone in the wxPython community immediately pointed out the (dumb) mistake I'd made. The label fonts now look fine, and there are no major errors visible in the standard demo suite. >> > >> > Bruce Sherwood >> > >> > On Fri, Dec 21, 2012 at 10:52 AM, Bruce Sherwood <Bru...@nc...> wrote: >> > The wxPython fonts look quite ugly in label objects, and I've asked the wxPython community about this. I hope they'll tell me that I'm doing something wrong. >> > >> > ------------------------------------------------------------------------------ >> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> > Remotely access PCs and mobile devices and provide instant support >> > Improve your efficiency, and focus on delivering more value-add services >> > Discover what IT Professionals Know. Rescue delivers >> > http://p.sf.net/sfu/logmein_12329d2d_______________________________________________ >> > Visualpython-users mailing list >> > Vis...@li... >> > https://lists.sourceforge.net/lists/listinfo/visualpython-users >> > |
From: Bruce S. <Bru...@nc...> - 2012-12-22 05:21:00
|
Yes, a compiler is easily obtainable for the Mac, but that's not the point. Most users won't want to be bothered with this and will want to have binary installers. Of course there's no problem for developers or others with a technical bent. Bruce Sherwood On Fri, Dec 21, 2012 at 9:44 PM, K.-Michael Aye <kmi...@gm...>wrote: > > > On Dec 21, 2012, at 20:08, Bruce Sherwood <Bru...@nc...> wrote: > > The mistake I made is so arcane as to be of little value to others. I used > DrawText to create an RGB bitmap to be used as a texture on an OpenGL quad > in C++ to form the label object. Part of the bitmap is background pixels > which by C++ program will be assigned opacity values of 0 to let the > background quad show through. For subtle antialiasing issues in the > preparation of the bitmap I used not the label background color but a color > very similar to the foreground color. This led to a spreading of the text > strokes which uglified the text. The cure was simply to use the label > background color as the background color in the preparation of the bitmap > using DrawText, an approach I had tried early on but abandoned when I ran > into difficulties, difficulties that later were removed by other > developments. Sorry you asked? > > I guess we should do the experiment of using the github machinery for the > reporting of bugs. I encourage everyone to wait a short time before trying > VPython-wx because Steve Spicklemire is in the process of finalizing the > machinery for creating easy-to-use installers. > > > Oh, I wanted to comment on that: Xcode is still freely available via App > Store and with it come the compilers that should be able to build > everything. So I'm not sure the requirement of building complete binary > installers for Mac is really THAT stringent? Alternatively the 'brew' > system delivers a lot of command line tools without much hassle so maybe I > should give it a go with a trial of compilations? > > Michael > > Bruce Sherwood > > > On Fri, Dec 21, 2012 at 8:18 PM, K.-Michael Aye <kmi...@gm...>wrote: > >> Could you briefly describe the mistake you made, so that we learn >> something about what can go wrong with wxpython? >> >> Happy holidays! >> >> PS.: As I am a Mac user, I offer to test the stuff on my Mac, shall I >> report via github issues or here in the mailing list? >> >> >> On Dec 21, 2012, w52, at 7:12 PM, Bruce Sherwood <Bru...@nc...> >> wrote: >> >> > Now fixed. As has happened a number of times in the past, someone in >> the wxPython community immediately pointed out the (dumb) mistake I'd made. >> The label fonts now look fine, and there are no major errors visible in the >> standard demo suite. >> > >> > Bruce Sherwood >> > >> > On Fri, Dec 21, 2012 at 10:52 AM, Bruce Sherwood < >> Bru...@nc...> wrote: >> > The wxPython fonts look quite ugly in label objects, and I've asked the >> wxPython community about this. I hope they'll tell me that I'm doing >> something wrong. >> > >> > >> ------------------------------------------------------------------------------ >> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> > Remotely access PCs and mobile devices and provide instant support >> > Improve your efficiency, and focus on delivering more value-add services >> > Discover what IT Professionals Know. Rescue delivers >> > >> http://p.sf.net/sfu/logmein_12329d2d_______________________________________________ >> > Visualpython-users mailing list >> > Vis...@li... >> > https://lists.sourceforge.net/lists/listinfo/visualpython-users >> >> > |
From: Kevin K. <ka...@so...> - 2012-12-22 15:38:23
|
Bruce Sherwood <Bru...@nc...> wrote to kmi...@gm..., vis...@li...: > Yes, a compiler is easily obtainable for the Mac, but that's not the point. > Most users won't want to be bothered with this and will want to have binary > installers. Of course there's no problem for developers or others with a > technical bent. I strongly agree that if you want Vpython to be used, it must have a standard binary installer on Mac and Windows systems. If it is not worth the effort for one person to build a proper binary installer, then it isn't worth the effort for 100s of people to install all the dependencies and compile it themselves. (I've gotten very irked with the gnuplot community for having a project that is damn near uninstallable on Macs---they expect people to build a complete Linux shadow OS in order to install gnuplot.) |