Squeak-dev December 2015

squeak-dev@lists.squeakfoundation.org

60 participants
161 discussions

loading Ubuntu 64-bit
by Robert Withers 17 Dec '15

17 Dec '15

Hi, I just got a new 64-bit laptop I am configuring with 64-bit Ubuntu and trying to resolve those issues to build the vm. I ran the apt-get for everything I was aware of, but I get an error when running buildspurtrunkvmmakermage.sh: cogspurlinuxht/squeak trunk50.image UpdateSqueakTrunkImage.st squeak: could not find any display driver ./updatespurimage.sh: line 14: 27399 Aborted (core dumped) $VM trunk50.image UpdateSqueakTrunkImage.st cogspurlinuxht/squeak SpurVMMaker.image BuildSqueakSpurTrunkVMMakerImage.st squeak: could not find any display driver ./buildspurtrunkvmmakerimage.sh: line 12: 27431 Aborted (core dumped) $VM SpurVMMaker.image BuildSqueakSpurTrunkVMMakerImage.st For some reason it isn't finding the vm-display-X11 and I do not recall why from my prior install. Does this ring a bell with anyone who could assist me? Thank you, Robert ps. all the apt-get commands I ran: sudo apt-get install cmake zip bash-completion ruby git xz-utils debhelper devscripts sudo apt-get install libc6-dev:i386 libasound2:i386 libasound2-dev:i386 libasound2-plugins:i386 libssl-dev:i386 i#!libssl0.9.8:i386 libfreetype6-dev:i386 libx11-dev:i386 libsm-dev:i386 libice-dev:i386 sudo apt-get install build-essential gcc-multilib g++ sudo apt-get install libgl1-mesa-dev libgl1-mesa-glx:i386 sudo apt-get install binutils:i386 g++-4.6:i386 gcc-4.6:i386 sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so /usr/lib/i386-linux-gnu/libGL.so sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/mesa/libGL.so sudo apt-get install uuid-dev:i386 sudo apt-get install subversion

6 9

Daily Commit Log
by commits＠source.squeak.org 16 Dec '15

16 Dec '15

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2015-December/009215.h… Name: Sound-tpr.47 Ancestors: Sound-nice.46 Protect SoundRecorder from primitiveFailed inside a critical block; raise a Warning signal afterwards instead of a raw error =============================================

1 0

Re: [Pharo-dev] [squeak-dev] Re: [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: Unicode Support))
by Eliot Miranda 16 Dec '15

16 Dec '15

Hi Todd, On Tue, Dec 15, 2015 at 3:46 PM, Todd Blanchard <tblanchard(a)mac.com> wrote: > Hi Eliot, > > On Dec 15, 2015, at 13:46, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Just so you know, I will dig my heels in as deeply as I am able to prevent > the use of C++ libraries in the VM. It destroys the simulator, which is > the most important thing we have for VM development productivity. As far > as I'm concerned any use of external libraries to implement core > functionality kills the VM-in-Smalltalk concept that Squeak (and Pharo) are > built upon. > > > OK, I defer to you because you certainly know more about the VM internals > and what does and doesn't work well than anyone else. > > So I guess I would like to know your recommendation for 1) how best to > store strings - byte arrays (UTF8), - 2-byte word arrays (UTF16 - now we > get to worry about endian). > Raw Unicode, either as 8-bit, 16-bit or 32-bit. When creating a String it should start as an 8-bit-per-Unicode-character string. Attempts to store Character values that won't fit cause the String to become a String whose element size is large enough to accommodate the character. In Spur, become: is cheap so this growth pays only for the reallocation and copying of the at a, not for an expensive heap scan necessary to do the become:. > Bearing in mind that both representations are variable length and so while > accessing the n'th byte/word is O(1), accessing the n'th character is > necessarily O(n) unless you know you have no surrogates in your string. > Right, so UTF-8 and UTF-16 are not convenient representations and to be provided only for interchange. > > Also...since NSString has been mentioned...it is worth noting that > NSString is built atop CFString (source code here: > https://www.opensource.apple.com/source/CF/CF-855.11/CFString.c) which > does a fair job of optimizing memory by using bytes where it can and shorts > where it cannot. It is also worth noting that characterAt: actually does > the wrong thing, since it assumes characters are no bigger than FFFF rather > than 10FFFF. > Yes, and Squeak (and AFAIA, Pharo) has been doing this for ages. If one has become: it is very easy to manage. Now with Spur not only do we have become:, we have a fairly fast become:. Does this make sense? > Also...I'll just toss in this very nice article on unicode and how > NSString deals with it. > https://www.objc.io/issues/9-strings/unicode/ > > -Todd Blanchard > _,,,^..^,,,_ best, Eliot

3 3

The Trunk: Sound-tpr.47.mcz
by commits＠source.squeak.org 16 Dec '15

16 Dec '15

tim Rowledge uploaded a new version of Sound to project The Trunk: http://source.squeak.org/trunk/Sound-tpr.47.mcz ==================== Summary ==================== Name: Sound-tpr.47 Author: tpr Time: 15 December 2015, 4:33:09.091 pm UUID: 998878c2-2ae5-41e1-b60a-dbc169c238cd Ancestors: Sound-nice.46 Protect SoundRecorder from primitiveFailed inside a critical block; raise a Warning signal afterwards instead of a raw error =============== Diff against Sound-nice.46 =============== Item was changed: ----- Method: SoundRecorder>>primStartRecordingDesiredSampleRate:stereo:semaIndex: (in category 'primitives') ----- primStartRecordingDesiredSampleRate: samplesPerSec stereo: stereoFlag semaIndex: anInteger + "Start sound recording with the given stereo setting. Use a sampling rate as close to the desired rate as the underlying platform will support. If the given semaphore index is > 0, it is taken to be the index of a Semaphore in the external objects array to be signalled every time a recording buffer is filled. + We do *not* raise a primitiveFailed error here since this prim is called insdied a critical blcok and that often makes things painful. The only really likely case where this prim fails is a linux machine with no sound input hardware (a Raspberry Pi for example). See the startRecording method for how the failure is handled" - "Start sound recording with the given stereo setting. Use a sampling rate as close to the desired rate as the underlying platform will support. If the given semaphore index is > 0, it is taken to be the index of a Semaphore in the external objects array to be signalled every time a recording buffer is filled." <primitive: 'primitiveSoundStartRecording' module: 'SoundPlugin'> + "self primitiveFailed" - self primitiveFailed ! Item was changed: ----- Method: SoundRecorder>>startRecording (in category 'recording controls') ----- startRecording + "Turn on the sound input driver and start the recording process. Initially, recording is paused. + If the primStartRecordingDesiredSampleRate:... fails it almost certainly means we have no usable + sound input device. Rather than having the prim raise a failure error we let it quietly do nothing + (since I hate trying to debug errors inside a critical block) and check the actual sampling rate later. + If the sampling rate is 0 we know the startup failed and raise an application level Signal to let any + user code know about the problem. + You might think we should also use the stopRecording message to close things down cleanly but + that simply results in astorm of attempts to start recording so it is simpler to let it be deluded. An + attempts to start recording will repeat the test and thereby handle any plug-in hardware etc." - "Turn of the sound input driver and start the recording process. Initially, recording is paused." recordLevel ifNil: [recordLevel := 0.5]. "lazy initialization" CanRecordWhilePlaying ifFalse: [SoundPlayer shutDown]. recordProcess ifNotNil: [self stopRecording]. paused := true. meteringBuffer := SoundBuffer newMonoSampleCount: 1024. meterLevel := 0. self allocateBuffer. Smalltalk newExternalSemaphoreDo: [ :semaphore :index | bufferAvailableSema := semaphore. self primStartRecordingDesiredSampleRate: samplingRate asInteger stereo: stereo semaIndex: index ]. RecorderActive := true. samplingRate := self primGetActualRecordingSampleRate. + samplingRate = 0 ifTrue: [ Warning signal: 'SoundRecorder: unable to connect to sound input device']. self primSetRecordLevel: (1000.0 * recordLevel) asInteger. recordProcess := [self recordLoop] newProcess. recordProcess priority: Processor userInterruptPriority. recordProcess resume!

1 0

Looking for a working mailreader
by Robert Withers 16 Dec '15

16 Dec '15

Is there such for squeak? I tried Celeste but it didn't load correctly. I prefer all my tools tin squeak for immersion and full screen experience. -- . .. .. ^,^ best, robert

2 2

Re: [squeak-dev] Re: Looking for a working mailreader
by Robert Withers 15 Dec '15

15 Dec '15

That's unfortunate. I was hoping to hear of an updated stable version. thanks, robert On 12/15/2015 06:16 PM, Jecel Assumpcao Jr. wrote: > Robert Withers replied to self: >> I guess it was left behind. >> >> On 12/15/2015 06:09 AM, Robert Withers wrote: >>> Is there such for squeak? I tried Celeste but it didn't load >>> correctly. I prefer all my tools tin squeak for immersion and full >>> screen experience. > I am writing this reply in Celeste using a Squeak 4.1 image. I have not > tried loading Celeste in a newer image than that. I do have a small set > of fixes which I have not sent to be included in the official Celeste > because most of them are very wrong and were only enough to keep only > loading emails even though some were very broken. > > -- Jecel > > -- . .. .. ^,^ best, robert

1 0

Re: [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))
by H. Hirzel 15 Dec '15

15 Dec '15

Dale Thank you for your answer with links to the ICU library and the notes about classes in Gemstone. Noteworthy that you have a class Utf8 as a subclass of ByteArray. I understand that Gemstone uses the ICU library and thus does not implement the algorithms in Smalltalk. I am currently looking into what the ICU library provides. I found as well a Ruby library [2] which implements CLDR [3] It has methods like this "Alphabetize a list using regular Ruby sort:" $> ["Art", "Wasa", "Älg", "Ved"].sort $> ["Art", "Ved", "Wasa", "Älg"] Alphabetize a list using TwitterCLDR’s locale-aware sort: $> ["Art", "Wasa", "Älg", "Ved"].localize(:de).sort.to_a $> ["Älg", "Art", "Ved", "Wasa"] I hope that given such an example it would not be too difficult to reimplement a similar sort algorithm in Squeak/Cuis/Pharo. Currently the interest is in getting sorting done in a cross-dialect-way. --Hannes [2] https://blog.twitter.com/2012/twittercldr-improving-internationalization-su… [3] Unicode Common Locale Data Repository http://cldr.unicode.org/index On 12/7/15, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > Hannes, > > For GemStone, we are using the ICU library[1]. We have Unicode7, > Unicode16 and Unicode32 classes (subclasses of CharacterCollection) for > internal Strings and the class Utf8 (a subclass of ByteArray) for Utf8 > encoded strings ... > > The ICU library provides the primitive implementations for working with > the Unicode* and Utf8 classes > > When we started considering Unicode support, we looked at what it would > take to support collation - our main reason for looking at Unicode in > the first place) -- and we saw just how complicated the collation rules > can be[2], we were glad to see that someone had already done the hard > work[1]... > > Reconciling our legacy String implementations (String, DoubleByteString, > and QuadByteString) with the Unicode* classes was also interesting, > because the rules for Unicode equality and our legacy equality > implementation were not quite compatible. > > If you are interested in more information, I can share additional > details ... > > Dale > > [1] http://site.icu-project.org/ > [2] http://unicode.org/reports/tr10/ > > On 12/07/2015 11:54 AM, H. Hirzel wrote: >> Hello >> >> According to http://www.unicode.org/cldr/charts/27/collation/de.html the >> German >> phonebook sort order is >> >> a A ä Ä ą̈ Ą̈ ǟ Ǟ ạ̈ Ạ̈ ḁ̈ Ḁ̈ b B c C d D e E f F g G h H i I j J k K >> l L m M n N o O ö Ö ǫ̈ Ǫ̈ ȫ Ȫ ơ̈ Ơ̈ ợ̈ Ợ̈ ọ̈ Ọ̈ p P q Q r R s S ss ß t >> T u U ü Ü ǘ Ǘ ǜ Ǜ ǚ Ǚ ų̈ Ų̈ ǖ Ǖ ư̈ Ư̈ ự̈ Ự̈ ụ̈ Ụ̈ ṳ̈ Ṳ̈ ṷ̈ Ṷ̈ ṵ̈ Ṵ̈ v >> V w W x X y Y z Z >> >> I wonder why it looks like this. A lot of characters which never >> appear in a German text. >> >> >> For Spanish there is 'traditional' and 'standard' >> >> http://www.unicode.org/cldr/charts/27/collation/es.html >> >> standard a A á Á b B c C d D e E é É f F g G h H i I í Í j J k K l L m >> M n N ñ Ñ ņ̃ Ņ̃ ṇ̃ Ṇ̃ ṋ̃ Ṋ̃ ṉ̃ Ṉ̃ o O ó Ó p P q Q r R s S t T u U ú Ú >> ü Ü v V w W x X y Y z Z >> >> traditional a A á Á b B c C ch Ch CH cĥ Cĥ CĤ cȟ Cȟ CȞ cḧ Cḧ CḦ cḣ Cḣ >> CḢ cḩ Cḩ CḨ cḥ Cḥ CḤ cḫ Cḫ CḪ cẖ Cẖ d D e E é É f F g G h H i I í Í j >> J k K l L ll Ll LL lĺ Lĺ LĹ lľ Lľ LĽ lļ Lļ LĻ lḷ Lḷ LḶ lḹ Lḹ LḸ lḽ Lḽ >> LḼ lḻ Lḻ LḺ m M n N ñ Ñ ņ̃ Ņ̃ ṇ̃ Ṇ̃ ṋ̃ Ṋ̃ ṉ̃ Ṉ̃ o O ó Ó p P q Q r R s >> S t T u U ú Ú ü Ü v V w W x X y Y z Z >> >> And French is not easily found >> http://www.unicode.org/cldr/charts/27/collation/index.html >> or seems to be defined elsewhere >> >> http://unicode.org/repos/cldr/tags/release-27/common/collation/fr.xml >> >> Suggestions and hints are welcome >> >> --Hannes >> _______________________________________________ >> Cuis mailing list >> Cuis(a)jvuletich.org >> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org > > > _______________________________________________ > Cuis mailing list > Cuis(a)jvuletich.org > http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org >

7 18

Re: [Pharo-dev] [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))
by H. Hirzel 15 Dec '15

15 Dec '15

On 12/15/15, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, Dec 10, 2015 at 12:37 AM, Todd Blanchard <tblanchard(a)mac.com> > wrote: >> They are practically the same thing. >> >> ICU was developed by Taligent which was a joint venture between Apple and >> IBM. Makes sense that NSString and ICU's UnicodeString are pretty close >> in implementation. ICU was also ported to Java for Sun by IBM. The point >> is - this is a very elaborate chunk of code with far reach. If ICU is >> wrong on some point - it is universally wrong and thus likely to be taken >> as "right" as it is at least consistent. I think re-implementing it is >> folly TBH. Just use it. > > Apple seem to have moved on from NSString to support Unicode in a > different way in Switft... Could you please give some more details? I have read https://www.objc.io/issues/9-strings/unicode/#nsstring-and-unicode so far. It says that an NSString object actually represents an array of UTF-16-encoded code units. This in contrast to Squeak / Pharo where a String is an ArrayedCollection of 21 bit Unicode code points (transparently optimizing to a ByteArray if the string only contains values of the first code page). >> >>> On Dec 8, 2015, at 15:52, EuanM <euanmee(a)gmail.com> wrote: >>> >>> Equally old are the NextStep Object C functions which are now embodied >>> within MacOS X. >>> >> >> > >

2 1

drawing an arc
by Chris Muller 15 Dec '15

15 Dec '15

Does anyone know how to draw an arc on a Canvas? It has drawOval / fillOval, but I want to draw a piece of pie.

4 3

Re: [Pharo-dev] Unicode Support - Normalization NFD -- #decomposedStringWithCanonicalMapping
by H. Hirzel 15 Dec '15

15 Dec '15

On 12/13/15, stepharo <stepharo(a)free.fr> wrote: > >> It is best and (mostly) correct to think of a Unicode string as a sequence >> of Unicode characters, each defined/identified by a code point (out of >> 10.000s covering all languages). That is what we have today in Pharo (with >> the distinction between ByteString and WideString as mostly invisible >> implementation details). >> >> To encode Unicode for external representation as bytes, we use UTF-8 like >> the rest of the modern world. >> So far, so good. >> ...> > > like me ;) > I will wait for a conclusion with code :) > > Stef > Some code with illustration by the e acute example see below >> Why then is there confusion about the seemingly simple concept of a >> character ? Because Unicode allows different ways to say the same thing. >> The simplest example in a common language is (the French letter é) is >> >> LATIN SMALL LETTER E WITH ACUTE [U+00E9] >> >> which can also be written as >> >> LATIN SMALL LETTER E [U+0065] followed by COMBINING ACUTE ACCENT [U+0301] >> >> The former being a composed normal form, the latter a decomposed normal >> form. (And yes, it is even much more complicated than that, it goes on for >> 1000s of pages). >> >> In the above example, the concept of character/string is indeed fuzzy. >> >> HTH, >> >> Sven The text below shows how to deal with the Unicode e acute example brought up by Sven in terms of comparing strings. Currently Pharo and Cuis do not do Normalization of strings. Limited support is in Squeak. It will be shown how NFD normalization may be implemented. Swift programming language ----------------------------------------- How does the Swift programming language [1] deal with Unicode strings? // "Voulez-vous un café?" using LATIN SMALL LETTER E WITH ACUTE let eAcuteQuestion = "Voulez-vous un caf\u{E9}?" // "Voulez-vous un café?" using LATIN SMALL LETTER E and COMBINING ACUTE ACCENT let combinedEAcuteQuestion = "Voulez-vous un caf\u{65}\u{301}?" if eAcuteQuestion == combinedEAcuteQuestion { print("These two strings are considered equal") } // prints "These two strings are considered equal" The equality operator uses the NFD (Normalization Form Decomposed)[2] form for the comparison appyling a method #decomposedStringWithCanonicalMapping[3] Squeak / Pharo ----------------------- Comparison without NFD [3] "Voulez-vous un café?" eAcuteQuestion := 'Voulez-vous un caf', 16rE9 asCharacter asString, '?'. combinedEAcuteQuestion := 'Voulez-vous un cafe', 16r301 asCharacter asString, '?'. eAcuteQuestion = combinedEAcuteQuestion false eAcuteQuestion == combinedEAcuteQuestion false The result is false. A Unicode conformant application however should return *true*. Reason for this is that Squeak / Pharo strings are not put into NFD before testing for equality = Squeak Unicode strings may be tested for Unicode conformant equality by converting them to NFD before testing. Squeak using NFD asDecomposedUnicode[4] transforms a string into NFD for cases where a Unicode code point if decomposed, is decomposed only to two code points [5]. This is so because when initializing [6] the Unicode Character Database in Squeak this is a limitation imposed by the code which reads UnicodeData.txt [7][8]. This is not a necessary limitation. The code may be rewritten at the price of a more complex implementation of #asDecomposedUnicode. "Voulez-vous un café?" eAcuteQuestion := 'Voulez-vous un caf', 16rE9 asCharacter asString, '?'. combinedEAcuteQuestion := 'Voulez-vous un cafe', 16r301 asCharacter asString, '?'. eAcuteQuestion asDecomposedUnicode = combinedEAcuteQuestion asDecomposedUnicode true Conclusion ------------------ Implementing a method like #decomposedStringWithCanonicalMapping (swift) which puts a string into NFD (Normalization Form D) is an important building block towards better Unicode compliance. A Squeak proposal is given by [4]. It needs to be reviewed.extended. It should probably be extended for cases where there are more than two code points in the decomposed form (3 or more?) The implementing of NFD comparison gives us an equality test for a comparatively small effort for simple cases covering a large number of use cases (Languages using the Latin script). The algorithm is table driven by the UCD [8]. From this follows an simple but important fact for conformant implementations need runtime access to information from the Unicode Character Database [UCD][9]. [1] https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swif… [2] http://www.unicode.org/glossary/#normalization_form_d [3] https://developer.apple.com/library/ios/documentation/Cocoa/Reference/Found… [4] String asDecomposedUnicode http://wiki.squeak.org/squeak/6250 [5] http://www.unicode.org/glossary/#code_point [6] Unicode initialize http://wiki.squeak.org/squeak/6248 [7] http://www.unicode.org/Public/UNIDATA/UnicodeData.txt [8] Unicode Character Database documentation http://unicode.org/reports/tr44/ [9] http://www.unicode.org/reports/tr23/

1 0

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

Jump to page: