🌐 Mailman 3 January 1997 - Pythonmac-SIG - python.org

Yes, but can it do... THIS?
by Joseph Strout Jan. 23, 1997

Jan. 23, 1997

I encountered "Chipmunk Basic" for the Mac the other day. It's a freeware BASIC implementation which can do some pretty nifty stuff in its Mac version, such as sprites (shapes which arrange themselves in layers, move around without clobbering the background or each other, and provide for collision detection). I've been looking for a language to get some young brothers-in-law into programming, and sprites would be a big plus (gives a language "Pac-Man equivalence"). But BASIC is pretty nasty by modern standards; Python is much nicer. So. Any sprite libraries for Mac Python yet? Thanks, -- Joe ,------------------------------------------------------------------. | Joseph J. Strout Department of Neuroscience, UCSD | | jstrout(a)ucsd.edu http://www-acs.ucsd.edu/~jstrout/ | `------------------------------------------------------------------' ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

2 1

Anyone got Py CFM68k working?
by just＠knoware.nl Jan. 21, 1997

Jan. 21, 1997

Hi all, Is anyone using Python 1.4 as CFM68k binaries? The distributed version crashes immediately upon launch on my machine. If I compile the whole stuff myself with CW10 the exact same thing happens. But 1.4b3 works splendid! The only difference really is that that version was compiled with CW9. Since I don't have CW9 on my machine anymore and since CW10 projects can't be opened in CW9 anyway (#@$!) I can't really compare. If anyone has some experience with this, I be really happy to hear about it. Thanks in advance, Just _______________ PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org _______________

1 0

How do I create a fullscreen window?
by Jack Jansen Jan. 12, 1997

Jan. 12, 1997

Ok folks, can anyone tell me how I can create a true fullscreen window on the Mac? I've looked all over Inside Mac and in various other places, but I can't seem to find it. I want to create a black background (preferrably with optional hiding of the menubar) like you see in game titles and such. I know this is a beginners question, but I am still a beginning mac programmer, I've only really done one little program for it (and not even that, really: I basically picked up where Guido left off:-), -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

2 1

AppleScript and the NeXTMac OS
by Bill Bedford Jan. 11, 1997

Jan. 11, 1997

This was posted on the Applescript List, and a few others, I thought it might be of interest to people here. ~X-URL: http://www.infoworkshop.com/~jonpugh/ ~Date: Sat, 11 Jan 1997 00:02:20 -0800 ~Reply-To: Macintosh Scripting Systems <MACSCRPT(a)LISTSERV.DARTMOUTH.EDU> ~Sender: Macintosh Scripting Systems <MACSCRPT(a)LISTSERV.DARTMOUTH.EDU> ~From: Jon Pugh <jonpugh(a)FROSTBITEFALLS.COM> ~Subject: Re: AppleScript and the NeXTMac OS ~ ~Well, I guess that's my cue... ~ ~First off, nothing I say here is official Apple policy. This is ~essentially a summary/continuation of a discussion that started on the ~OpenDoc-Interest mailing list in the beginning of December. I've ~crossposted this to MacScripting, AppleScript Users and OpenDoc Interest ~because I think everyone wants to know what's going on. I know I do. ;) ~ ~I didn't hear about the NeXT deal until you folks did, so I'm still ~absorbing it and providing my feedback when asked, but this discussion ~started before that happened, and it hasn't changed much, so I think that ~validates a lot of the reasons for doing it. ~ ~I've been trying to decide what to do about OpenDoc and OSA. We've all ~been hampered by a number of aspects of AppleScript. Notably it's lack of ~improvement. Given OpenDoc's cross platform aspects, and AppleScript's ~lack of those cross platform aspects, AppleScript is proving to be of ~limited use. Thus, we must consider other options. ~ ~The J word is what comes in here. Java could suffice as a scripting ~language if you had an OSA implementation of it. It's too geeky for a lot ~of people, so an AppleScript/HyperTalk kind of thing would still be nice, ~but considering that programmers like working in Java, it should be an easy ~sell. ~ ~An OSA Java would let us compile a bunch of classes up into a standalone ~script. We could use our own interface with run, open, idle and quit, as ~well as the applet interface. That would be a fine start. Using Frontier, ~you ought to be able to nest classes in the odb. Should be cool. ~ ~Then, we could bridge AppleEvent subroutine events, like the ones ~AppleScript and Hypercard use, into Java methods called by name. To send ~messages back, we'd need to have a package which allowed you to build ~AppleEvents, much like Frontier does. ~ ~We could even implement a new security module since we'd like to allow more ~access than an applet but still disallow some kinds of operations. I think ~a control panel the user could set would be nice. That would allow one ~person's OSA Java to check for virus type actions while letting us geek ~boys do those kinds of potentially dangerous operations without complaint. ~ ~So, if we had a Java OSA component, what would that buy us in OpenDoc? ~That's my responsibility after all. ~ ~Well, we could build a system which attaches Java code to OpenDoc objects ~pretty easily. Part editors could use it to attach code to their objects ~too. You could use AppleScript, Java or any OSA language. This is the ~value of the OSA. We could do that in our C++ implementation if we like, ~or in some new implementation draft pick to be named later. ~ ~Now, we would need a few more things for this to be truly cool though. In ~addition to the package which allows us to build AppleEvents and object ~specifiers, we'd need to be able to send and receive AppleEvents. Since ~this is Java, we have IP easily. We also have the MacOS, so we have ~AppleTalk. Assuming we have OpenTransport or something equivalent on the ~newOS, we could do a portable AppleTalk implementation, but that would ~involve rewriting the AppleEvent manager in Java. That would enable AEIP ~and it would do wonderful things for the interface and performance. ~Considering that the AE manager is interpreted 68K right now, a Java AEM ~would run as fast or faster. We'd get IP easily and we'd get garbage ~collection. This would remove all the copying that the AEM does now, which ~should improve performance of AE code immensely. ~ ~Then we need to parse incoming AEs and map them to Java methods. We also ~need to be able to parse object specifiers so that we can talk with ~AppleScript and use them for remote object references. I still like the ~way whose clauses map to lists which are resolved remotely. I think it ~would be worthwhile keeping those in our brave new world. ~ ~We can also use standard Java RPC methods, including their 1.1 scripting ~features, although these won't talk to other OSA languages. While I'm at ~it, I'd add a new call to the OSA component interface, which is a ~CallByName kind of method that would correspond to the subroutine ~AppleEvent. Right now you have to build an AE and use ExecuteEvent or such ~to send the event to the script. I think it would be better to hide that ~common implementation in a standard OSA call which takes a method name and ~an array of parameters. ~ ~So, we basically rewrite the AEM and the OSL in Java as well as doing the ~OSA Java. Piece of cake. ;) ~ ~Of course, we'd get a cross platform implementation, most of it at least, ~depending on the AppleTalk capabilities we can use or reimplement. We ~don't really get a scripting language, but we can use either an existing or ~new OSA AppleScript. You'd have to program in Java using this new package ~interface, but it should be pretty nice to deal with. ~ ~We could also add an object resolution framework much like ODF uses in C++. ~In Java and without the OSL, it'll be a lot cleaner too. My questions now ~revolve around building a decent OOP framework for resolving whose clauses. ~It would be simple enough to build a framework which iterated through all ~the objects and compared them to a literal, but the trick comes in allowing ~someone to override everything properly and add other more efficient ~searches of the objects when appropriate. Ideas are welcome here, as are ~they everywhere else. It sounds like it shouldn't be too hard to do ~simply, but I can imagine people making it difficult with legacy code and ~database stuff. ;) ~ ~So, that's what I've been thinking about. I'd like to see a new and ~improved AppleScript, but I'm not holding my breath. Of course, I'm not ~holding my breath about this stuff yet either. It sounds like a sensible ~plan given the whole Java emphasis that everyone is into these days, but ~there's still plenty of work to do and few people to do it. ~ ~Feel free to comment and question things. Remember to color outside the ~lines. This is all just brainstorming at this stage. ~ ~Jon ----------------------------------------------------------------------- Bill Bedford Designer of Photo-Etches billb(a)mousa.demon.co.uk owner Brit_Rail-L --- british railways historical list ----------------------------------------------------------------------- ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0

Internet Config module available
by Jack Jansen Jan. 10, 1997

Jan. 10, 1997

I've built a Python interface to the Internet Config package (finally), available for Python 1.4 PPC and CFM68K. You can fetch it from <ftp://ftp.cwi.nl/pub/jack/python/mac/ic.hqx>. As usual, the ppc version has been lightly tested and the cfm68k version not at all. Please let me know whether it works. I would also appreciate feedback on the design of the interface, let me know if you would like it to work differently or if you miss functionality in the high-level interface. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

1 0

Re: [PYTHONMAC-SIG] Default Tk attributes?
by Jack Jansen Jan. 4, 1997

Jan. 4, 1997

Hmm, the sensible thing to do on the Mac would be to get this preferences file either from the "Preferences" folder in the system folder, from the Python "home" folder or from anywhere on sys.path. <p> All of these are pretty easy to implement, what do people think is the handiest? Hmm, ignore the <p> above: as people may have guessed I spent all evening typing html:-) -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)cwi.nl | ++++ if you agree copy these lines to your sig ++++ http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm ================= PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org =================

2 1

Useless, but fun program for Python fans
by Jurjen N.E. Bos Jan. 3, 1997

Jan. 3, 1997

I was inspired by the Pi program that is distibuted with Python. I decided to expand it a little, and speed it up using a better approximation method. The result is a program that can print the following number to infinite precision: - pi - e to fraction powers - sin, cos, sinh, cosh, asin, atan, acos of a fraction - roots of fractions - sums of any of the above At the end of the program, there are some examples. For example, if you are only interested in printing pi, use p(pi4). Hope you like it; let me know if you do. # This program prints mathematical constants to infinite precision # It can print all constants specifiable as num/den*sum(i=0,,product(k=1,i,f(n)/g(n))) # where f and g integral functions satisfying -g(k), # or sums of these constants. # Written by Jurjen N.E. Bos (jurjen(a)q2c.nl), 1996-97. # Examples are shown below from sys import stdout from string import zfill # the class below is dirty in the sense that class instances modify themselves # after quite "innocent" operations, such as *,/,+ negDenom = "Denominator must be positive" class series: def __init__(self,num,den,f,g): self.num = long(num) # current value (always positive) self.term = self.num # next term (may be negative) self.den = long(den) # common denominator (always positive) self.f = f self.g = g self.k = 1 # multiply sequence by a number (modifying the sequence!) def __mul__(self,n): self.num = n*self.num self.term = n*self.term return self # divide sequence by a number (modifying the sequence!) def __div__(self,n): self.den = n*self.den return self # add number to sequence (modifying the sequence!) def __add__(self,n): self.num = self.num+n*self.den return self # expand with given precision def expand(self,factor): while abs(self.term)*factor>=self.den: self.term = self.term*self.f(self.k) g=self.g(self.k) self.num = self.num*g self.den = self.den*g self.num = self.num+self.term self.k = self.k+1 # this is a lower estimate: subtract one if negative term return self.num*factor/self.den-(self.term<0) # integer part of sum of a list of series def intPart(l): extra = 1 # force the while to execute once estimate = 0 # we have fractional part and error for every term, # so we can expect up to 2 extra per term while estimate%extra >= extra-3*len(l): # too much error, estimate two more digits extra = extra*100L estimate = 0 for s in l: estimate = estimate+s.expand(extra) return int(estimate/extra) def p(l): digits = 8 # number of digits to print at once base = 10**digits # our computation "number base" lastInt = intPart(l) stdout.write(`lastInt`+',') #print fraction while 1: carry = lastInt for s in l: q,s.num = divmod(s.num,s.den) carry = carry-int(q) s*base lastInt = intPart(l) output = lastInt-carry*base if not (0<=output<base): raise "Consistency check failed" stdout.write(zfill(output,digits)) stdout.flush() # now some interesting series # e to the power n/m def expSeries(n=1,m=1): if m<0: raise negDenom def f(k,nn=n): return nn def g(k,mm=m): return k*mm return series(1,1,f,g) # c*arc sine of n/m def asinSeries(n,m=1): if m<0: raise negDenom def f(k,n2=n**2): return (2*k-1)**2*n2 def g(k,m2=m**2): return m2*(2*k)*(2*k+1) return series(n,m,f,g) # arc tangent of 1/n def atanSeries(n,m=1): if m<0: raise negDenom def f(k,n2=n**2): return -(2*k-1)*n2 def g(k,m2=m**2): return m2*(2*k+1) return series(n,m,f,g) # r-th root of n/m (around one) def rootSeries(n,m,r=2): if m<0: raise negDenom n = n-m # move origin to zero def f(k,nn=n,rr=r): return nn*(1-(k-1)*rr) def g(k,mr=m*r): return k*mr return series(1,1,f,g) # the sine of n/m def sinSeries(n,m=1): if m<0: raise negDenom def f(k,n2=n**2): return -n2 def g(k,m2=m**2): return (2*k)*(2*k+1)*m2 return series(n,m,f,g) # the cosine of n/m def cosSeries(n,m=1): def f(k,n2=n**2): return -n2 def g(k,m2=m**2): return (2*k-1)*(2*k)*m2 return series(1,1,f,g) # the hyperbolic sine of n/m def sinhSeries(n,m=1): if m<0: raise negDenom def f(k,n2=n**2): return n2 def g(k,m2=m**2): return (2*k)*(2*k+1)*m2 return series(n,m,f,g) # the hyperbolic cosine of n/m def coshSeries(n,m=1): def f(k,n2=n**2): return n2 def g(k,m2=m**2): return (2*k-1)*(2*k)*m2 return series(1,1,f,g) # natural log of n/m (around one) def logSeries(n,m): if m<0: raise negDenom n = n-m # move origin to zero def f(k,nn=n): return -k*nn def g(k,mm=m): return mm*(k+1) return series(n,m,f,g) # now try a few of these: just type p(<value>), e.g. p(pi4) # (this works only once for each <value>, since it is modified!) # the constant e is the simplest e=[expSeries()] # pi using some standard formulas (in speed order: last one is fastest) pi1=[series(4,2,lambda(k): k,lambda(k): 2*k+1)] pi2=[asinSeries(1,2)*6] pi3=[atanSeries(1,5)*16,atanSeries(1,239)*-4] pi4=[atanSeries(1,8)*24,atanSeries(1,57)*8,atanSeries(1,239)*4] # roots are easily speeded up by rational approximations of the result # square root of 2 sr2=[rootSeries(2*14**2,17**2)*17/12] # cube root of 2 cr2=[rootSeries(2*4**3,5**3,3)*5/4] # golden ratio phi=[(rootSeries(5*17**2,38**2)*38/17+1)/2] # log of 2 (simple way) ln2a=[logSeries(1,2)*-1] # log of 2,3,5,7 (fast way, using combinations of small logs) def combineLogs(a,b,c,d): return [logSeries(125,126)*-a,logSeries(224,225)*-b, logSeries(2400,2401)*c,logSeries(4374,4375)*-d] ln2=combineLogs( 72,27,19,31) ln3=combineLogs(114,43,30,49) ln5=combineLogs(167,63,44,72) ln7=combineLogs(202,76,53,87) # log of 10 is sum of log 2 and 5 ln10=combineLogs(239,90,63,103) -- jurjen(a)q2c.nl ( Jurjen N.E. Bos) ========PYTHONMAC-SIG - SIG on Python for the Apple Macintosh send messages to: pythonmac-sig(a)python.org administrivia to: pythonmac-sig-request(a)python.org ========

1 0