Squeak-dev July 2014

squeak-dev@lists.squeakfoundation.org

31 participants
223 discussions

minor Browser bug on linux
by gettimothy 14 Jul '14

14 Jul '14

Hi guys, I did not see this on Mantis. On a Browser click and hold on the left resizer bar on the protocol pane. The color of the bar changes, the mouse pointer changes to a double arrow icon <-> and the length of the resize bar extends over the top of the Browser title bar. apologies if it already exists.

2 2

Why are zipped and unzipped implemented in String rather than ByteArray?
by Nicolas Cellier 13 Jul '14

13 Jul '14

Because instead of just handling raw sequence of bytes, it instead handles raw sequence of bytes on Objects which are not sequence of bytes... Because we love complexity. ('All work and no play makes jack a dull boy' copyWith: 300 asCharacter) zipped unzipped

2 1

Please make http://ftp.squeak.org/current_stable/ redirect to http://ftp.squeak.org/4.5/ (is 4.4 currently) [EOM]
by Tobias Pape 13 Jul '14

13 Jul '14

[eom]

4 5

Why is zipped using a RWBinaryOrTextStream rather than just a WriteStream?
by Nicolas Cellier 11 Jul '14

11 Jul '14

this code | stream gzstream | stream := RWBinaryOrTextStream on: ByteArray new. gzstream := GZipWriteStream on: stream. gzstream nextPutAll: #[1 2 3 4]. gzstream close. stream reset. ^ stream contents. versus | stream gzstream | stream := ByteArray new writeStream. gzstream := GZipWriteStream on: stream. gzstream nextPutAll: #[1 2 3 4]. gzstream close. ^ stream contents. Because we love complexity so much?

1 0

New Cog VMs available
by Eliot Miranda 11 Jul '14

11 Jul '14

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3034/. The Squeak Spur VMs will now run Pharo images that have been bootstrapped (SpurBootstrap bootstrapPharoImage: 'myimage'), but be aware that the bootstrap does not yet update the modified packages in a Pharo 4 image, and hence sources for the modified methods is unavailable. CogVM binaries as per VMMaker.oscog-eem.812/r3039 Spur: Fix bug in old space GC processing of weaklings. Old code didn't trace strong references in weaklings to weaklings in markWeaklingsAndMarkAndFireEphemerons. Make sure nilUnmarkedWeaklingSlotsIn: can be inlined. Bug shows up as crashes in Pharo Spur, Pharo making much more use of weakness than Squeak or Newspeak. Fix bug in nilUnmarkedWeaklingSlotsIn: which was not guarding the isForwarded: check with an isFreeObject: not check. Move the scanning for young references in scavenger processing of weaklings into processWeakSurvivor:. Fix minor slips in allObjects & allInstancesOf: which should only empty weaklingStack if marking. Fix a couple of storePointer:ofObject:'s being applied to objStacks. Rename isReallyForwarded: to isUnambiguouslyForwarder: and add an assert to isForwarded: to catch accidental applications to free objects. Fix longPrintOop: for free referents. V3 Cogit: Fix bogus assert fail due to signedness. Slang: Assign complex expressions to loop variables in value: expansions. Old code would replace variable with expansion of actual parameter everywhere. -- best, Eliot

4 5

Here's a bizarre behaviour
by Chris Cunningham 10 Jul '14

10 Jul '14

Try typing in: BSObject selecting it and pressing cmd+B. In fact, try any characters before an existing class. (Characters after the class doesn't do the same). Any idea why this happens? -cbc

3 3

flash revisited
by Chris Muller 10 Jul '14

10 Jul '14

>> > It seems to do a very nice >> > job of flashing the morph, and it plays nicely with the "Reuse Windows" preference. >> > What's not to like? >> >> Please see this note from Bob Arning which succinctly describes what's >> not to like about the original: >> >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2013-August/172823.h… > > Bob's proposal was discussed at some length, but it was never added to trunk and > it does not appear in the version history. I think that Karl's submission is > based on the same idea, except that does it with a "double flash". Is that right? I think so. >> > The cmm 8/22/2013 version does not flash nicely, and the kfr 7/3/2014 version >> > uses delays, which may be problematic. The sw 10/10/1999 version works well and >> > does not have either problem. How about just using the one the works? >> >> >> >> #flashStyle or #flashIntensity preference would be one way to address those >> >> differences. >> > >> > We have enough obscure preferences that have entered the system for reasons >> > that nobody can even remember. Let's not add another. >> >> So, no more preferences at all then? Ever? Look, I know what you're >> trying to say about Preferences, and I think many of them could be >> removed, but its clear that we all have different interpretations >> about what #flash is supposed to be for; a low-level notifier or a >> high-level notifier that can integrate into application-UI's without >> blocking the UI. > > I am saying that preferences should not be added without good reason. Our > not being able to make up our collective mind about how a morph flash should > work falls solidly into the "no good reason" category. Not being able to make up our collective mind is precisely WHEN we need a preference. A "preference", by definition, is something that can vary according to one's individual, umm.. preference. :) It's when we CAN make up our collective mind that we _don't_ need a preference. In this instance, not only is there a difference of opinion about the implementation (whether it is okay to block the UI or not), but we seem to also be exploring aesthetic differences related to color (black/white vs. color-negative) and style (double or single flash). Things related to color and style do fall solidly into the "good reason for a preference" camp. You may have simply meant that we should agree whether we need a preference at all or not. I agree! We typically use preferences as a tool to reconcile, not expand, our differences. But if no one cares intensely enough about #flash, we will by definition not need a new preference. So I see our options as: 1) Nothing. Stick with the non-blocking flash we have. Not worth one more line of code. 2) Add #flash: arg, that switches one or more flash options. #flash to call #flash: with users preferred arg. 3) Non-UI-blocking implementation (Alarms-based, whatever) for a single 50-100 ms flash and visible with any color morph, even black. I support any and all of those options.

4 3

how to publish a package requiring an external library
by Douglas McPherson 10 Jul '14

10 Jul '14

Hi All, Is there a preferred/best practice way to publish a package together with its required external libraries? I've developed a package for accessing hardware peripherals such as GPIO and I2C from single board linux platforms such as Raspberry Pi. It uses FFI to access external libraries which I've assembled for use with Squeak. I would like to make binaries as well as source available. I was considering ss3 but I'm not sure it can store anything other than .mcz files. Any advice much appreciated. Thanks! Doug

6 9

http://metatoys.org
by gettimothy 09 Jul '14

09 Jul '14

Hi All. Squeak 4.5-13680 LocaleTest >>testIsFontAvailable fails because in LanguageEnvironment >>fontDownloadUrls ^ #('http://metatoys.org/pub/' ) the url has a problem on their end. http://metatoys.org/pub/ I did not see an entry in bugs.squeak.org. Just pointing out what I saw. cheers. tty

1 0

Morphic Designer
by Blake McBride 09 Jul '14

09 Jul '14

Greetings, First, is it the general understanding that Morphic Designer is the best way to go when trying to write business GUI apps (i.e. text controls, drop downs, list boxes, buttons, check boxes, radio buttons, buttons, etc.)? Second, trying to load Morphic Designer from Squeak 4.5 with: (Installer mc http: 'http://www.hpi.uni-potsdam.de/hirschfeld/squeaksource/ ') project: 'MetacelloRepository'; install: 'ConfigurationOfDesigner'. (Smalltalk at: #ConfigurationOfDesigner) load. does not work. It gives some sort of back-trace that won't allow me to copy and paste here (I am a Squeak newbie) but the first line is: UndefinedObject(Object)>>doesNotUnderstand: #signal At this point, I am not interested in understanding the backtrace and fixing the problem. I just thought that this package should have loaded cleanly. This begs the questions: is Morphic Designer supported and used? I've played with Morphic Designer with an older version of Squeak in the past. I remember having some sort of difficulty then too but was able to get past it. Does Morphic Designer still work? How can I use it? Thanks. Blake

3 6

← Newer
1
...
15
16
17
18
19
20
21
22
23
Older →

Jump to page: