Squeak-dev November 2002

squeak-dev@lists.squeakfoundation.org

189 participants
695 discussions

Re: "Pattern Hatching"
by Daniel Altman (Da Vinci) 28 Nov '02

28 Nov '02

Hi! In OOP (at Univ. of Buenos Aires) we learn to call them this way: - variables --> internal collaborators - parameters --> external collaborators My opinion is that it's more OO thinking an object as having collaborators (and interacting with them sending messages) rather than thinking those collaborators as variables, a concept that is usually associated with a value that you can directly manipulate. ======================================== Daniel Altman Da Vinci - Consultoría de Sistemas

1 0

SocketStream>>upToEnd
by Markus Fritsche 28 Nov '02

28 Nov '02

SocketStream>>upToEnd needs contentLenth, however, it's not implemented. 28 November 2002 12:43:33 pm VM: Win32 - Squeak3.3alpha of 24 January 2002 [latest update: #4967] Image: Squeak3.4alpha [latest update: #5125] SocketStream(Object)>>doesNotUnderstand: Receiver: a SocketStream Arguments and temporary variables: aMessage: a Message with selector: #contentLength and arguments: #() Receiver's instance variables: socket: a Socket[connected] inStream: a BufferStream(0) outStream: a BufferStream(0) status: a Dictionary(#buffered->true #inDataCount->0 #localAddress->a ByteArray...etc... SocketStream>>upToEnd Receiver: a SocketStream Arguments and temporary variables: rest: nil Receiver's instance variables: socket: a Socket[connected] inStream: a BufferStream(0) outStream: a BufferStream(0) status: a Dictionary(#buffered->true #inDataCount->0 #localAddress->a ByteArray...etc... LIRPCTCPServer>>process: Receiver: a LIRPCTCPServer Arguments and temporary variables: aSocket: a Socket[connected] ss: a SocketStream Receiver's instance variables: connectionHandler: ConnectionHandler port: 8202 [running] port: nil [] in LIRPCTCPServer>>value: Arguments and temporary variables: aSocket: a Socket[connected] --- The full stack --- SocketStream(Object)>>doesNotUnderstand: SocketStream>>upToEnd LIRPCTCPServer>>process: [] in LIRPCTCPServer>>value: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [] in BlockContext>>newProcess

1 0

Recent Morphic/Alice changes?
by Bill Schwab 28 Nov '02

28 Nov '02

Hello all, I grabbed the most recent 3.4 alpha and loaded my code into it. There is a noticeable slow-down in my Alice-based experiments, which seems to be most severe as new objects are added to the wonderland. I'm using Alice as a retained mode engine, with the camera controls and script editor hidden. The visual feedback offered by PluggableButtonMorph seems to be spread over more time than in 3.2. That lead me to look at framerates. Absent a running wonderland, the frame rate (in 3.4a) on my P4 at home is being reported as roughly 470 frames per second???? That's vs. 45 fps or so in 3.2. Is that real, or is it just a bug in the frame rate morph? With the wonderland, frame rates are reported as 25-40 fps vs. similar ranges in 3.2, though there's more of a penalty for doing certain things in 3.4a. I did _not uninstall/reinstall Balloon3D. Should I have done so? I used SM to install a few things, including the RB and Connectors. Comments/suggestions? Bill Wilhelm K. Schwab, Ph.D. bills(a)anest4.anest.ufl.edu (352) 846-1285

2 1

looking for locally saved updates first?
by Jeff Sparkes 28 Nov '02

28 Nov '02

If I have the preference "updateSavesFiles" on, then the updates are saved into a folder called "updates". If I update from an older image, and have the preference on, I'd like it to load them from the local disk first, and only go out to the net if the update isn't available locally. This allows me to cache updates, and install them faster. I can do this manually with "Utilities applyUpdatesFromDisk", but would like to use the preference to enable it. Does anybody see any problems with this? There's a potential security risk, but not much more likely than inserted bogus updates at the server end. And having done this, would it make sense to always look for local updates first, so that reloading from a clean image doesn't require changes the preferences first? Although with Ned's changes to save/load preferences from disk, it's not much hassle. I suspect that the code is already in the Utilities class, but I haven't grokked it yet.

2 1

Re: [Q] x.509 encoding of a dsa public key
by Martin Kobetic 28 Nov '02

28 Nov '02

Hi Robert, > Thanks for the links - I had found the first one in my web searches but not the > second. I noticed Booz-Allen seems to have done a lot of beltway consulting in > this area. I am scared; that's a lot of work! pros: you get SNMP and PKI and > surely some other items with it, cons: ASN.1 and X509 represent...well a lot > more work than I have weekends. If code doesn't appear from a local diety, I > will proceed to hack TSTTCPW, which is the DSAPublicKeyInfo encoding {id-dsa- > with-sha1 SEQUENCE<q, p, g, y>} or so, and not the full X509Certificate. If > only I knew what those bits were.. Well, if you really need just that particular bit, it shouldn't be too hard. The actual bits likely are a DER encoded instance of given ASN.1 type. I am not sure where does the definition that you quote come from, because it doesn't quite match what I see in RFC3279/80 nor the older version RFC2459. The complete definition seems to consist of following types: SubjectPublicKeyInfo ::= SEQUENCE { algorithm AlgorithmIdentifier, subjectPublicKey BIT STRING } AlgorithmIdentifier ::= SEQUENCE { algorithm OBJECT IDENTIFIER, parameters ANY DEFINED BY algorithm OPTIONAL } Where in case of DSA: 1) the algorithm of AlgorithmIdentifier takes value of id-dsa OBJECT IDENTIFIER ::= {iso(1) member-body(2) us(840) x9-57(10040) x9cm(4) 1 } BTW, the oid that you mention id-dsa-with-sha1 OBJECT IDENTIFIER ::= {iso(1) member-body(2) us(840) x9-57 (10040) x9cm(4) 3 } seems to be used for actual DSS signatures, not for DSA public keys. But I may be just misreading things. 2) parameters of the AlgorithmIdentifier optionaly contains Dss-Parms ::= SEQUENCE { p INTEGER, q INTEGER, g INTEGER } 3) the subjectPublicKey bitstring is a DER encoding of an INTEGER describe as DSAPublicKey ::= INTEGER -- public key, Y The type definition that you quote, could be a flattened version of the same though, depending on the encoding that is used, I guess. In any case, translating either of these to/from bits is not that hard even without any ASN.1 infrastructure at hand. If you need a quick intro to ASN.1 and DER encoding, take a look at 'A Layman's Guide to a Subset of ASN.1, BER, and DER' at http://www.rsasecurity.com/rsalabs/pkcs/index.html. That should get you up to speed quickly. > I completely agree that this would be a _very_ useful open-source project. Any > chance of Cincom donating your work in X509 and ASN.1? We could put it in the > Goodies category of SqueakMap! ;-) I don't think anybody on the developement team would mind that, and the thoughts to pursue it come up from time to time. But it's not happening for various reasons that I can't get into. I don't think it's completely unlikely to happen, I'm just worried that it might be too late when it actually comes to that. On the other hand X509 in VW still needs a lot of work, it has just barely enough to get SSL going. Interestingly we've got 3 independent ASN.1 attempts though. X509 itself uses it's own fairly simplicistic ANS.1/DER decoder, then there's a preview of a general ASN.1 framework, and finally there's an SNMP optimized framework in Opentalk/SNMP. I hope that we will migrate X509 over to the generic ASN.1 framework sometimes soon. The SNMP version is likely to live a life of its own for a while, unless we'll suddenly have copious amounts of spare time to spend distilling the best out of those two implementations. Regards, Martin Martin Kobetic, Cincom Smalltalk Development, http://www.cincom.com/smalltalk

3 3

Re: minor annoyance with "world/open/package loader"
by Daniel Vainsencher 28 Nov '02

28 Nov '02

Can you explain more about your scenario? though I knew dynamic open menu would cause this kind of issue, I think I've actually never opened more than one SMLoader in an image where I only used it (and not developed it). So obviously, I haven't noticed that this is annoying for that package. It might be a general solution to just sort the open menu entries by their entry text. It wouldn't make items fixed, by pretty stable, easy to search. What do you think? Daniel Jeff Sparkes <jsparkes(a)databeacon.com> wrote: > While tracking the OSProcess problem, I did a lot of install of > SqueakMap installs. One minor annoyance is that the position of > the "Package Loader" line in the open menu changes position. I know that this is due to the dynamic open menu from Daniel. I suggest that it be moved to after IRC in the static menu. The > "SqueakMap Browser" label will still be inserted before it, but at > least the package loaded will be just above the line. At least until another package registers itself.

2 1

RE: manuallly controlling dependencies, at least for SAR
by Jeff Sparkes 28 Nov '02

28 Nov '02

> From: goran.hultgren(a)bluefish.se [mailto:goran.hultgren@bluefish.se] > This one is a fixed bug not yet released. Change this method to be: > > cardWithNameBeginning: aString > ...and then try again! Or make sure to only use lower case without > spaces (don't need the full name though) in the search like this: > > SMSqueakMap default installPackageNamed: 'win32nativefonts' That did the trick. You have to expect that people will want to use the literal name from the package loader display. Perhaps you shouldn't have allowed space in names, but I wasn't the first to do it. The refactoring browser was already there. :-) In the branch of this thread, you want us to use "load scripts" . I still think that the require: method is at least semantically useful to show why you're loading another package. Here's a working version, but not as a change set which might lead someone to actually use it. require: packageName "Install a package if it's not already installed." | card | card _ DefaultMap cardWithName: packageName. (DefaultMap installedPackages includes: card) ifFalse: [(self confirm: 'Install required package ' , packageName , ' first?') and: [DefaultMap installPackageNamed: card name]]

2 1

RE: manuallly controlling dependencies, at least for SAR
by Jeff Sparkes 28 Nov '02

28 Nov '02

> Again - you can do this today using "load scripts". > > I don't want people to add stuff like this "inside" the > packages though > because that will lead to problems later. The packages should be > "clean"! So, what to do then? Simply write a .st file that uses the > SqueakMap API and register that file as a "Dynamic/static load script" > on SM. Oh. Now I understand. Is there a "how to build a SqueakMap package" anywhere? It should be reachable from http://map2.squeakfoundation.org/sm/ I can start a page on minnow later today, but maybe someone else should write the first draft, since I'm obviously not a guru. I don't think I've read all the information in the mailing list, so it's time to go check the archives. The odd thing is, I don't even have a package with dependencies...

2 1

Squeak on Handheld Linux
by Tommy Thorn 28 Nov '02

28 Nov '02

There are a number of options for running Squeak on a handheld Linux system, but the information about them is quite spread out and hard to obtain. I've tried to consolidate what I know about these options: Squeak on Handheld Linux http://minnow.cc.gatech.edu/squeak/2437 Please feel free to correct and add more information. Also, I've added a new page with more detail on the DirectFB version that I've messed with: DirectFB Squeak on the Zaurus SL-5xxx http://minnow.cc.gatech.edu/squeak/2930 Unfortunately, nothing has yet changed with the code ... Regards, Tommy

1 0

[FIX] (was [BUG?][QUESTION] Browser behavior change between Squeak 2.x a nd 3.x ???)
by Doug Way 28 Nov '02

28 Nov '02

I thought Torge's fix here was useful enough to warrant a [FIX] tag, so we'd remember to pick it up for 3.5alpha (if not 3.4). Assuming a fancier fix isn't submitted in the meantime. - Doug Way Begin forwarded message: > From: Torge.Husfeldt <Torge.Husfeldt(a)gmx.de> > > You could, on the other hand, just hack your changes into: > Browser>>defineCless:notifying: > This is the place where right now all the magic is going on > regarding class changes. It could be as well extended to fit > your needs. > > HTH, > Torge > > P.S.I attached my first shot on this > > >

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
70
Older →

Jump to page: