Not well supported on the Mac?
In a thread starting at: http://forum.swarthmore.edu/epigone/geometry-research/pefrorsken Clifford J. Nelson advises me to forsake a Python-based approach for another language called Clean, because "Python is not supported well for the Mac." I thought I'd run that by comp.lang.python, as well as the Python edu-sig. Given the importance of Mac technology in the schools, limitations re Python on that platform are of some relevance to the "Computer Programming for Everyone" (CP4E) thread. Please reply cc: pdx4d@teleport.com -- no need to post a reply to the thread mentioned above, as that's a pure geometry research list and doesn't need to get bogged down in technical discussions re Mac OS, Tkinter, IDLE or whatever (I've already posted enough along those lines, will maybe summarize feedback I get re Mac). Kirby
Kirby- This is the reason I raised the issue of cross-platform support on this list on Feb 4, 2000 ("Common Graphical Framework for Python Tutorials?"). From what I read in comp.lang.python, TK support on the Mac has historically been questionable (although the base command line system otherwise works well). My personal feeling is that widespread acceptance of CP4E absolutely requires addressing seamless cross-platform support at the GUI level (like Squeak or LearningWorks), as well as incorporating numerous advanced features found to varying degrees in other systems (like Squeak, LearningWorks, or Dr. Scheme). http://www.squeak.org http://learningworks.neometron.com/ http://www.cs.rice.edu/CS/PLT/packages/drscheme/ Some discussion on edu-sig of needed features in Python to support CP4E has been discouraged as "vaporware". There is much truth to comments made here that people posting suggestions may have no plans or desire to implement them any time soon. But I feel that it is equally true that it is useful at the beginning to have some level of collaborative discussion of system needs and features (and prior art) before it make sense for anyone to make a big commitment to CP4E-specific implementation. Many people who are not implementers can contribute to such discussions based on their previous experience in education or with educational software (in a sense, as "requirements analysts"). There is also much value in just discussing what one can do easily on the PC with the existing implementation. I have greatly enjoyed your posts on your personal experiences and examples doing so. In many open ended systems with a body of useful scripts there are three categories of participants. Users: 90% use what is there (and complain/suggest and tell their friends). Authors: 9% write simple things and make minor improvements in existing scripts. They know what the important/feasible issues are, and do much of the support of the 90% in answering common questions, and making simple fixes and changes. Gurus: 1% understand the system through and through and do the bulk of the implementation, and do much of the support of the 9%. All three types of participants contribute in their own ways to making a system a success. Each level recruits from the previous level (World->User, User->Author, Author->Guru). In the case of CP4E, this would imply: Users: 90% of educators would use Python based materials that already exist (scripts, tutorials, and exercises). This group explains to the rest of the world why Python makes sense for education and where to get materials. They make creative suggestions they can't implement (like "Python should have a cross-platform GUI"), but in effect, these suggestions and complaints are producing "requirements". Authors: 9% of educators might write simple new materials, or improve a script or extend an exercise. This group helps support the 90% with minor customizations, and encourages some users to become authors. Gurus: 1% of educators are going to make significant changes or additions to Python and related educational materials to support CP4E. Much of these improvements are driven by observation of the 90% and more direct interaction with the 9%. This group encourages some authors to do bigger projects (especially if they complain or suggest too much :-) and take over aspects of system maintenance (becoming gurus). In the case of the Mac issue, which is a deep issue, only 1% of educators could do something about this, and only a fraction will be interested. So, this means we probably need about 1000 educators involved with CP4E to get this Mac support issue resolved (900 users, 90 authors, and 10 gurus, of which one guru will be a Mac enthusiast and also interested in resolving cross-platform issues). -Paul Fernhout Kurtz-Fernhout Software ========================================================= Developers of custom software and educational simulations Creators of the Garden with Insight(TM) garden simulator http://www.kurtz-fernhout.com Kirby Urner wrote:
In a thread starting at: http://forum.swarthmore.edu/epigone/geometry-research/pefrorsken
Clifford J. Nelson advises me to forsake a Python-based approach for another language called Clean, because "Python is not supported well for the Mac."
I thought I'd run that by comp.lang.python, as well as the Python edu-sig. Given the importance of Mac technology in the schools, limitations re Python on that platform are of some relevance to the "Computer Programming for Everyone" (CP4E) thread. [snip]
Kirby
At 03:24 PM 05/28/2000 -0400, Paul Fernhout wrote:
Kirby-
This is the reason I raised the issue of cross-platform support on this list on Feb 4, 2000 ("Common Graphical Framework for Python Tutorials?").
Yes, I understand this better now. When I say Python is already finished enough to support my math-through-programming approach, I'm more thinking of the Windows/Linux implementation as the paradigm. Yet schools have a lot of Macs. It still sounds like what I'm up to would work on a Mac, since I'm not doing anything multi-threaded or Tk-based (yet). Mostly, I'm just focussing on math students/teachers who already use calculators a lot, and suggesting Python's interactive environment as a next logical step (i.e. when moving from calculators to computers, let's not focus on spreadsheets, or dynamic geometry software to the exclusion of any real programming language). For this approach to work, you need, at minimum, an interactive command line, and a suitable text editor for writing/saving modules (programming interactively by typing defs at the command line is insufficient). Having keyword color coding in your editor sure helps kids learning the language -- at the command line too, as per IDLE. If the Mac doesn't have this, that's a problem from my point of view. Most of the stuff I'm doing would transfer to DrScheme easily. The one thing I'm not sure about is the lingo of objects as methods + data. DrScheme seems to use the paradigm of "data types" vs. "objects" and the implementation of objects is considered an advanced topic. But I prefer a way of conceptualizing that makes something called "objects" accessible near the bottom of the learning curve, because I want to talk about "vector objects" and "matrix objects" (no, not "types") without waiting for students to reach any guru level in the language. It may be a nomenclature issue. All that being said, I'm entirely in agreement with you that we need to attract a critical mass of new gurus with a commitment to the Mac platform, so that we don't so much rely on the 1% who do all the core enchancements. If, that is, we're serious about CP4E making inroads in schools. Either that, or wait for the UNIX-based MacOS (but that will be a slow upgrade process I think). Kirby
participants (3)
-
Kirby Urner -
Kirby Urner -
Paul Fernhout